Core Web Vitals: LCP, INP and CLS Explained Properly

Core Web Vitals are three metrics Google uses to measure real-world page experience: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. The “good” thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, measured on real users at the 75th percentile. They’re a genuine but modest ranking signal — and they matter for conversions regardless of ranking. This guide explains each vital properly and how to improve it.

What are Core Web Vitals?

Core Web Vitals are a set of three metrics Google uses to quantify the real-world experience of loading and interacting with a web page. They’re part of Google’s broader page-experience signals and were designed to capture the aspects of user experience that frustrate people most: pages that load slowly, respond sluggishly to interaction, or shift around unexpectedly as they load. Each vital targets one of those problems with a specific, measurable metric and a clear “good” threshold.

Crucially, Google measures these on field data — real Chrome users visiting your pages — not just lab tests, and it uses the 75th percentile, meaning at least 75% of visits must meet the threshold to pass. So your typical visitor isn’t enough; your slower visitors count too.

Largest Contentful Paint (LCP): loading

LCP measures how long it takes for the largest visible content element — usually a hero image, heading or main text block — to render, marking the point where the page feels loaded to the user. Good LCP is under 2.5 seconds; poor is over 4 seconds. Slow LCP usually comes from slow servers, render-blocking resources, large unoptimised images, or slow-loading fonts.

To improve LCP: speed up your server response (good hosting, caching, a CDN), optimise and correctly size the largest image and serve it in a modern format like WebP, eliminate render-blocking CSS and JavaScript, and preload critical resources. The largest element should be one of the first things the browser can paint, not something waiting behind a queue of scripts.

Interaction to Next Paint (INP): responsiveness

INP measures how quickly your page responds visually after a user interacts — clicks, taps, or key presses — across the whole visit, capturing overall responsiveness. It replaced First Input Delay in March 2024 as the interactivity vital, because it measures all interactions rather than just the first, giving a truer picture of how responsive the page feels. Good INP is under 200 milliseconds; poor is over 500.

Poor INP is almost always a JavaScript problem — heavy scripts blocking the main thread so the browser can’t respond promptly to input. To improve it: reduce and break up long JavaScript tasks, defer non-essential scripts, minimise third-party code, and avoid doing heavy work in response to interactions. INP is often the hardest vital to pass on script-heavy sites, and the one where reducing JavaScript pays off most.

Cumulative Layout Shift (CLS): visual stability

CLS measures how much visible content unexpectedly shifts around as the page loads — the frustrating experience of trying to tap a button that jumps as an image or ad loads above it. It’s a unitless score; good CLS is under 0.1, poor is over 0.25. Layout shift usually comes from images and embeds without dimensions specified, dynamically injected content, or web fonts causing reflow.

To improve CLS: always specify width and height (or aspect ratio) on images and video so the browser reserves space, reserve space for ads and embeds, avoid inserting content above existing content, and handle font loading to minimise layout jumps. CLS is often the easiest vital to fix, because the causes are usually specific, identifiable elements.

How much do Core Web Vitals affect rankings?

Honestly, modestly. Core Web Vitals are a confirmed ranking signal but a lightweight one — best understood as a threshold and tiebreaker. Passing them removes a disadvantage and can tip you ahead of a comparable competitor, but great vitals won’t lift genuinely weaker content above stronger content. Don’t expect a vitals overhaul alone to transform rankings.

The stronger reason to fix them is user behaviour. Slow, unresponsive, unstable pages frustrate visitors, increase abandonment, and hurt conversions — effects that matter regardless of ranking. Treat Core Web Vitals as user-experience work that also happens to be a small ranking factor, and the investment justifies itself on conversions even before any ranking benefit.

How to measure your Core Web Vitals

Use field data (real users) for the metrics that count toward ranking, and lab data for debugging. Google Search Console’s Core Web Vitals report shows your field performance grouped by page type — the best starting point. PageSpeed Insights combines field and lab data for individual URLs. Chrome’s built-in tools and Lighthouse help you diagnose specific issues in the lab. Fix based on field data, verify improvements over the following weeks as new field data accumulates, since field metrics reflect a rolling window of real visits.

Frequently asked questions

The bottom line

Core Web Vitals measure the page experience that frustrates users most: slow loading (LCP), sluggish response (INP), and jumpy layout (CLS). Hit the thresholds — 2.5s, 200ms, 0.1 — at the 75th percentile of real users. For ranking they’re a modest threshold, but for conversions they matter more, which makes them worth fixing either way. Optimise images and server for LCP, cut JavaScript for INP, and reserve space for elements to fix CLS.

We build fast, stable sites that pass Core Web Vitals — see our web development service.

Sources

• Web Vitals — web.dev
• Chat Widgets, Pixels and Tag Managers: The Hidden Speed Bill
• Does Page Speed Affect Rankings? Separating Signal From Noise
• Does Hosting Affect SEO? What Actually Changes