Core Web Vitals explained: LCP, INP and CLS in plain language

"Page speed" used to mean one crude number. Core Web Vitals replaced that with three specific, visitor-centered questions: Did the content show up quickly? Did the page respond when I interacted? Did things stay where they were? Here's each one in plain language.

LCP — Largest Contentful Paint: "how fast does the main thing appear?"

LCP measures the time from opening the page until its largest visible element — usually the hero image or the main headline — has rendered. It's the moment the page feels loaded, regardless of what's still happening in the background.

• Good: under 2.5 seconds · Needs improvement: 2.5–4s · Poor: over 4s

What usually drags LCP down: enormous unoptimized images, slow server responses (typical for WordPress sites that build every page on the fly from a database), and render-blocking scripts and CSS that must load before anything can show. The biggest levers are the same in reverse: properly sized modern-format images (like WebP), a fast host or CDN that serves pages from a location near the visitor, and pages that are pre-built rather than assembled per request — which is why static sites tend to score so well here.

INP — Interaction to Next Paint: "does it react when I tap?"

INP measures how long the page takes to visually respond after you click, tap, or press a key — across all interactions during the visit, not just the first. Type in a search box and see the letter appear instantly? Great INP. Tap a menu and nothing happens for half a second? That's exactly what INP catches.

• Good: under 200 ms · Needs improvement: 200–500 ms · Poor: over 500 ms

The culprit is almost always too much JavaScript: heavy scripts keep the browser's main thread busy, so your tap has to wait in line. Sites loaded with plugins, trackers, and widgets each bringing their own scripts suffer most. The fix is ruthless subtraction — fewer and smaller scripts, third-party embeds loaded only when needed. (INP replaced the older FID metric in 2024; if you see FID mentioned in an older article, INP is its stricter successor.)

CLS — Cumulative Layout Shift: "does the page jump around?"

CLS measures visual stability: how much visible content shifts position while the page loads. You've felt it — you go to tap a button, an ad loads above it, everything jumps, and you tap the wrong thing. CLS is a score rather than a time.

• Good: under 0.1 · Needs improvement: 0.1–0.25 · Poor: over 0.25

Layout shift comes from elements that arrive without reserved space: images without declared dimensions, ads and embeds injected mid-load, banners that push content down, custom fonts that swap in at a different size. The fix is to give everything its space up front — set width and height on images and embeds, and reserve room for anything that loads late.

Where do I see my scores?

• PageSpeed Insights — enter any URL and get both lab results and, for sites with enough traffic, 28 days of real-visitor data (the numbers Google actually uses).
• Google Search Console — the Core Web Vitals report shows how all your pages score, grouped by status, based on real-user data.
• If your site runs on ShiftPress, the dashboard's Speed & SEO report runs these checks for you and turns the findings into plain-language fixes.

One distinction worth knowing: lab data is a one-off simulated test (useful for debugging), while field data is what real visitors experienced over 28 days — rankings are influenced by the field data. That's also why improvements take a few weeks to show up in the reports.

Do Core Web Vitals really affect rankings?

Yes, with proportion. Google confirms page experience — with Core Web Vitals at its heart — is a ranking signal, but content relevance still dominates: a slow page with the best answer beats a fast page with a mediocre one. The signal matters most as a tiebreaker in competitive results. The indirect effect is often bigger than the direct one: slow, janky pages make visitors leave sooner, and both users and search engines notice that. Speed is also cumulative — a fast site gets crawled more efficiently and converts better, vital for every goal the site has.

Frequently asked questions