Performance

Core Web Vitals in 2026: what changed and how to pass

The three Core Web Vitals — LCP, INP and CLS — explained with their 2026 thresholds, why INP trips up most sites, and the fixes that move the needle.

SeoraUpdated June 22, 20262 min read

Core Web Vitals are three field metrics Google uses to judge real-world page experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). A page passes when all three sit in the "good" range for the 75th percentile of real visits — LCP under 2.5 s, INP under 200 ms, and CLS under 0.1. They are a lightweight ranking signal, but more importantly they track the friction that makes visitors leave.

The three metrics that matter

LCP (Largest Contentful Paint) — how long until the biggest element in the viewport renders. Good: ≤ 2.5 s.

INP (Interaction to Next Paint) — how quickly the page responds to taps, clicks and key presses across the whole visit. Good: ≤ 200 ms.

CLS (Cumulative Layout Shift) — how much the layout jumps around as it loads. Good: ≤ 0.1.

The big shift is INP. On 12 March 2024 it replaced First Input Delay as a Core Web Vital, and it is now the metric most sites fail — roughly two in five URLs still miss the 200 ms bar. Where FID only measured the delay before the first interaction, INP watches every interaction and reports a near-worst-case latency, so sluggish menus, filters and forms can no longer hide.

How Google actually grades you

Two things surprise people. First, the score is field data, not a lab test: it comes from the Chrome User Experience Report — real Chrome users on real devices and networks — so a fast laptop can pass a page that real phones fail. Second, a URL group only earns a "good" status when at least 75% of visits meet the good threshold for all three metrics at once. Chase your slowest quartile, on the hardware your audience actually uses.

Fixing INP — the metric most sites fail

Break up long tasks. Anything over 50 ms on the main thread blocks interaction — split work and yield back to the browser between chunks.

Ship less JavaScript. Code-split, defer non-critical scripts, and remove unused third-party tags; every kilobyte parsed is time the main thread can't respond.

Keep event handlers cheap. Do the visual update first, then defer heavy work (analytics, network calls) to after the next paint.

Avoid large, synchronous re-renders. Memoise expensive components and virtualise long lists so a single click doesn't re-render the world.

LCP and CLS quick wins

Preload the LCP image or font, serve modern formats (AVIF/WebP), and make sure the hero isn't waiting behind render-blocking CSS or JS.

Give images and embeds explicit width/height (or an aspect-ratio box) so nothing reflows when they load.

Reserve space for ads, banners and late-injected UI instead of letting them shove content down the page.

Where Seora fits

Seora's audit reads your real Core Web Vitals, flags the exact element dragging LCP or the script eating your INP budget, and writes the fix for you. See it on the performance side of an audit or start free.

Treat Core Web Vitals as a product-quality habit, not a one-off cleanup. Measure in the field, fix your slowest 25%, and re-check after every release — the same loop that keeps you fast keeps you ranking. Next, make those fast pages easy to find with a deliberate internal-linking structure.