Core Web Vitals WordPress scores, and why yours might be failing in 2026
If your Core Web Vitals WordPress scores are sitting in the red, you’re not alone, and in 2026 the metric tripping up most sites is INP. Google’s three checks are simple on paper: how fast the main content loads (LCP), how quickly the page responds when someone taps or clicks (INP), and how much the layout jumps around while it loads (CLS). Get them green and you’ve got a faster site that Google’s ranking systems reward. Get them wrong and you’re slower than the shop next door, which on mobile is where most Australian customers find you.
Passing Core Web Vitals isn’t about chasing a perfect 100. It’s about getting three real-user numbers into Google’s “good” range and keeping them there.
MyWebs Agency
What counts as a good score?
Here are the numbers Google actually grades you on, taken straight from Google Search Central. They’re measured at the 75th percentile of real visits, so one fast test on your own fast laptop doesn’t count. Your slowest quarter of visitors do.
| Metric | What it measures | Good | Needs work |
|---|---|---|---|
| LCP | Time for the biggest thing on screen to load | Under 2.5s | Over 4s |
| INP | How fast the page reacts to a tap or click | Under 200ms | Over 500ms |
| CLS | How much the layout shifts while loading | Under 0.1 | Over 0.25 |
Why INP is the one catching people out
INP replaced the old First Input Delay metric back in March 2024, and it’s a much tougher test. Where the old metric only measured the very first tap, INP looks at how responsive your page is across every interaction, all the way through a visit. According to Google’s web.dev team, anything over 200 milliseconds at the 75th percentile counts as sluggish. On a typical WordPress site loaded with a page builder, a slider, a chat widget and three tracking scripts, the browser’s main thread gets clogged, and that’s exactly what blows out INP. This one catches people out because the page can look fast while still feeling slow to touch.
- Page builders. Elementor and Divi add a lot of CSS and JavaScript per page.
- Too many plugins. Each one can load its own scripts on every page, even where it isn’t used.
- Third-party scripts. Chat widgets, pop-ups, heat maps and ad pixels all run on the main thread.
- Huge images. A 3MB hero photo straight off a phone is the classic LCP killer.
- Run PageSpeed Insights on your three busiest pages.
- Open the Core Web Vitals report in Search Console for the real-user picture.
- Note which metric fails most: usually INP on mobile.
- Fix the cheap wins first, then tackle the script bloat.
Worth saying plainly: Core Web Vitals are a real ranking input, but they’re not magic. Google has been clear that great content still beats a fast empty page. We saw this play out after the May 2026 Google core update, where the sites that held their rankings tended to be both genuinely useful and quick on mobile. Speed is the tie-breaker, not the whole game.
Test on a mid-range Android over 4G, not your office fibre. That’s closer to how your customers actually load the site.
MyWebs Agency
The 5 fixes to pass Core Web Vitals WordPress checks
You don’t need to rebuild the site. Most sites pass their Core Web Vitals WordPress checks after five practical changes, roughly in this order of effort versus payoff.
1. Fix LCP first: images and caching
LCP is almost always your largest image. Compress and convert hero images to WebP, set proper width and height, and serve them in the right size for the device. Then add a caching plugin so pages don’t get rebuilt on every visit. We reach for WP Rocket on most builds, or the free WP Super Cache with ShortPixel for image compression. This one change alone often pulls LCP from 4 seconds down under 2.5.
2. Cut the JavaScript to fix INP
INP lives and dies on JavaScript. Audit your plugins and remove anything you don’t actually use, because every active plugin can load scripts site-wide. Defer or delay non-critical scripts so they don’t block the first tap, and use a plugin like Perfmatters or the script controls in WP Rocket to stop things like chat widgets and tracking pixels loading until the user interacts. For deeper INP work, web.dev’s optimisation guide is the practical reference our developers use.
3. Stop the layout jumping (CLS)
CLS is the easiest to fix and the most annoying to live with. The usual culprits are images and ads without set dimensions, web fonts that swap in late, and cookie banners that push everything down. Set width and height on every image, reserve space for embeds and ads, and load fonts with font-display set to swap. Most sites get CLS under 0.1 in an afternoon once you know where the jumps come from.
4. Rethink the page builder
This is the unpopular one. Heavy page builders are the single biggest cause of bloated WordPress pages we see. You don’t always have to rip it out, but turning off unused modules, avoiding nested sections, and using the block editor for simple pages makes a real difference. On new builds we often skip the heavy builder entirely and use a lightweight theme, which is part of how we keep our WordPress development projects fast from day one.
5. Get hosting that isn’t holding you back
Cheap shared hosting where a thousand sites fight over one server will undo a lot of your speed work. A slow server response time (TTFB) drags LCP down before your page even starts rendering. Decent web hosting in Australia, ideally with servers in Sydney or Melbourne so the data travels less distance, plus a CDN for images, gives every other fix a faster foundation to work on.
Is it worth the effort for a small business?
Yes, especially on mobile. Better Core Web Vitals WordPress scores mean a faster site that holds more visitors, converts more enquiries, and gives Google one less reason to rank the competitor above you. For a cafe, a tradie or a clinic where most traffic comes from a phone search on the go, a page that loads quickly and reacts the instant someone taps “Book” or “Call” is money. You can chase this yourself with the free tools below, or hand it to us and get on with running the business. Our SEO and performance team does this every week.
Frequently asked questions
What are good Core Web Vitals scores in 2026?
LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, all measured at the 75th percentile of real visits. Those are Google’s own “good” thresholds and they haven’t changed for 2026.
Why is my WordPress site failing INP?
Almost always too much JavaScript. Page builders, a long list of plugins, and third-party scripts like chat widgets and tracking pixels clog the browser’s main thread, so the page is slow to react when a visitor taps or clicks.
Do Core Web Vitals actually affect Google rankings?
Yes. Google confirms Core Web Vitals are used by its ranking systems. They won’t outrank genuinely better content on their own, but between two similar pages, the faster one tends to win.
How long does it take to pass Core Web Vitals on WordPress?
Caching and image fixes can show up within days. INP work that needs script and plugin changes takes longer to confirm, because Google uses 28 days of real-user data, so allow a few weeks to see the report turn green.
Can I check my own Core Web Vitals for free?
Yes. Run PageSpeed Insights for a single page, and use the Core Web Vitals report in Google Search Console for the whole site’s real-user data. Both are free and don’t need a plugin.
Want to know exactly why your Core Web Vitals WordPress scores are failing and what to fix first? We’ll run a free website audit, show you your real LCP, INP and CLS numbers, and give you a plain plan to pass. Book your free audit here and we’ll take a look this week.