
Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor: how fast the main content shows up, how quickly the page reacts when someone taps, and whether things jump around while loading. This guide is for owners and managers who need to read a report, know whether the numbers are a problem, and brief whoever fixes the site. No coding needed to follow it.
The three Core Web Vitals
Google’s own definition, on web.dev, lists three metrics and the “good” target for each.
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP, Largest Contentful Paint | How long until the biggest thing on screen (often a hero image or headline) appears | 2.5 s or less | up to 4 s | over 4 s |
| INP, Interaction to Next Paint | How long the page takes to visibly respond after a tap, click or key press | 200 ms or less | up to 500 ms | over 500 ms |
| CLS, Cumulative Layout Shift | How much visible content moves unexpectedly | 0.1 or less | up to 0.25 | over 0.25 |
The “needs improvement” and “poor” bands come from the individual metric pages on web.dev for LCP, INP and CLS. INP replaced the old First Input Delay metric in 2024, so any guide that still tells you to chase FID is out of date.
A page passes when all three are in the “good” range at the 75th percentile. That means three out of four real visits have to be at least that good, and mobile and desktop are judged separately. One lucky fast load on your own laptop proves nothing.
What each one feels like to a visitor
LCP is the blank-screen wait. The element that counts is usually the largest image, video poster, or block of text in view. If your homepage opens with a big slider image, that image is your LCP.
INP is the dead-button feeling. You tap “Add to basket” or open the menu and nothing happens for a beat. Google measures from the tap until the next frame is painted, and it looks across the whole visit, not just the first tap.
CLS is the misclick. You go to tap a link and a banner loads above it, pushing everything down, so you hit the wrong thing. Only unexpected movement counts. Shifts right after your own tap are generally excluded.
Do Core Web Vitals affect rankings?
Google’s page on Core Web Vitals and Search says it highly recommends good scores for success in Search and ties them to its page experience aims. It does not say how much weight they carry, and it frames them as one part of the picture.
Our reading, which is an opinion and not a Google statement: a slow site will not rank well just because its content is good, and a fast site will not rank well because its vitals are green. Relevance and quality come first. The better argument for fixing vitals is commercial. Visitors who wait, mistap or get frustrated leave, and that costs you enquiries and sales regardless of rankings. If your pages already get visits but few enquiries, see why a website gets visitors but no enquiries.
How to check your site for free
Two kinds of data exist, and mixing them up causes most arguments between owners and agencies.
- Field data comes from real visitors, via the Chrome User Experience Report. This is what Google uses. You see it in PageSpeed Insights (top section) and in the Core Web Vitals report in Search Console.
- Lab data comes from a simulated test, for example Lighthouse. It is handy while fixing things, but web.dev says it does not replace field measurement. Lighthouse cannot measure INP at all, because a simulated load has no real taps; it uses a stand-in called Total Blocking Time.
So run your key pages through PageSpeed Insights: home page, a service or category page, a product or article. Look at the field data first. If it says “not enough data”, the page has too little traffic for a field score, and the lab results are your guide until it grows.
Test on mobile. Most small-business sites pass easily on a desktop connection and struggle on a phone.
What usually fails, and the fix for each
Slow LCP
web.dev splits LCP into four parts: server response time, the delay before the image starts downloading, the download itself, and the delay before it is painted. Typical fixes:
- Make the hero image discoverable in the page HTML, not hidden in CSS or loaded by script.
- Never lazy-load the main image.
loading="lazy"on the LCP image delays it. - Mark the one likely LCP image with
fetchpriority="high". Use it on one or two images only, or it stops meaning anything. - Shrink the file. A 2 MB photo straight from a camera is the usual culprit; see our guide to WordPress image SEO, compression and WebP.
- Check hosting. If the server takes ages to reply, no image trick will save you.
Poor INP
Slow responses come from a busy main thread: too much JavaScript running, long tasks, heavy event handlers, a very large page structure. web.dev’s advice is to load less script, break long tasks into smaller pieces, and do only the visual update inside the click handler. For owners, the practical version is a script audit. Chat widgets, review pop-ups, tag managers, sliders and A/B testing tools all add work. Remove what nobody uses, then retest. On Shopify this is the same story as app bloat.
High CLS
web.dev names four usual causes, and each has a cheap fix:
- Images without dimensions. Always include
widthandheightattributes, or reserve space with CSSaspect-ratio. - Ads, embeds and iframes. Reserve a box for them.
- Banners and pop-ups injected late. Reserve space or overlay them so they do not push content.
- Web fonts swapping in. Preload important fonts and choose a sensible fallback.
CLS is often the easiest of the three to fix, so start there if you want a quick win.
Core Web Vitals on WordPress and Shopify
These platforms are not the problem on their own; the theme, plugins and apps you stack on top are. A lean WordPress theme with a decent host and compressed images passes more often than a page-builder theme with fifteen plugins. A Shopify store passes or fails largely on theme code, image handling and installed apps. If you run Shopify, our Liquid speed optimisation guide covers the theme side, and the more technical Core Web Vitals and Lighthouse piece covers LCP in depth.
A sensible order of work
| Step | Why first |
|---|---|
| 1. Test five key pages on mobile | Measures reality before spending money |
| 2. Fix image sizes and add width/height | Cheap, helps LCP and CLS together |
| 3. Remove unused plugins, apps and scripts | Helps LCP and INP, and cuts maintenance |
| 4. Check hosting response time | Slow servers cap everything else |
| 5. Retest and log the change | Proves the work paid off |
Fixes show up in field data slowly, because that data is built from real visits over time. Do not panic if a report is unchanged the week after you fix something.
When not to bother: a small brochure site with five pages that already passes. Spend the effort on clearer service pages instead. If you are paying for speed work, ask what metric moved, in field data, and by how much.
Frequently Asked Questions
What is a good Core Web Vitals score?
A page passes when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less, judged at the 75th percentile of real visits. Mobile and desktop are assessed separately.
Why does PageSpeed Insights show two different results?
The top section is field data from real visitors, which is what Google uses. The lower section is a lab test on one simulated device. They often disagree, and the field data wins.
Is Lighthouse the same as Core Web Vitals?
No. Lighthouse is a lab tool and cannot measure INP. It is useful for finding problems, but a green Lighthouse score does not guarantee passing field data.
How long do fixes take to show up?
Lab tests change immediately. Field data lags because it reflects real visits over a period, so give it a few weeks before judging.
Do I need a developer to fix them?
Image sizes and unused plugins you can often handle yourself. Script, theme and server work is easier with a developer, which is when a brief based on your PageSpeed Insights results helps.
Conclusion
Core Web Vitals are a practical checklist, not a mystery. Measure real visits first, fix images and layout shifts, trim scripts, check hosting, and retest. Keep expectations honest: good vitals support your SEO and your conversion rate, they do not replace good content. If you would like help with this, CYPHEX can plan and deliver it for you, with one project lead as your contact. You can also read about our web development and WordPress and WooCommerce services.
Stock photography provided by Pexels under the Pexels License.
