Blog

WordPress Speed in 2026: The Fixes That Actually Move Core Web Vitals

By Juyel Rana · November 7, 2026 · Updated November 7, 2026

WordPress Speed in 2026: The Fixes That Actually Move Core Web Vitals

Here's a number worth sitting with before you touch a single plugin: in September 2026, fewer than half of WordPress sites passed all three Core Web Vitals on mobile. 48.3%, to be exact, against 52.8% for the web as a whole. Desktop was a little kinder at 53.7%, but the gap is real, and it's been stubborn — the mobile figure barely moved between June and September.

WordPress itself isn't slow. That's the part people get wrong. The same dataset shows WordPress sites are fine once the page actually loads: 90.3% of them pass the responsiveness metric, INP. The problem is getting the page to the visitor in the first place. Only 55.4% are good on Largest Contentful Paint, and only 22.9% get the first byte back within 0.8 seconds. Slow server response is where most WordPress sites lose the race, and everything downstream inherits it.

Start with the server, not the plugins

When a site is slow, the instinct is to install something. A caching plugin, an optimizer, a minifier — ideally all three, stacked on top of each other. I've seen that stack more times than I can count, and it usually makes things worse, because three tools fighting over the same HTML is its own kind of bloat.

Start one layer down instead. Time to first byte is the metric nobody wants to talk about because you can't fix it from the WordPress dashboard alone. It's your hosting, your PHP version, and whether anything is cached before WordPress even wakes up. WordPress.org now recommends PHP 8.3 or greater, and that's not a footnote — old PHP on cheap shared hosting is the single most common reason a small business site answers slowly. If your host still has you on PHP 7.4 or 8.0, no plugin will paper over that.

Check it before you change anything. Run your homepage and one inner page through PageSpeed Insights, then open the Core Web Vitals report in Search Console and look at the field data — what real visitors experienced over the last 28 days, not what a lab test guessed in a data centre. Lab scores are useful for diagnosis. Field data is what Google actually uses. If the two disagree, trust the field data.

What WordPress 6.9 already fixed for you

Here's the good news, and the reason this post is timed the way it is: the last two years of WordPress releases have been quietly doing some of this work for you. Version 6.9, codenamed Gene, shipped on December 2, 2025, and it was the most performance-focused release in years — more than 45 performance tickets, most of them aimed at the frontend your visitors actually see.

The biggest one is also the easiest to explain. Before 6.9, WordPress loaded CSS for every registered block on every page, even if that page only used three of them. Now it loads styles only for the blocks that actually appear. One agency testing the change across 12 sites measured CSS payloads dropping about 45%, with LCP improving around 17% — their numbers, not a promise, but the direction is what core intended. The same release added fetchpriority support for scripts, moved script modules to the footer, raised the inline style limit from 20K to 40K, and stopped WP Cron from firing during page loads — cron jobs now spawn at shutdown instead of stealing time from the first byte.

Then 7.0 arrived in May 2026, and 7.1 "Mary Lou" followed on August 19. The current stable release is 7.1.4, from October 28, 2026, with 7.2 scheduled for December 8. If your site is still on 6.x, the update alone buys you real speed — but take a backup and check your plugins first, the way you would with any major release.

The usual suspects on a slow WordPress site

Once the foundation is right, the remaining slowness almost always comes from the same short list. Run through it with your own site in mind.

The page builder. This is the uncomfortable one. Elementor powers a huge share of WordPress sites, and in the September 2026 data only 36.3% of its mobile origins passed Core Web Vitals. A builder isn't automatically slow — but a page built from dozens of nested sections, each loading its own scripts and styles, usually is. If your builder pages are the slow ones and your plain pages aren't, you've found your answer. Sometimes the fix is a lighter theme, sometimes it's rebuilding the two pages that matter most and leaving the rest alone.

Images that were never resized. A 2MB hero image uploaded straight from a camera, displayed at 800 pixels wide, is still 2MB of downloading. WordPress has supported modern formats for a while now — WebP since 6.1, AVIF since 6.5 — and it lazy-loads below-the-fold images by default. The wins here are unglamorous and large: resize to the size actually displayed, serve a modern format, and let the browser skip what isn't on screen yet.

Render-blocking scripts and styles. Chat widgets, tracking pixels, social embeds, font loaders — each one small, together a queue in front of your content. Audit what's actually loading on a page and ask each script what it earns its place for. Anything that isn't needed for the first paint can wait.

Plugin sprawl. Twenty plugins that each add a little CSS and a little JavaScript add up to a lot. Deactivate what you don't use, and delete it rather than leaving it dormant. Two optimization plugins doing the same job is worse than one, and worse than none if they conflict.

A fix order that respects your time

If you only have an afternoon, do it in this order, because this is roughly the order the impact comes in:

  1. Measure first. PageSpeed Insights on your three most-visited pages, plus the Search Console Core Web Vitals report. Write the numbers down.
  2. Hosting and PHP. Confirm you're on PHP 8.3 or newer, and that full-page caching is actually running — not installed, running.
  3. Update WordPress to the current 7.1.x release, and update the theme and plugins with it.
  4. Images. Resize, modern formats, lazy loading where it isn't already happening.
  5. Trim the plugins and the builder weight on the pages that matter most.
  6. Turn on speculative loading if your setup supports it — WordPress has shipped it since 6.8, and with a moderate setting it prerenders pages when a visitor hovers a link, which makes the next click feel instant.

Then measure again, on the same pages, and compare field data after a few weeks. Core Web Vitals are 28-day rolling numbers, so don't expect the Search Console report to change overnight.

What not to chase

Two things worth saying plainly. First, a perfect lab score is not the goal. A page can score 100 in a lab test and still fail in the field if your real visitors are on slow phones and slower connections. Optimize for the field data, not the screenshot.

Second, speed is a ranking input, not a ranking strategy. A fast page with nothing useful on it still ranks nowhere. What speed does is stop your content from being held back — and right now, with AI Overviews answering questions above the results and citations going to pages that load cleanly and read clearly, a fast, quotable page is worth more than it was two years ago. Speed doesn't replace the work. It lets the work be seen.

Keep reading on heyjuyel.com

Sources

Want help making your site faster?

If your WordPress site feels slow and you're not sure whether it's the hosting, the theme, or the plugin pile, that's the kind of thing I sort out for clients. Get a free SEO audit and I'll look at what's actually holding your pages back.