To pass Core Web Vitals on WordPress, at least 75% of real visits need a good result on all three measures: loading (LCP), responsiveness (INP) and visual stability (CLS). Find out which one is failing in Google Search Console, then fix its usual WordPress cause. That’s usually slow hosting or a heavy hero image for LCP, too much JavaScript for INP, and things that load late and push the page around for CLS.
Key takeaways
- Google judges Core Web Vitals on real visitors’ experience over 28 days, not on a single speed test.
- A group of pages takes the status of its worst metric, so one failing measure fails the lot.
- Fix the metric that’s failing. A better PageSpeed score on a metric that already passes changes nothing.
- Hosting decides much of LCP. Plugins, page builders and third-party scripts decide most of INP and CLS.
- After a fix, expect up to 28 days before Search Console shows the change.
What counts as passing Core Web Vitals?
Google measures three things, and sets a “good” line for each (web.dev):
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How fast the main content appears | 2.5 seconds or less | Over 4 seconds |
| Interaction to Next Paint (INP) | How fast the page responds to a tap or click | 200 milliseconds or less | Over 500 milliseconds |
| Cumulative Layout Shift (CLS) | How much the page jumps around as it loads | 0.1 or less | Over 0.25 |
Each is measured at the 75th percentile of real visits. In plain terms, three out of four visitors need a good experience. INP replaced the older First Input Delay measure in March 2024, so older guides that talk about FID are out of date.
Do Core Web Vitals affect Google rankings?
They’re part of it, but not the biggest part. Google “highly” recommends good Core Web Vitals and says they align with what its core ranking systems seek to reward (Google Search Central). Useful, relevant content still comes first.
The stronger reason to care is your customers. A page that loads slowly or jumps as someone goes to tap a button loses enquiries, whatever Google thinks.
Where do I check whether my WordPress site passes?
Start with the Core Web Vitals report in Google Search Console. It uses data from real Chrome users and groups pages that behave alike. Google says a group “defaults to the slowest status” of its metrics for that device type (Search Console Help). Check mobile and desktop separately, because they’re judged separately.
Small sites often don’t have enough traffic for page-level data. Search Console then falls back to one result for the whole site, or shows nothing at all.
Then use PageSpeed Insights on one page from a failing group. The top section shows real-user data, if there’s enough. The lower section is a lab test, which is useful for finding causes but isn’t what Google judges you on. Our website speed test guide explains how to read each tool’s results.
How do I fix a slow LCP on WordPress?
Google’s guide splits LCP into four parts (web.dev). PageSpeed Insights shows which part is slow, and each part has a usual WordPress cause:
Google’s rule of thumb is that server response and image download should each take about 40% of LCP. The delays in parts 2 and 4 should each be under 10%. Two WordPress specifics matter here:
- Don’t lazy-load the hero image. Google says to “never lazy-load your LCP image”. Since version 6.3, WordPress adds a high-priority hint to the image it thinks is the main one and skips lazy-loading it (Make WordPress Core). Page builders and optimisation plugins can override that, so check.
- Sliders are a common culprit. A slider often loads several large images and a script before the first slide shows. A single static image usually loads faster.
Image sizes are covered in detail in our guide to optimising images for the web.
How do I fix poor INP on WordPress?
INP measures the wait between a tap and the page visibly responding. It’s mostly about JavaScript. While the browser is busy running scripts, it can’t respond to the visitor (web.dev).
In our experience, the usual WordPress causes are:
- chat widgets, pop-ups, review badges and tracking tags that all load on every page
- page builders with many nested sections, which make a very large page for the browser to update
- plugins that load their scripts site-wide when they’re only needed on one page
- mega menus, product filters and sliders driven by heavy scripts
The fixes are mostly subtraction. Remove plugins and tags you don’t use. Load the rest only on the pages that need them. Delay chat and marketing scripts until after the page has loaded, and simplify pages with deep layers of builder sections. These changes need care, so test forms and checkout afterwards.
How do I fix layout shift (CLS) on WordPress?
Layout shift happens when something loads late and pushes content down. Google lists the usual causes as images and embeds without set dimensions, content injected after load, and web fonts that swap in (web.dev). On WordPress sites, we most often see:
- Cookie banners and announcement bars that appear at the top of the page after it loads. Overlay them at the bottom instead.
- Images, videos and maps without a set size. Give each one a width and height, or reserve the space with CSS, so the browser holds the gap.
- Web fonts that swap in at a different size. Use fewer fonts, preload the main one and pick a similar fallback.
- Ads and embeds that resize themselves. Reserve a fixed space for them.
I’ve fixed it. Why does Search Console still say “Poor”?
Because the data runs over 28 days. Real-user data is a rolling picture, so old slow visits take time to drop out. In the Core Web Vitals report, open the issue and start validation. Google then monitors the issue for 28 days and marks it fixed if no pages show it in that window.
Starting validation doesn’t speed up the data. It just tells you when the fix has held. Meanwhile, use PageSpeed Insights’ lab test to confirm the change worked.
Where do hosting and maintenance help?
Hosting sets the floor for LCP. If the server is slow, nothing on the page can make up for it. Distance adds delay too: one recent measurement put Sydney to Los Angeles at 136.6 milliseconds per round trip, against 9.7 milliseconds from Sydney to Melbourne (HATSnet). Our WordPress hosting in Australia runs in NEXTDC data centres in Brisbane and Melbourne.
Mobile matters most. Mobile and desktop each make up just under half of Australian web traffic (StatCounter). In our experience, phones are where most sites fail. Our guide to a mobile friendly website covers the other problems phones show up.
Maintenance keeps a site passing. Every new plugin, tag or page builder update can add weight. Our website speed and improvement work fixes the cause, not just the score. Our website maintenance plans then keep the site updated, and Elite adds database and image optimisation. For a wider list of fixes, see our guide on how to speed up WordPress.
Frequently asked questions
Why does PageSpeed Insights give a different result each time?
The lab test runs once, on a simulated phone and network, so results vary from run to run. The real-user data at the top changes slowly, because it covers 28 days of visits. Judge progress by the real-user data, and use the lab test to find causes.
Can a plugin fix Core Web Vitals on its own?
A caching or optimisation plugin can help LCP, but it can’t fix slow hosting, a heavy page builder or too many third-party scripts. Some optimisation settings also break layouts or forms. Fix the cause, and test the site after each change.
Is Elementor bad for Core Web Vitals?
Not by itself, but page builders make it easy to build heavy pages. Deeply nested sections, sliders, animations and many widgets on one page all add work. A lean layout built with the same builder can pass comfortably.
My site has no Core Web Vitals data. Is that a problem?
No. It means Google doesn’t have enough real visits to report on. Use PageSpeed Insights’ lab test as a guide, and aim for the same good thresholds. As traffic grows, field data will appear.
Which Core Web Vital should I fix first?
The one marked Poor in Search Console on mobile. A page group takes the status of its worst metric, so fixing a failing metric moves the group. Improving one that already passes won’t change its status.
Sources
- Web Vitals, web.dev
- Understanding Core Web Vitals and Google search results, Google Search Central
- Core Web Vitals report, Search Console Help
- Optimize Largest Contentful Paint, web.dev
- Image performance enhancements in WordPress 6.3, Make WordPress Core, July 2023
- Optimize Interaction to Next Paint, web.dev
- Optimize Cumulative Layout Shift, web.dev
- Sydney to Los Angeles round-trip latency, HATSnet, October 2026
- Desktop vs mobile vs tablet market share, Australia, StatCounter, October 2026