WordPress performance

Make your WordPress site load in under a second.

Passing Core Web Vitals is not a plugin you install — it's the render path, the images, the database and the third-party scripts, fixed one measurement at a time. I do that work on WordPress and WooCommerce sites without touching your design.

0years on WordPress
<2.5sLCP target
0redesign required
Two colleagues reacting to a site loading instantly
The delta

The numbers that move after a real optimization pass.

Not a theme swap — the same site, made fast. Below is a representative before/after on a plugin-heavy WooCommerce build.

Largest Contentful Paint
4.2s0.0s
−79% faster
Total page weight
5.6MB0.0MB
−77% lighter
Lighthouse score
380
passing, mobile
Time to Interactive
9.1s0.0s
−80% quicker

Representative figures. Actual gains depend on your host, theme and plugin stack — the audit tells you what yours can realistically hit.

Why it's slow

The usual suspects.

Ninety percent of failing WordPress sites fail for the same handful of reasons. The audit finds which ones are yours.

01

Render-blocking CSS & JavaScript

Every plugin queues its own stylesheet and script into the <head>, and the browser can't paint until they're done. Critical CSS, deferral and unloading fix it.

02

A hero image that weighs 2MB

The Largest Contentful Paint element is almost always an image. Correct sizing, modern formats and priority hints usually halve LCP on their own.

03

Layout shift from fonts & embeds

Late web fonts, un-sized images and injected ad slots push content around after load. That's CLS — fixable with sizing, font-display and reserved space.

04

Slow server response (TTFB)

Uncached PHP, a bloated database and cheap shared hosting delay the very first byte. Object caching, query cleanup and edge delivery bring it down.

05

Third-party scripts you forgot about

Chat widgets, heat-maps, tag managers and old tracking pixels quietly block the main thread. They get audited, deferred, or removed.

How I work

Measure, fix, verify — in that order.

No guesswork and no "let's install five plugins and hope." Every change is proven against numbers on a staging copy before it reaches your visitors.

Audit

Baseline every page against field and lab data, then map each failing metric to its real cause.

Fix on staging

Work on a clone, one change at a time, re-measuring after each so nothing is done on faith.

Ship & verify

Roll the verified wins to production and confirm the numbers held under real traffic.

Hand over

A short doc and the guardrails so a plugin update six months from now doesn't undo the work.

What you get

A faster site, and proof it's faster.

Passing Core Web Vitals

LCP, INP and CLS in the green on the field assessment, not just a lab score.

Before/after report

Concrete numbers per page so you can see exactly what changed and by how much.

Same design, intact

Nothing about how your site looks or works changes — it just gets fast.

Handover & guardrails

A short maintenance doc so the gains survive future plugin and theme updates.

Questions

Before you ask.

Caching fixes repeat-visit speed, not the first paint a new visitor and Google actually measure. Most failing sites fail on render-blocking CSS and JavaScript, an oversized hero image, layout shift, and slow server response. A plugin helps at the edges, but the wins come from fixing the critical rendering path — hands-on work, not a toggle.

No. Everything runs on a staging copy first, one change at a time, with before-and-after measurements. Nothing ships to production until it's verified visually and functionally, and any change that regresses layout or behaviour is rolled back.

Yes — those are the most common cases, and where the biggest gains hide: uncached cart fragments, bloated builder markup, dozens of plugin scripts on every page. The method is the same: measure, cut, verify.

Lighthouse is a lab test on one simulated device. Core Web Vitals in Search Console use field data — real Chrome users over 28 days. The goal is passing the field assessment, so the work is validated against both, never just a green lab number.

Usually one to three weeks depending on the site. You get a prioritised audit, the fixes implemented on staging then production, a before-and-after report, and a short handover doc so your team keeps the wins.

A review of your live pages against Core Web Vitals and Lighthouse, the specific bottlenecks ranked by impact, and an honest estimate of the effort to fix them. No obligation — and useful even if you take it in-house.

Let's find out how fast yours can be.

Send me your URL and I'll come back with the real bottlenecks and what it takes to pass — free, no strings.