Core Web Vitals: A Practical Guide

Jason Yochim Jul 8, 2026

What LCP, INP, and CLS actually measure, why field data disagrees with your lab tests, and the fixes that reliably move each metric.

Core Web Vitals are Google's attempt to reduce user experience to three numbers: how fast the main content appears, how quickly the page responds to interaction, and how much the layout jumps around. They are a modest ranking input and a meaningful conversion input, which is reason enough to care.

The three metrics in plain terms

Largest Contentful Paint (LCP): time until the biggest visible element renders; target under 2.5 seconds.
Interaction to Next Paint (INP): how long the page takes to visibly respond when users click, tap, or type; target under 200 milliseconds.
Cumulative Layout Shift (CLS): how much content moves unexpectedly; target under 0.1.

Trust field data over lab data

Lighthouse runs a simulation on your machine; Google ranks you on real Chrome users' experiences collected in the CrUX dataset. The two disagree constantly. Use Search Console's Core Web Vitals report to find which page groups actually fail in the field, then use lab tools to diagnose why.

Fixes that usually work

For LCP: compress and properly size the hero image, serve it early with a preload hint, and cut server response time with caching or a CDN. For INP: break up long JavaScript tasks, defer scripts the first paint does not need, and audit third-party tags, which are the culprit more often than your own code. For CLS: give images and embeds explicit dimensions, and reserve space for ads and banners instead of letting them shove content down.

Keep it from regressing

Performance decays one marketing tag at a time. Set a budget, test on real mid-range phones, and re-check vitals after every redesign or new vendor script. The teams that stay green treat speed as a feature with an owner, not a one-time project.

Services related to this content