A slow site does not lose points: it loses customers before it loads. Core Web Vitals are how Google measures that experience, and they can be checked in five minutes. Here is what they mean and how to fix them.
What are Core Web Vitals and what does each one measure?
Three different things: how long until it appears, how long until it responds, and how much it moves.
They are not one global score but three independent signals. A page can load fast and still fail if the buttons shift while the user is trying to tap them.
| Metric | What it measures | Good threshold |
|---|---|---|
| LCP | When the largest element on screen appears | Under 2.5 s |
| INP | How long the page takes to respond to an interaction | Under 200 ms |
| CLS | How much content shifts while loading | Under 0.1 |
Why do they matter for the business, not just for Google?
Because a user who waits leaves, and the one who leaves does not come back through SEO.
Google uses these as experience signals, but the real impact comes earlier: every second of waiting on mobile turns into abandoned carts and unsent forms.
In e-commerce the effect is direct; in services it is quieter — people simply pick the competitor whose page opened first.
How do you measure them properly?
With field data, not a single lab run on your own computer.
PageSpeed Insights shows both: what happens on your machine and what happens to real users over 28 days. Search Console groups those same metrics by URL groups, which is where the pattern shows.
Rule of thumb: when the lab says green and the field says red, trust the field.
How do you improve each metric?
With five fixes that resolve most cases, in this order.
You rarely need to rewrite the site. In practice, these changes move the needle:
- Compress and serve images in modern formats, with width and height declared.
- Reserve space for banners, ads and fonts so nothing jumps (CLS).
- Lazy-load anything below the first screen.
- Cut and group third-party scripts: every tracking pixel costs interaction (INP).
- Turn on caching and a CDN, and check server response time.
What if the site runs on WordPress?
Eighty per cent of the problem is usually accumulated plugins and a heavy theme.
Before buying an optimisation plugin, audit what the page is actually loading: page builders with dozens of modules, sliders nobody uses, and scripts from old campaigns.
A light theme with proper caching usually beats a heavy theme with three speed plugins layered on top.
When is it time to call a specialist?
When images and caching are already handled and field data is still red.
At that point the problem is usually architectural: render-blocking resources, badly loaded fonts, heavy hydration, or a server that answers late. No plugin fixes that.
Frequently asked questions
Do Core Web Vitals affect rankings directly?
They are part of the page experience signals Google considers. They do not replace content relevance, but they break ties when several pages answer a query equally well.
What is INP and why did it replace FID?
INP measures the latency of all interactions during a visit, not just the first one. It gives a more honest picture of how responsive the page is while somebody actually uses it.
How long before improvements show in Search Console?
Field data is computed over a 28-day window, so a fix takes weeks to show fully, even when the lab test reflects it immediately.
Is buying a caching plugin enough?
It helps, but it rarely suffices. Caching speeds delivery; it does not fix heavy images, third-party scripts or layout shifts, which are common causes of poor CLS and INP.
Should I optimise for mobile or desktop?
Mobile. That is where most traffic happens and where the thresholds are missed most often, because of connection quality and device power.
Summary: what to remember
- Three separate metrics: LCP (appears), INP (responds) and CLS (does not jump).
- Trust field data from real users over a single lab run.
- Images, reserved space, lazy loading, third-party scripts and caching resolve most cases.
Is your site slow and you don't know why?
We audit performance with field data and fix the cause, not the symptom.
See our web development service
