Core Web Vitals

What Are Core Web Vitals?

Google boils down how a page feels to use into three numbers. Loading speed. Click responsiveness. Whether the layout holds still while you're trying to read it.

These aren't lab numbers. Google pulls them from real visits to real pages, out in the wild, not a fast connection in a testing lab somewhere.

That real-user dataset even has a name: the Chrome User Experience Report, or CrUX, built from actual Chrome sessions across millions of real devices and connections.

A good score means real visitors got a fast, stable page. A bad one means they didn't. It doesn't matter how well the site performed on the developer's own machine.

There's a ranking angle too. Core Web Vitals feed into Google's page experience signals. A slow or jumpy page doesn't just annoy whoever lands on it, it loses search visibility too.

Here's the part that trips people up. A page can ace a one-time lab test and still feel awful in someone's actual hands. Try it on a mid-range phone with spotty Wi-Fi and the cracks show fast. Core Web Vitals exist to catch exactly that: the real-world version, not the demo.

What Are the Three Core Web Vitals?

The three Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. One covers loading, one covers responsiveness, one covers stability.

One more thing worth knowing: Google doesn't grade a page on its best moment. Each vital gets scored at the 75th percentile of real visits, which means a page only passes if three out of four visitors actually got that experience, not just the lucky ones on a fast connection.

1. Largest Contentful Paint (LCP)

Largest Contentful Paint is a clock on the biggest thing you see on the page, usually a hero image or headline. Under 2.5 seconds, good. Between 2.5 and 4, shaky. Past 4 seconds, most visitors are already gone.

Usually it's a slow server response, or a hero image nobody bothered to optimize. Save a product photo at full resolution instead of compressing it for the web, and that alone can cost a full second.

2. Interaction to Next Paint (INP)

How fast does the page respond once someone actually clicks something? That is what INP measures, checked across every interaction on the page rather than just the first one.

Two hundred milliseconds or less reads as instant. Cross 500 and the page starts to feel broken even while it is technically still working.

Heavy JavaScript running on the main thread is what usually gets in the way. A button click has to wait behind whatever script the browser's already running. All the user sees is a page that ignored them.

3. Cumulative Layout Shift (CLS)

Ever click a button and hit something else instead because an ad or an image loaded late and shoved everything down? That's the Cumulative Layout Shift.

A CLS score under 0.1 means the page mostly holds still. Above 0.25, and content is visibly shifting enough to cause real mis-clicks.

Images and ads without a reserved size on the page are the most common cause. Reserve the space before the content loads, and the shift never happens in the first place.

Why Do Core Web Vitals Matter?

Two different audiences care about these numbers, for two different reasons.

Search rankings are one. Core Web Vitals count toward Google's page experience signals, so a slow, jumpy page is fighting faster competitors for the same spot in results, one more factor on a long list Google already weighs.

Real visitors are the other, and honestly the bigger one. A page that loads in 2.5 seconds and holds still keeps people around. One that lags and jumps loses them before they ever see what the page was actually for.

That gap turns into a business number eventually. Call it a bounce, an abandoned cart, or just a visitor who quietly clicked over to a competitor instead.

Google Search Console and PageSpeed Insights pull all three straight from real visitor data. No need to guess which one's dragging a page down.

Search Console even breaks it down by URL group, so it's possible to see that only the checkout flow is failing CLS while the rest of the site passes clean.

Fix the three vitals and you are not just chasing a ranking signal. You are fixing the actual experience Google was trying to measure in the first place.