Core Web Vitals Explained: LCP, INP, and CLS in Plain English

The three metrics, in plain English

Core Web Vitals are three specific measurements Google uses to judge how a page actually feels to use — not what it says about itself, but what happens when a real person tries to load and interact with it.

LCP (Largest Contentful Paint) measures how long it takes for the biggest visible element on the page — usually a hero image or a headline — to actually finish loading. It's a proxy for "does this page feel like it's ready yet."

INP (Interaction to Next Paint) measures the delay between a person doing something — clicking a button, tapping a menu — and the page visibly responding. This replaced an older metric called FID in 2024, and it's a better measure of actual responsiveness because it looks at every interaction on the page, not just the first one.

CLS (Cumulative Layout Shift) measures how much content unexpectedly jumps around while a page is loading. If you've ever tried to tap a button and had an ad load in above it at the last second, shifting everything down so you tapped the wrong thing — that's exactly what CLS measures.

Why Google cares about this at all

These aren't arbitrary numbers Google invented to give developers something to chase. They're a genuine, if imperfect, attempt to measure something real: whether a page is actually pleasant and functional to use, independent of how good the content on it is.

A page can have perfect content and still be a bad experience if it takes eight seconds to become usable, or if the layout keeps jumping while someone's trying to read it. Core Web Vitals are Google's way of factoring that into rankings, not just what's written on the page.

What actually counts as "good"

Google publishes specific thresholds, measured at the 75th percentile of real visits to your site:

• LCP: 2.5 seconds or less is good. Above 4 seconds is considered poor.
• INP: 200 milliseconds or less is good. Above 500 milliseconds is poor.
• CLS: A score of 0.1 or less is good. Above 0.25 is poor.

The middle ranges between those numbers are labeled "needs improvement" — not failing, but not where you want to stay either.

What actually causes each one to go bad

LCP problems are usually caused by slow server response times, render-blocking JavaScript or CSS that has to finish loading before the main content can appear, or unoptimized images that are far larger than they need to be for how they're actually displayed.

INP problems are almost always caused by JavaScript that's doing too much work on the main thread — heavy scripts, too many third-party trackers and widgets, or code that wasn't written with performance in mind, all competing for the same processing time a click needs to be handled.

CLS problems are usually caused by images or ads without a reserved size, so the browser doesn't know how much space to leave for them until they've actually loaded — at which point everything else on the page has to move to make room.

How to actually check your own numbers

Google Search Console has a Core Web Vitals report that shows real data from actual visitors to your site, not a simulated test — which matters, because real-world conditions (slower phones, patchy connections) often look worse than a clean lab test run on a fast desktop.

For a specific page, PageSpeed Insights gives you both the real-world field data and a lab-based diagnostic breakdown of exactly what's slowing that particular page down, which is more useful when you're trying to fix one specific problem rather than get a site-wide overview.

A realistic way to think about priority

Core Web Vitals are one ranking signal among many, not the single deciding factor for where you rank. But they're also not purely cosmetic — Google has confirmed they're part of the page experience signals used in ranking, and beyond rankings entirely, a page that loads slowly or jumps around while loading is going to lose visitors regardless of what Google does with it. Treating these as a real, ongoing part of technical maintenance — not a one-time fix — tends to be the difference between a site that stays fast and one that quietly degrades as more scripts and images get added over time.