What Core Web Vitals actually measure
Core Web Vitals are a set of three measurements Google uses to assess the real-world experience of loading and using a webpage. They’re not abstract developer metrics — they measure things your visitors feel directly, even if they’d never describe them in technical terms.
<aside=“Google confirmed in 2021 that Core Web Vitals are now a ranking signal. A poor score doesn’t just hurt the experience — it actively suppresses your position in search results.”>
The practical implication: two otherwise identical pages, one fast and one slow, will not rank equally. The fast one gets the edge. At competitive keyword levels, that edge is the difference between page one and page two.
Why LCP matters most for first impressions
Largest Contentful Paint measures the time from when a user navigates to your page until the largest visible element — usually a hero image or headline — appears on screen. The target is under 2.5 seconds.
2.5s
the LCP threshold — pages loading their main content within this window are rated ‘Good’ by Google
Most poorly optimised sites fail this metric because of uncompressed images, render-blocking scripts, or web fonts that delay text rendering. Each of these is fixable — but they need to be identified first.
When a visitor waits more than three seconds for a page to load, the data is clear: around half of them leave. They don’t wait. They don’t give you the benefit of the doubt. They hit the back button and click the next result.
CLS and the trust problem
Cumulative Layout Shift captures something most users experience but few can name: the frustration of a page that reorganises itself as it loads. A button you’re about to click moves. A paragraph you’re reading shifts down. An image appears and pushes everything else away.
0.1
the CLS threshold — a score above this means your page is visually unstable during load
CLS problems usually come from images without declared dimensions, late-loading ads or embeds, and dynamically injected content. The fix is almost always straightforward once the problem is found — but it requires someone looking for it.
<quote=“Layout instability is a trust problem before it’s a technical problem. A page that jumps around feels unfinished — and visitors associate that with the business behind it.”>
INP — the newest metric and why it matters for conversion
Interaction to Next Paint replaced First Input Delay in 2024. It measures how quickly your page responds when a user interacts with it — clicking a button, filling a form field, opening a menu. The target is under 200 milliseconds.
200ms
the INP threshold — beyond this, interactions feel noticeably sluggish and users begin to lose confidence in the page
A slow INP score is particularly damaging on pages where you need a visitor to take action — contact forms, quote requests, product pages. The moment a button feels unresponsive, trust in the whole experience erodes.
What a poor score is actually costing you
Key takeaway
Every visitor who leaves because your site is slow or unstable is a visitor you paid to acquire — through SEO, advertising, or word of mouth — who left without converting. The cost of a slow site is not just ranking suppression; it’s wasted acquisition spend.
The ROI of performance work is often clearer than other digital investments. If your site currently converts 2% of visitors, and a performance overhaul improves that to 3%, you’ve increased revenue by 50% from the same traffic — without spending another pound on advertising.
How to check your own scores
- Google PageSpeed Insights Go to pagespeed.web.dev and enter your URL. Focus on the mobile results — that’s where scores tend to be weakest and where most of your traffic arrives. The report gives you a score for each Core Web Vital plus specific recommendations.
- Google Search Console If Search Console is set up for your domain, the Core Web Vitals report shows which URLs are rated Poor, Needs Improvement, or Good across your actual users — not just a lab simulation.
- Chrome DevTools Press F12, navigate to the Lighthouse tab, and run a full audit. This works on any page, including pages that aren’t yet publicly accessible — useful for testing before launch.
Getting from poor to good
Most sites can move from Poor to Good on Core Web Vitals with targeted technical work — typically image optimisation, script management, and font loading strategy. A full site rebuild isn’t usually necessary unless the underlying platform is fundamentally unsuited to performance.
| Metric | Common cause of failure | Typical fix |
|---|---|---|
| LCP | Uncompressed hero images | WebP format, explicit dimensions, preload hint |
| LCP | Render-blocking scripts | Defer or async loading, critical CSS inline |
| CLS | Images without width/height | Explicit dimension attributes on all images |
| CLS | Late-loading third-party embeds | Placeholder dimensions, lazy loading |
| INP | Heavy JavaScript on interaction | Code-split, debounce, remove unused scripts |
Ready to act on this?
Get a Core Web Vitals audit
We assess your current scores, identify the specific causes, and fix them — typically within two weeks. No jargon, no retainer, clear results.