What are Core Web Vitals? A plain-English explanation

Short definition

Core Web Vitals are Google's three user-experience metrics — LCP (loading), INP (responsiveness) and CLS (visual stability) — measured on real visitors and used as a ranking signal.

The short version

Core Web Vitals are three numbers Google uses to describe how a page feels to a real person: how fast the main content shows up, how quickly the page reacts when you tap or click, and how much things jump around while it loads.

Google measures these on actual Chrome visitors and uses them as a ranking signal. So they matter twice: once because a snappy page keeps users, and once because a slow one can quietly cost you search traffic.

I have chased these metrics on real projects, and the honest takeaway is this: they are a decent proxy for “does this page respect the user’s time.” That is worth optimizing for even if Google did not exist.

The three metrics

LCP, INP and CLS at a glance

LCP

Largest Contentful Paint

How fast the main content appears. Aim for under 2.5s.

INP

Interaction to Next Paint

How quickly the page reacts to a tap or click. Aim for under 200ms.

CLS

Cumulative Layout Shift

How much the layout jumps while loading. Aim for under 0.1.

Each captures a different kind of 'this feels bad'. You want all three in the green.

What each one really means

LCP (loading). The moment the biggest useful thing — usually the hero image or headline — finishes rendering. Slow LCP usually means heavy images, slow servers or render-blocking scripts.
INP (responsiveness). How long between a user action and the page visibly responding. Bad INP almost always means too much JavaScript blocking the main thread.
CLS (stability). Whether content shifts under a user’s finger — the classic “I tapped the wrong button because an ad loaded.” Usually caused by images or embeds without reserved space.

Where the wins usually come from

You do not fix Core Web Vitals by chasing the score. You fix them by removing the causes. In my experience the same handful of changes move the needle on most sites.

The usual high-impact fixes

1

Serve from a CDN

Cut latency and speed up LCP with a content delivery network.
2

Cache aggressively

Cache static assets so repeat views are near-instant.
3

Ship less JavaScript

Less main-thread work is the biggest lever for INP.
4

Reserve space for media

Set width/height on images and embeds to kill CLS.

The first two — a CDN and good caching — are often the cheapest large wins for a small team.

FAQ

Do Core Web Vitals actually affect SEO?

Yes, but they are one signal among many. Great content on a slightly slow page still ranks; terrible content on a fast page does not. Treat Core Web Vitals as a tiebreaker and a user-experience goal, not a magic ranking button.

What happened to FID?

Interaction to Next Paint (INP) replaced First Input Delay (FID) as the responsiveness metric. INP is stricter and measures the full interaction, not just the initial delay, so it reflects real responsiveness better.

What tools show my Core Web Vitals?

Google’s PageSpeed Insights and Search Console show field data for free. For ongoing monitoring and alerts, see the best web performance monitoring tools.

What’s a “good” score?

Roughly: LCP under 2.5s, INP under 200ms, CLS under 0.1 — measured at the 75th percentile of your real users. Hitting those on real devices, not just your laptop, is the goal.