Technical SEO

Core Web Vitals 2026: How Page Speed Affects Rankings & Revenue

How LCP, INP, and CLS shape Google rankings, conversion, and revenue in 2026. Thresholds, fixes, and what AI search engines care about now.

vaza.aiPublished: 2 April 2026Updated: 10 June 20268 min read

Laptop screen showing performance analytics dashboard with charts and Core Web Vitals scores

Quick Answer

Core Web Vitals (LCP, INP, CLS) are a confirmed Google ranking factor in 2026 and a direct driver of conversion. Pages in the green range (LCP under 2.5s, INP under 200ms, CLS under 0.1) consistently outrank slower competitors and convert 2-3x better. AI search engines (ChatGPT, Perplexity, Google AI Overviews) also skip slow pages, so the same scores now control your AEO visibility too.

Related guides: Best SEO Framework 2026 covers which frameworks score best, Best Frontend Stack for SEO 2026 goes deeper on the UI library plus build tool combinations, and VEO 2026 explains why voice assistants require sub-3-second loads too.

2.5s

Good LCP threshold

200ms

Good INP threshold

0.1

Good CLS threshold

conversion drop per 1-second delay

The 3 Core Web Vitals (2026)

Metric	What it measures	Good	Needs Work	Poor
LCP (Largest Contentful Paint)	When the main content finishes loading	< 2.5s	2.5-4s	> 4s
INP (Interaction to Next Paint)	How fast the page responds to clicks/taps	< 200ms	200-500ms	> 500ms
CLS (Cumulative Layout Shift)	How much the page jumps around as it loads	< 0.1	0.1-0.25	> 0.25

INP replaced First Input Delay (FID) in March 2024 and is now the responsiveness metric. It measures the worst-case interaction latency, not just the first one, so it is harder to game.

You need to hit "Good" on at least 75% of real-user page loads (from the Chrome User Experience Report) to pass the ranking threshold.

Why Core Web Vitals Matter More in 2026

Three things shifted between 2023 and 2026 that made Core Web Vitals more important, not less:

AI search engines are pickier. ChatGPT browsing, Perplexity, Claude search, and Google AI Overviews skip pages that respond slowly to their crawlers. A 5-second LCP is invisible to them. If your page is not part of the indexed AI training set, you do not get cited.
Mobile-first is universal. Over 60% of all queries are mobile in 2026. Mobile Core Web Vitals scores carry more weight than desktop in Google's ranking algorithm.
Page Experience compounds with E-E-A-T. Google's 2026 core updates strengthened the link between technical health and content authority. A fast page with strong E-E-A-T outranks a slow one even when both have similar content quality.

How Page Speed Hits Revenue Directly

Speed is not just an SEO factor. It is a revenue factor.

A 1-second delay drops conversion by ~7% (Akamai, Portent)
Pages under 1.5 seconds convert 2-3x better than pages over 5 seconds
Every 100ms of LCP improvement correlates with measurable revenue lift on e-commerce sites
Mobile bounce rate jumps 32% as load time goes from 1s to 3s (Google research)

The relationship is non-linear. The gap between 1s and 2s costs you more than the gap between 4s and 5s, because user expectations are anchored to the fast end of the distribution.

How to Fix LCP

LCP measures when the main content (usually a hero image or H1) finishes painting. Most LCP problems come from one of these:

Unoptimized hero images. Use WebP or AVIF. Set explicit width and height. Use fetchpriority="high" on the LCP image.
Render-blocking JavaScript. Move scripts to async/defer. Move all non-critical scripts to load after the main content paints.
Slow server response (TTFB). Move to a CDN-backed host (Cloudflare Pages, Vercel, Netlify). Static or edge-cached pages have TTFB under 50ms globally.
Web font loading. Use font-display: swap and self-host fonts. Avoid blocking on Google Fonts in production.

Most legacy WordPress sites have an LCP of 4-7 seconds on mobile. Migrating to a modern stack (Next.js or Astro on Cloudflare or Vercel) routinely cuts that to under 1.5 seconds.

How to Fix INP

INP is harder than LCP because it depends on the entire interaction lifecycle. The main causes:

Long JavaScript tasks. Anything blocking the main thread for more than 50ms hurts INP. Use the Performance tab in Chrome DevTools to find them.
Heavy event handlers. Avoid synchronous work in click and input handlers. Move it to requestIdleCallback or break it up with scheduler.yield().
Excessive React re-renders. Use React 19 concurrent features, memoize expensive components, and consider Server Components for static UI.
Bundle size. Less JavaScript = better INP. Astro, SvelteKit, and Qwik ship minimal JS by default. Code-split aggressively in larger React apps.

How to Fix CLS

CLS is the easiest to fix and the most often ignored.

Reserve space for images, videos, embeds, and ads with explicit width and height attributes (or CSS aspect-ratio)
Avoid injecting content above existing content after load
Use `font-display: swap` with a matched fallback to prevent web font layout shift
Test on slow 3G to expose shifts that fast networks hide

A well-built site has CLS under 0.05 effortlessly. If you are above 0.1, something is being injected without reserved space.

Framework Choice and Core Web Vitals

The framework you build on sets your ceiling.

Framework	Default LCP	Default INP	Default CLS	Effort to score green
Astro 5	Excellent	Excellent	Easy	Minimal
SvelteKit 2	Excellent	Excellent	Easy	Minimal
Qwik	Excellent	Excellent	Easy	Minimal
Next.js 15 (App Router)	Good	Good	Easy	Moderate
Nuxt 3	Good	Good	Easy	Moderate
WordPress (default theme)	Poor	Poor	Variable	High
React SPA (Vite, no SSR)	Poor	Variable	Variable	High
Angular (no SSR)	Poor	Poor	Variable	High

For a deeper framework comparison, see Best SEO Framework 2026.

How to Measure Core Web Vitals

Use field data, not lab data, for ranking decisions:

Chrome User Experience Report (CrUX) is what Google uses for ranking. It shows real users, not synthetic tests.
PageSpeed Insights (pagespeed.web.dev) combines CrUX field data with a Lighthouse lab run.
Google Search Console has a Core Web Vitals report under Experience showing your trend over 28 days.
Real User Monitoring (RUM) via Vercel Analytics, Cloudflare Web Analytics, or a custom web-vitals library setup gives you continuous data.

Lab tools (Lighthouse, WebPageTest) are useful for debugging individual pages, but rankings are decided by field data.

Summary

Core Web Vitals (LCP, INP, CLS) are a confirmed 2026 Google ranking factor
Good thresholds: LCP under 2.5s, INP under 200ms, CLS under 0.1, on 75% of real-user loads
Fast pages convert 2-3x better and earn more AI engine citations
The biggest wins: optimize hero images, reduce JavaScript, fix font loading, and use a CDN host
Framework choice matters. Astro, SvelteKit, Qwik, and Next.js 15 score best by default
Legacy WordPress sites typically have LCP of 4-7 seconds on mobile; migration routinely cuts that under 1.5 seconds
Measure with field data (CrUX, Search Console), not lab data, for ranking decisions

Get a Free Core Web Vitals + SEO Audit of Your Website

References

Google Search Central: Core Web Vitals - Official Google docs on the ranking signal
web.dev: Core Web Vitals - Definitive metric documentation
web.dev: Interaction to Next Paint (INP) - INP explained
Chrome User Experience Report - Field data source Google uses for ranking
Portent: Page Speed Conversion Research - Conversion rate vs load time data
Think with Google: Mobile Page Speed Benchmarks - Mobile speed benchmarks

Frequently Asked Questions

What are Core Web Vitals in 2026?

Core Web Vitals are three metrics Google uses to measure user experience: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. INP replaced First Input Delay (FID) in March 2024 and remains the responsiveness metric in 2026.

Are Core Web Vitals a ranking factor?

Yes. Google confirmed Core Web Vitals are part of the Page Experience ranking signal. Sites that pass all three thresholds in the green range consistently outrank slower competitors, especially for competitive head terms and mobile queries.

What are the Core Web Vitals thresholds in 2026?

Good thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Anything above LCP 4 seconds, INP 500 ms, or CLS 0.25 is rated poor. Most sites should aim for the good range on at least 75% of real-user page loads.

How does page speed affect conversion rate and revenue?

Studies consistently show pages that load in under 1.5 seconds convert 2-3x better than pages that take 5+ seconds. A 1-second delay can drop conversions by 7%. For e-commerce sites, every 100ms improvement in LCP correlates with a measurable lift in revenue per session.

Do AI search engines like ChatGPT and Perplexity care about page speed?

Yes. AI search engines pull from pages that load quickly and respond reliably to their crawlers. Slow pages get skipped or timed out, which reduces your chances of being cited in AI Overviews, ChatGPT search results, and Perplexity answers.

What is the biggest cause of poor LCP?

Unoptimized hero images, render-blocking JavaScript, and slow server response times are the top three. In 2026, the most common fix is moving from a slow legacy host to a CDN-based platform like Cloudflare Pages or Vercel and using modern image formats (WebP or AVIF) with explicit dimensions.

How do I fix INP issues?

Reduce long JavaScript tasks, split your bundles, and avoid heavy work in event handlers. Frameworks like Astro and SvelteKit ship less JavaScript by default. For React or Next.js apps, server components and React 19's concurrent features dramatically improve INP.

How do I prevent CLS issues?

Reserve space for images, videos, and ads by setting explicit width and height. Avoid injecting content above existing content after page load. Use font-display swap with a matched fallback font to prevent layout shift from web font loading.

Does framework choice affect Core Web Vitals?

Yes, significantly. Astro 5, SvelteKit 2, and Qwik consistently produce the best Core Web Vitals scores out of the box because they ship minimal JavaScript. Next.js 15 with React 19 server components is also excellent. Older React SPAs and Angular apps require more tuning.

How does vaza.ai monitor Core Web Vitals?

vaza.ai scans every deploy for Core Web Vitals regressions, alerts you when scores drop, and opens pull requests with the specific fixes (image optimization, JS splitting, font loading). The pipeline runs continuously, so issues are caught and fixed before they affect rankings or revenue.