What Core Web Vitals means
LCP measures how quickly the main content renders. INP measures responsiveness to interaction. CLS measures how much the layout jumps around while loading.
They're measured on real user data rather than lab tests, which is why field data and lab scores often disagree.
Why it matters for AI search
For AI search, the more relevant metric is often bot response time, which Core Web Vitals doesn't capture. Slow or timing-out responses to crawlers reduce retrieval frequency.
The underlying work overlaps heavily though — a fast site serves users and crawlers alike.
See it in action
Field metrics and the metric nobody measures.
Bot response time is the one nobody tracks.
Crawlers that time out or receive slow responses fetch less often, so your content goes stale in the index regardless of how good your field metrics look.
How to get it right
Improving Core Web Vitals
- Optimise the largest above-the-fold element — usually a hero image or web font
- Reserve space for images and embeds to prevent layout shift
- Reduce and defer JavaScript; it's the main driver of poor interaction responsiveness
- Measure bot response times separately from user-facing metrics
- Use field data rather than lab scores as the source of truth
Common questions
Are Core Web Vitals a ranking factor?
They're a modest one, generally acting as a tiebreaker rather than a primary signal. Content relevance dominates.
Do Core Web Vitals affect AI visibility?
Indirectly. Bot response time affects crawl frequency and therefore how current your retrievable content is. The user-facing metrics matter less.
Why do lab and field scores differ?
Lab tests run on simulated conditions; field data reflects real devices and networks. Field data is what Google uses.
Related concepts
These come up alongside Core Web Vitals constantly.