WordPress Core Web Vitals: Why Only 44% of Sites Pass (and How to Join Them)

Here's a number that should bother anyone running marketing on a WordPress site: on mobile, only around 44% of WordPress sites pass all three Core Web Vitals. Shopify sites pass at roughly 65%; Wix has climbed past 60%. The platform powering nearly half the web is, out of the box, one of the worst-performing places to put a landing page.

That's not a reason to leave WordPress, the passing 44% prove it's fixable. But it is a reason to stop treating Core Web Vitals as a developer curiosity. If you buy traffic or compete for rankings, CWV is a line item in your budget whether you track it or not.

Why marketers should care (in money terms)

Organic: Core Web Vitals are a Google ranking signal, a tiebreaker between comparable content, and increasingly a filter for who gets into top stories and prominent placements. Paid: landing page experience feeds Google Ads Quality Score, and Quality Score directly sets what you pay per click. A slow landing page means you pay more for the same visitor, a quiet tax on every campaign you run. Conversion: every additional second of load time bleeds conversion rate; slow pages lose people before your headline gets a chance.

The three metrics, translated

• LCP (Largest Contentful Paint): how long until the main thing on the page (usually your hero image or headline) is visible. Target: under 2.5 seconds. This is the one WordPress sites fail most.
• INP (Interaction to Next Paint): when a visitor taps a button or opens your menu, how long before the page responds. Target: under 200ms. Heavy JavaScript is the culprit; this metric replaced FID precisely because FID was too easy to pass.
• CLS (Cumulative Layout Shift): does the page jump around while loading (you go to tap a button and an ad shoves it down the page). Target: under 0.1. Caused by images without dimensions, injected banners, and late-loading fonts.

One crucial distinction: Google judges you on field data, real Chrome users over the past 28 days, not the lab score you get by running a test. PageSpeed Insights shows both; the field data at the top is the one that counts, and it's also why fixes take up to a month to show in the report. Don't panic-optimise the lab score.

Why WordPress specifically struggles

The 44% number isn't bad luck. WordPress's flexibility is precisely the problem: a typical business site stacks a multipurpose theme, a page builder, and 25+ plugins, each adding CSS and JavaScript to every page. The result is exactly what CWV punishes, heavy render-blocking assets (LCP), lots of JavaScript competing with user input (INP), and elements loading in late and shoving things around (CLS). Add entry-level shared hosting and you start every page load half a second behind. Platforms like Shopify score better not because they're cleverer but because they're closed: users can't stack arbitrary code. WordPress lets you build anything, including a very slow site.

The fix list, ranked by impact

For LCP (start here):

1. Decent hosting + full-page caching, a slow server response caps everything else.
2. Optimise the hero: compress it, serve WebP/AVIF, size it correctly, and preload it, and never lazy-load the LCP image (a shockingly common self-inflicted wound; lazy-loading everything includes the one image you needed instantly).
3. Reduce render-blocking CSS/JS, minify, defer non-critical scripts, unload plugin assets on pages that don't use them (Perfmatters/Asset CleanUp).
4. Host fonts locally with font-display: swap instead of pulling from Google Fonts at runtime.

For INP:

1. Cut JavaScript, every chat widget, heatmap, and redundant pixel competes with your visitor's taps. Delay third-party scripts until interaction.
2. Audit the page builder and heavy interactive plugins; on key landing pages, less machinery = faster response.

For CLS:

1. Set explicit width/height on all images and embeds.
2. Reserve space for banners, ads, and cookie notices instead of letting them inject and shove.
3. Preload fonts so text doesn't reflow when they arrive.

Then wait for the 28-day field window to roll over, and track it in Search Console's Core Web Vitals report rather than one-off tests.

When WordPress is the wrong tool for the job

Everything above will move most sites into the passing 44%. But there's a version of this problem money-spending marketers know well: you've optimised everything optimisable, and the builder-generated pages still hover at "needs improvement," because the theme and builder ship more code per page than the budget allows. Fixes can't remove weight that the architecture insists on adding.

Two structural exits. A custom WordPress theme (built lean, shipping only what each page uses) keeps your team's editing workflow and routinely turns failing scores into green across the board; for a campaign-heavy business, cheaper CPCs and better rankings pay it back on a schedule you can actually calculate. And if your highest-stakes pages are more app than page (configurators, quote engines, funnels with logic), a custom-built front end gives you performance as a design decision instead of a rescue mission. We build both; a CWV audit against your ad spend will tell you whether either pays for itself, and we'll show the arithmetic rather than the adjectives.

Get your field data read properly

We'll audit your real-user CWV, rank the fixes by impact against your traffic and ad spend, and tell you whether optimisation gets you to green or whether you're paying an architecture tax. Fast pages, cheaper clicks, higher rankings; that's the whole pitch.

May the Code Be With You.

---

WordPress Pro builds, fixes, and maintains WordPress sites, and builds custom solutions for businesses that have outgrown them. [Book a Core Web Vitals audit →]