Skip to content
AEO Canon · the reference for answer-engine optimization

Core Web Vitals Thresholds for AEO

The Core Web Vitals thresholds are fixed — LCP good under 2.5s, INP good under 200ms, CLS good under 0.1 — and you pass only when 75% of visits hit good on all three. Speed does not directly rank you in AI answers, but it keeps crawlers fetching and users landing on the pages that get cited.

BBurke Atkerson2 min read

Core Web Vitals thresholds are fixed numbers, and you pass only when 75% of real visits hit "good" on all three. They do not directly rank you in AI answers — but a slow, unstable page quietly costs you the crawls and the visits that citations depend on.

Quick answer

Good = LCP under 2.5s, INP under 200ms, CLS under 0.1. You pass only when 75% of visits reach good on all three at the 75th percentile. Speed doesn't directly earn AI citations — but it keeps crawlers fetching and keeps humans on the pages that do get cited. INP (which replaced FID) is the most-failed metric in 2026.

What are the exact thresholds?

Each metric has three bands. Largest Contentful Paint is good under 2.5s and poor past 4.0s; Interaction to Next Paint is good under 200ms and poor past 500ms; Cumulative Layout Shift is good under 0.1 and poor past 0.25. Google defines these on web.dev and in Search Central.

What does it take to "pass"?

You pass when 75% of real-user visits land in the good band, measured at the 75th percentile, across all three metrics at once. One weak metric fails the whole page — so a fast-loading page with jumpy layout still fails.

Why do Core Web Vitals matter for AEO if they don't rank citations?

Because they protect the conditions for citation. AI engines cite content, not speed, but slow servers waste crawl efficiency and unstable pages lose the human visitors who read, link, and mention you. Speed is a supporting signal, not a direct one.

Core Web Vitals thresholds (web.dev / Google Search Central)
MetricGoodNeeds workPoor
LCP (loading)Under 2.5s2.5s – 4.0sOver 4.0s
INP (responsiveness)Under 200ms200ms – 500msOver 500ms
CLS (visual stability)Under 0.10.1 – 0.25Over 0.25
Sites passing INP in 2026
At risk57Established

Roughly 43% of sites fail INP — the most-failed Core Web Vital in 2026.

Fix the slowest metric first, then protect the rest. More in page speed and AI citations and the Core Web Vitals glossary entry.

Does page speed affect AI citations?

Indirectly — speed keeps crawlers efficient and visitors present, but content earns the citation.

Read the full answer →
What are Core Web Vitals?

Google's three real-user metrics for loading, responsiveness, and visual stability.

Read the full answer →
What is LCP?

Largest Contentful Paint — how fast the main content of a page renders. Good is under 2.5s.

Read the full answer →

Frequently asked questions

What are the good Core Web Vitals thresholds?
A page scores good when Largest Contentful Paint is under 2.5 seconds, Interaction to Next Paint is under 200 milliseconds, and Cumulative Layout Shift is under 0.1. To pass overall, at least 75% of real visits must hit good on all three metrics at the 75th percentile.
Do Core Web Vitals directly affect AI citations?
Not directly. AI engines cite pages based on content and retrievability, not page speed. But fast, stable pages keep crawlers fetching efficiently and keep human visitors on the pages that earn citations, so Core Web Vitals support AEO indirectly rather than ranking you in AI answers.
Which Core Web Vital is hardest to pass in 2026?
Interaction to Next Paint, which replaced First Input Delay, is the most-failed metric — roughly 43% of sites fail it. INP measures responsiveness across all interactions on a page, so heavy JavaScript and slow event handlers push many sites into the needs-work or poor range.

Related reading

One scannable reference for the major AI bots — GPTBot and OAI-SearchBot (OpenAI), ClaudeBot and Claude-SearchBot (Anthropic), Google-Extended, Applebot-Extended, PerplexityBot, CCBot, and Bytespider — with each bot's owner, purpose, and whether it actually obeys robots.txt.

2 min read

HTTP status codes are instructions to AI crawlers — 200 means crawl and use, 301 consolidates signals to a new URL, 404 drops a page slowly while 410 drops it fast, 429 says back off, and repeated 5xx errors can get a page removed from the answer pool entirely.

2 min read

In an XML sitemap only a few fields carry weight — loc is essential, lastmod is trusted as a freshness signal if you keep it honest, while changefreq and priority are largely ignored. Include only canonical, indexable 200 URLs and split large files with a sitemap index under 50,000 URLs.

2 min read