What's a Good Core Web Vitals Score in 2026? (LCP, INP, CLS Explained)

The three metrics, and the exact 2026 thresholds

Core Web Vitals are three measurements Google uses to judge how a page actually feels to use. As of 2026, they are:

• LCP (Largest Contentful Paint) — how long the main content takes to load. Good: under 2.5 seconds.
• INP (Interaction to Next Paint) — how quickly the page responds when someone clicks, taps, or types. Good: under 200 milliseconds.
• CLS (Cumulative Layout Shift) — how much the layout jumps around while loading. Good: under 0.1.

If you've read an older guide that mentions "FID" instead of INP, it's out of date — INP fully replaced FID as the responsiveness metric back in March 2024.

The part almost everyone gets wrong

A perfect score in Lighthouse or PageSpeed Insights' lab test does not mean you're passing Core Web Vitals. Google doesn't grade you on a lab test — it grades you on real visitor data, collected through the Chrome User Experience Report (CrUX), measured at the 75th percentile over a rolling 28-day window.

In plain terms: your page needs to feel fast for at least 75% of real people visiting it — including the ones on a three-year-old Android phone with a spotty connection, not just your own laptop on office wifi. That's why a site can look instant to you personally while still failing Core Web Vitals in Search Console — you're testing on a much better device and connection than a meaningful chunk of your actual visitors.

Which one to fix first

If you're failing more than one, start with INP. It's the metric most sites fail, and unlike LCP and CLS — which usually have a short, well-known list of fixes (compress images, reserve space for elements, preload fonts) — INP often means rethinking how much JavaScript runs on the main thread during an interaction. That's a bigger job, so it's worth starting on it early rather than leaving it for last.

Practical starting points, roughly in order of impact:

1. LCP — compress and properly size your largest image or hero element, preload it instead of lazy-loading it, and get server response time down.
2. CLS — add explicit width and height to every image, video, and embed, and reserve space for anything that loads in late (ads, cookie banners, web fonts).
3. INP — break up long JavaScript tasks, defer anything that isn't needed immediately, and cut back on heavy third-party scripts (chat widgets, analytics, ad tech) that block the main thread.

How to actually check your score

Two different tools tell you two different things, and it's worth knowing which is which:

• Google Search Console's Core Web Vitals report shows real CrUX field data — this is the number that affects rankings.
• PageSpeed Insights / Lighthouse shows a lab test on one simulated device — useful for debugging why a page is slow, but not what Google actually scores you on.

If you want a quick read on where a site currently stands, a full crawl will pull live Core Web Vitals data for you alongside everything else — broken links, missing tags, mobile issues — in one pass, rather than checking each page by hand.