Google made Core Web Vitals a ranking signal in 2021. Five years on, most sites still fail at least one metric — yet the impact on rankings isn't always what you'd expect. Understanding which metrics matter most, and why, changes how you prioritise your optimisation work.
The three metrics that actually count
Core Web Vitals measure three things: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. Google uses field data from the Chrome User Experience Report (CrUX) to score your site, not lab data from a synthetic test.
A green Lighthouse score does not mean you pass Core Web Vitals. Google's ranking signal is based on CrUX field data — anonymised measurements from real Chrome users. A page needs 75% or more of real visits to register as "Good" for each metric.
Measure your real performance first
Don't guess at your CWV status. Run a test against real CrUX field data before spending engineering time on optimisations that may not be necessary.
Analyze page performance, loading speed, and Core Web Vitals with actionable recommendations to improve page experience. Uses real CrUX field data — not just lab scores.
LCP: the metric that moves rankings most
Among the three, LCP tends to have the strongest correlation with ranking changes when you cross thresholds. The "Good" threshold is under 2.5 seconds at the 75th percentile. Fix TTFB first — if your server takes 800ms to respond, nothing else you do will push LCP under 2.5 seconds on a typical 4G connection.
Practical LCP wins
- →Add <link rel="preload"> for your LCP image — don't let the browser discover it by parsing HTML
- →Use a CDN with edge caching to bring TTFB under 200ms globally
- →Serve images in WebP or AVIF — same quality, 30–50% smaller file size
- →Set explicit width and height attributes on images to prevent layout shifts during load
- →Avoid lazy-loading the LCP element — it defeats the purpose entirely
INP replaced FID — and it's harder to pass
In March 2024, Google retired First Input Delay (FID) and replaced it with Interaction to Next Paint (INP). FID only measured the first interaction; INP measures every interaction throughout the page visit and reports the worst one. Most sites that were comfortably passing FID found themselves failing INP.
INP failures often come from long tasks on the main thread: third-party scripts (chat widgets, heatmap tools, A/B testing libraries) that block interaction handling. Use Chrome DevTools Performance panel to identify which scripts are scheduling long tasks.
CLS: easier to fix, often overlooked
CLS is usually the quickest win of the three. Add explicit dimensions to all images and iframes. Reserve space for any element that loads asynchronously. Use font-display: swap or optional to prevent font-induced layout shifts.
Threshold crossing matters more than marginal improvement
Google's ranking signal is threshold-based, not continuous. Moving from 2.6s LCP to 2.3s LCP (crossing the "Good" threshold) likely has more ranking impact than moving from 2.3s to 1.8s. Focus on getting "Poor" pages to "Needs Improvement" and "Needs Improvement" pages to "Good" — not on pushing already-passing pages further.
See exactly how Googlebot renders and evaluates your pages — including which resources are loading in a way that hurts your Core Web Vitals score.
Co-founder and CTO of SEOVentra. Builds the indexing pipelines, audit engine, and AI visibility infrastructure. Former backend engineer obsessed with making search work at scale.