Core Web Vitals: understanding and passing Google's metrics
LCP, INP, CLS: what Core Web Vitals measure, why they matter for your SEO and how to fix them in practice on your website.
Contents 9 sections
Google measures the real experience of your visitors, not just the presence of keywords on your pages. Core Web Vitals are the three indicators it uses to do so.
The good news: they can be fixed, and once fixed, they no longer degrade if your website is well built.
What Core Web Vitals are
Three metrics, each measuring a different aspect of the user experience.
LCP — Largest Contentful Paint
The time needed to display the largest visible element of the page — usually a banner image or a large heading.
Target: under 2.5 seconds.
LCP is the indicator your visitors feel most directly: it is the moment the page seems “loaded”.
INP — Interaction to Next Paint
The delay between a user action (click, tap) and the visible reaction of the page.
Target: under 200 milliseconds.
A high INP gives the impression of a sluggish website: you click and nothing happens for a second.
CLS — Cumulative Layout Shift
The amount of unexpected visual shifting during loading.
Target: under 0.1.
You know this phenomenon: you are about to click and an element suddenly moves. It is frustrating and can make you click in the wrong place.
Why it matters for your SEO
Google has included Core Web Vitals as a ranking factor since 2021. The impact is real but secondary: mediocre content will not rank well just because the website is fast.
On the other hand, with equivalent content quality, a website that passes its Core Web Vitals ranks better than one that fails them. Above all, a fast website converts much better: that is where the impact on your revenue is most direct.
How to measure
With real data (what Google uses)
- Search Console » Core Web Vitals report — shows the status of your pages based on data from your real visitors, over the last 28 days.
- Chrome User Experience Report — aggregated data from all Chrome users.
In the lab (for diagnosis)
- PageSpeed Insights — combines real data and analysis under controlled conditions.
- Lighthouse (built into Chrome) — detailed analysis with recommendations.
- WebPageTest — advanced simulation, with the device and network of your choice.
Always test in mobile mode. It is what Google uses as the reference, and it is where problems show up.
Fixing LCP
LCP depends on four factors: server response time, resource load time, render time and element display delay.
Concrete actions
- Optimise the main image. Convert to WebP, compress, and above all do not load a 4000-pixel image for an 800-pixel display.
- Preload the LCP image. The
<link rel="preload">tag on the main image can save several hundred milliseconds. - Improve server response time. A static website responds in a few milliseconds; a poorly configured CMS can take more than a second.
- Eliminate render-blocking resources. CSS and JavaScript that block rendering directly delay LCP.
- Use a CDN. For a spread-out audience, a delivery network brings the content closer to your visitors.
Fixing INP
INP measures responsiveness. It mainly depends on the JavaScript being run.
Concrete actions
- Reduce JavaScript. This is the main lever. Audit the scripts loaded and remove anything that is not essential.
- Defer non-critical scripts. Chat, widgets, marketing scripts: load them after the main content, or on click.
- Break up long tasks. A script that blocks the main thread for 500 ms makes the page unresponsive. Split it up.
- Avoid costly event handlers. A
scrolllistener that recalculates the layout on every movement makes responsiveness drop.
Fixing CLS
CLS almost always comes from resources loaded without reserved dimensions.
Concrete actions
- Always set
widthandheighton images. The browser then reserves the space even before the image arrives. - Reserve space for ads and embeds. A widget inserted after loading shifts everything below it.
- Watch out for fonts. A font that loads late and changes the text metrics shifts the layout. Use
font-display: swapand fonts with similar metrics. - Do not inject content above existing content. An announcement banner inserted at the top of the page pushes everything down.
- Use
aspect-ratioin CSS for media containers.
The case of static websites
A statically generated website almost always passes its Core Web Vitals by design:
- LCP — the HTML is served immediately, without querying a database.
- INP — very little JavaScript runs at load time.
- CLS — no dynamic content injection.
It is one of the reasons we favour this architecture: performance is not extra work, it is built in.
The order of priority
If you need to work on an existing website, tackle things in this order:
- Images — maximum impact on LCP, minimum effort.
- Third-party JavaScript — maximum impact on INP.
- Media dimensions — maximum impact on CLS.
- Hosting — latency gain.
- Fonts — additional gain.
Most websites turn green with the first three areas alone.
In short
Core Web Vitals measure what your visitors really feel: display speed (LCP), responsiveness (INP) and stability (CLS). They influence your ranking at the margin, but your conversion rate directly.
Want to know where your website stands? We carry out a complete Core Web Vitals audit with a correction plan prioritised by impact.