Core Web Vitals in 2026: What Google Actually Wants and Why Speed Is Now Money

Core Web Vitals Got a Major Update

If you learned Core Web Vitals when they launched in 2021, your knowledge needs updating. Google replaced First Input Delay (FID) with Interaction to Next Paint (INP) as a core ranking signal, and the thresholds for what counts as "good" performance have become stricter as devices and connections have improved.

More importantly: Google's search ranking now incorporates these signals more heavily than it did at launch. Page experience is not just a tiebreaker. It is a real factor in competitive keyword rankings.

The Three Vitals You Need to Know in 2026

LCP — Largest Contentful Paint (Target: under 2.5 seconds)

Time until the largest visible element on the page (usually a hero image or heading) loads. This is what users experience as "the page loaded."

Top causes of poor LCP:

• Unoptimised hero images (PNG or uncompressed JPEG)
• Server response time too slow (shared hosting under load)
• Render-blocking resources (JavaScript that blocks the browser)
• No CDN — serving assets from a single origin server

Fixes: Convert hero images to WebP/AVIF. Add fetchpriority="high" to your LCP image. Use a CDN. Preload critical fonts.

INP — Interaction to Next Paint (Target: under 200ms)

How long from when a user clicks, taps, or types until the page visually responds. Replaced FID because FID only measured the first interaction; INP measures the worst interaction across the whole session.

Top causes of poor INP:

• Heavy JavaScript execution blocking the main thread
• React/Next.js components with expensive re-renders on interaction
• Event handlers doing synchronous work that should be async
• Third-party scripts (analytics, chat widgets, ad scripts)

Fixes: Break up long tasks with scheduler.yield(). Move non-critical JavaScript to web workers. Defer third-party scripts. Use the React Compiler to eliminate unnecessary re-renders.

CLS — Cumulative Layout Shift (Target: under 0.1)

How much the page visually jumps around as it loads. A button that moves as the user is about to click it, causing them to click the wrong thing, is a CLS failure.

Top causes: Images without explicit width/height. Fonts that cause text reflow on load. Dynamically injected content above existing content.

Fixes: Always specify image dimensions. Use font-display: optional or swap with size-adjust. Reserve space for dynamic content with CSS min-height.

How to Measure Your Scores

• PageSpeed Insights (pagespeed.web.dev) — uses real-world Chrome data. The most accurate measure of what Google sees.
• web.dev/measure — detailed recommendations per metric.
• Chrome DevTools Performance panel — for diagnosing specific INP issues.
• Google Search Console — Core Web Vitals report shows your real-world scores grouped by URL.

The Business Case for Caring

Page speed is not just a ranking signal. It is a conversion signal. Every 100ms of LCP improvement correlates with measurable conversion rate improvement across e-commerce. A site that loads in 1.5 seconds converts more than one that loads in 3.5 seconds — across every industry vertical that has been studied.

When "what Google wants" aligns with "what users want," it is not a difficult optimisation decision. It is table stakes for any serious web presence.