Definition
Core Web Vitals are three measurements Google uses to describe a page’s real-world experience: loading speed, responsiveness and visual stability. Unlike crawlability, which asks whether a bot can reach a page at all, Core Web Vitals describe what a human sees once the page arrives. AI crawlers experience almost none of it.
At a glance
- CategoriesTechnical
- Related fieldsSEO, Technical
- DifficultyIntermediate
At a glance
- The three metrics are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
- The scores Google reports come from real Chrome sessions, not from a test you run yourself.
- Time to first byte is the part of page speed an AI crawler genuinely experiences.
- A page with perfect scores can still be impossible to quote.
Loading, responsiveness and stability, measured separately
Largest Contentful Paint times how long the biggest visible element takes to render. It stands in for the question a visitor is asking, which is when can I read this.
Interaction to Next Paint measures the gap between someone tapping and the page visibly responding. Heavy scripts cause most bad ones.
Cumulative Layout Shift scores how much the page jumps around while loading. Late images without reserved space and injected banners do most of the damage.
Google’s Web Vitals documentation holds the current definitions and thresholds. The scores in Search Console come from real Chrome sessions, so they move when your visitors change, not only when your code does. A test run from your laptop on office wifi measures something else and will flatter you.
A bot does not feel a layout shift
Core Web Vitals were designed around a person holding a phone. Most of what they measure means nothing to a machine.
An AI crawler requests a URL, takes the response and leaves. It does not wait for a web font, it clicks nothing, and a banner shoving your first paragraph down the screen costs it exactly zero.
One part carries across. If your server is slow to return the first byte, or falls over under crawl load, the fetch fails and there is no content to read. To the system asking, that looks identical to a page that does not exist.
So hold these metrics in the right place. They are a human experience measure sharing a server with your AI visibility. Fixing your slowest templates helps both. A green score on a page nobody would quote helps neither.
Work from field data, not a lab score
Two hours in Search Console, then a ticket for whoever owns the front end.
- Open the Core Web Vitals report and sort by template, not by URL. One layout fix usually clears thousands of pages at once.
- Check time to first byte on its own. It governs whether a crawler gets a response, and a CDN cache can hide a slow origin behind a respectable LCP.
- Reserve space for anything that loads late. Width and height on images, a fixed slot for consent banners and ad units.
- Stop at good enough. Once a template is out of the poor bucket, the next hour goes further on crawlability or on whether the page says anything worth lifting.
Who each measurement actually affects
| Metric | What it measures | Who notices |
|---|---|---|
| Largest Contentful Paint | Time until the main content renders | Human visitors, Google Search |
| Interaction to Next Paint | Delay before the page responds to input | Human visitors only |
| Cumulative Layout Shift | How much the page moves while loading | Human visitors only |
| Time to first byte | Server response speed | Humans, search crawlers, AI crawlers |
Frequently asked questions
-
Do Core Web Vitals affect whether AI assistants cite me?
Not directly, with one exception. These metrics describe a rendered experience no crawler has, so layout shift and input delay are irrelevant to citation. Server response time is not: a fetch that times out returns nothing, and nothing cannot be quoted.
-
Are Core Web Vitals the same as page speed?
No. Page speed is a loose term for any timing measurement. Core Web Vitals is a specific named set that Google defines and reports from real Chrome users. A page that looks fast in one tool can still fail the field data Google actually uses.
-
How long after a fix before the scores move?
Weeks, not days. The reported score is a rolling window of real user sessions, so a deploy today changes the number only as new sessions accumulate. Lab tools show the improvement at once, which confirms the fix landed and tells you nothing about reported progress.
-
Is this worth doing for a small site?
Once, on your main templates, then leave it alone. A small site with server-side rendering and sensibly sized images usually passes without special effort. Ongoing Core Web Vitals work earns its keep on large ecommerce catalogs and media sites, and rarely anywhere else.