Core Web Vitals
Core Web Vitals are Google's three field metrics for how a page actually loads and behaves for real visitors: Largest Contentful Paint (loading speed), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). They are measured from real Chrome user data, not a lab simulation, and Google uses them as one confirmed signal of page experience quality.
What the three metrics mean
LCP (Largest Contentful Paint) measures how long the largest visible element – usually a hero image or headline – takes to render; under 2.5 seconds is good. INP (Interaction to Next Paint), which replaced First Input Delay as the responsiveness metric in 2024, measures how quickly the page visibly responds to a click, tap or keypress; under 200 milliseconds is good. CLS (Cumulative Layout Shift) measures how much content jumps around as the page loads; under 0.1 is good. Together they describe whether a page feels fast, stable and responsive, and Google pulls the numbers from the Chrome User Experience Report (CrUX), meaning they reflect what your actual visitors experienced, not a synthetic test run.
Why this matters for visibility
In classic Google Search, Core Web Vitals are a confirmed but minor ranking factor: among pages with comparable content quality, the faster and more stable one has an edge. The bigger effect is indirect. A slow or jumpy page loses visitors before they read anything, which shows up as a higher bounce rate and fewer conversions – and that damage happens whether or not the ranking algorithm cares. It matters for AI visibility too, though not for the reason many teams assume: Google has stated plainly that no special markup, schema, or AI-specific files are required for AI Overviews or AI Mode, and that writing separate content "for AI" is the wrong approach. What crawlers from OpenAI, Google and others do need is a page that loads and renders reliably enough to be fetched at all. Good Core Web Vitals don't earn you an AI citation on their own, but a page that times out or renders unpredictably can be skipped before your content is ever considered.
Common mistakes in practice
The most common mistake is checking Core Web Vitals only in a lab tool like Lighthouse and stopping there. What actually counts for ranking and for understanding real visitor experience is the field data in Google Search Console's Core Web Vitals report, pulled from CrUX. A second classic mistake: images without fixed width and height attributes, which push text around as they load and wreck the CLS score. Equally costly are oversized, uncompressed hero images that inflate the LCP, and heavy JavaScript bundles that block the main thread and worsen INP. Ads, cookie banners or chat widgets injected after the initial render are a frequent, easily missed source of layout shift. And teams that only optimise the homepage often miss that it's the guide, product and pricing pages – the ones actually carrying traffic and conversions – where poor vitals cost the most.
Relation to AI visibility
Core Web Vitals are not a documented ranking or citation signal for ChatGPT, Perplexity, Gemini or Google AI Overviews – none of these systems has published vitals as an input. What they are is a reasonable proxy for whether a crawler can fetch and parse your page cleanly. Research bears this out indirectly: Ahrefs found that only 6–8% of URLs ChatGPT cites overlap with a site's Google top-10 rankings, and about 80% of ChatGPT-cited URLs don't rank in Google's top 100 at all – AI citation runs on a largely separate selection process from SEO ranking, and page speed alone won't bridge that gap. What actually correlates more strongly with getting cited is how often a brand is mentioned across the web (Ahrefs found this correlates with AI citation rate at roughly 0.664, about three times stronger than backlinks at 0.218). Treat Core Web Vitals as a floor to clear, not a lever to pull: a slow or unstable page can quietly keep a crawler from indexing you properly, but fixing it won't manufacture citations on its own.
Example
An online shop for bike accessories is puzzled by high cart abandonment on mobile. Measurement shows the large product image doesn't finish loading until four seconds in (poor LCP), and a discount banner that slides in shifts the buy button just as users tap it (poor CLS). The team compresses the images, reserves fixed space for the banner before it loads, and trims unused JavaScript. Two weeks later all three metrics sit in the green range in Search Console, bounce rate drops, and mobile conversion improves. The same pattern shows up for tradespeople, law firms or travel providers whose booking or contact forms sit behind a slow, shifting page.
Common questions
Are Core Web Vitals a ranking factor for AI search?
Not directly, and no AI system has published them as a citation signal. But a page with good vitals is usually one that crawlers can fetch and render without trouble, which is a precondition for being read in the first place – and reading is a precondition for being cited.
How can I measure Core Web Vitals for free?
Google Search Console shows field data from real visitors, PageSpeed Insights combines field and lab data with specific fix suggestions, and the Chrome Web Vitals extension measures the metrics live as you browse. The field data in Search Console is the one that matters most, since it reflects real users rather than a single test run.