Core Web Vitals targets and what each one measures
Core Web Vitals are Google's three measurements of how a page feels to a real visitor. The targets below come from Google's Web Vitals reference on web.dev.
| Metric | What it measures | Good score | Usual cause of a miss |
|---|---|---|---|
| Largest Contentful Paint (LCP) | Loading: when the main content appears | Within 2.5 seconds | Oversized hero images, slow server response |
| Interaction to Next Paint (INP) | Interactivity: how fast the page reacts to a tap or click | 200 milliseconds or less | Heavy scripts, too many third-party tags |
| Cumulative Layout Shift (CLS) | Visual stability: how much content jumps around | 0.1 or less | Images and embeds without set dimensions, late-loading fonts |
The score that counts is the 75th percentile of page loads, measured separately for mobile and desktop. In other words, three out of four real visits need to hit the target, so one fast test on office Wi-Fi proves little. Google says Core Web Vitals align with what its core ranking systems seek to reward and recommends good scores, but it does not promise rankings for them. Our guide on how to improve Core Web Vitals covers the fixes in order.
Speed is only half of it
A fast page still fails if Google can't read it. Google's JavaScript SEO basics describe three phases for script-driven pages: crawling, rendering and indexing. Pages wait in a queue before rendering, which can take seconds or longer, and Google recommends server-side rendering or pre-rendering because not every bot runs JavaScript. Google also discovers links only when they are a elements with an href attribute. Menus built from click handlers can hide whole sections of a site. A full SEO audit checks both halves.
