You tap a link. Nothing happens. You tap again. The page jumps and you hit the wrong button. You leave.
Core Web Vitals are Google’s way of measuring exactly that frustration. Three measures, each tied to something a visitor feels.
The three measures
- LCP, Largest Contentful Paint: how soon the biggest thing on screen, usually a hero image or a headline, appears. Good is 2.5 seconds or less.
- INP, Interaction to Next Paint: how quickly the page responds when someone clicks, taps or presses a key. Good is 200 milliseconds or less.
- CLS, Cumulative Layout Shift: how much things move around unexpectedly while the page loads. Good is 0.1 or less.
These are judged at the 75th percentile of real visits, split by mobile and desktop. In plain words: at least three in four of your visitors, on each kind of device, should have a good experience. A page passes when all three measures are good.
Field data and lab data
Field data comes from real visitors on their real phones and networks. Lab data is a test run on a single machine. The first tells you what people actually felt. The second helps you find out why.
- PageSpeed Insights shows real-visitor data where it’s available, alongside a lab test.
- Search Console’s Core Web Vitals report shows how your pages perform across the site.
- Lighthouse and Chrome DevTools are lab tools for debugging. Lighthouse can’t measure INP because it has no real user input, so it reports Total Blocking Time instead.
Fixing LCP: show the main thing sooner
Start with the hero image. Google’s guidance is blunt: never lazy-load your LCP image. Lazy loading tells the browser to wait, which is the opposite of what you want for the first thing people see.
- Put the hero image in the page’s HTML so the browser finds it early.
- Set fetchpriority="high" on it, on one or two images at most.
- Serve it at the right size in a modern format such as AVIF or WebP.
- Trim render-blocking CSS and avoid synchronous scripts in the head.
- Use a CDN and sensible caching so the first byte arrives sooner.
<img
src="/hero.webp"
width="1200"
height="630"
fetchpriority="high"
alt="Our shop front on a busy morning"
/>Fixing INP: answer taps quickly
A slow response usually means the browser is busy running JavaScript when the visitor taps. Send less script. Break long jobs into smaller pieces so the page can respond between them. Check the slow interactions in your field data first, then reproduce them in the lab.
Fixing CLS: stop the jumping
Layout shifts happen when something arrives and pushes everything else around. Give images and videos a width and height, as in the snippet above, so the space is saved before they load. Reserve room for embeds, ads and banners. Be careful with web fonts, because text that renders at a different size than its fallback will shift when the font loads.
What about rankings?
Google’s Search documentation says it highly recommends good Core Web Vitals, and that they align with what its core ranking systems seek to reward. It doesn’t say how much weight they carry, so treat them as one part of a good experience, not a magic switch.
The better reason to care is simpler. A site that appears quickly, responds quickly and stays still is nicer to use. People notice, even if they never know why.

