Guides

Core Web Vitals Explained: LCP, INP, and CLS in Plain English

What Google's Core Web Vitals actually measure, the thresholds that count as good, and the fixes that move each metric the most.

Updated 2 min read

Core Web Vitals are the three metrics Google uses to judge whether a page feels fast and stable to real visitors. They are measured from real Chrome users, reported in Search Console, and used as a ranking signal. If you only track three performance numbers, track these.

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible element, usually a hero image or headline, to render. It is the closest single number to the question a visitor asks: has this page loaded yet?

  • Good: 2.5 seconds or less. Poor: over 4 seconds.
  • Most common causes: slow server response, render-blocking CSS and JavaScript, and oversized hero images.
  • Biggest wins: preload the hero image, serve modern formats like AVIF or WebP, and defer non-critical scripts.

Interaction to Next Paint (INP)

INP replaced First Input Delay in 2024. It measures how quickly the page visibly responds after a click, tap, or key press, across the whole visit rather than just the first interaction.

  • Good: 200 milliseconds or less. Poor: over 500 milliseconds.
  • Most common causes: long JavaScript tasks, heavy third-party tags, and large DOM updates.
  • Biggest wins: break up long tasks, load analytics and chat widgets after the page is interactive, and remove unused scripts.

Cumulative Layout Shift (CLS)

CLS measures how much content jumps around while the page loads. Every time a button moves just as someone goes to tap it, CLS goes up and trust goes down.

  • Good: 0.1 or less. Poor: over 0.25.
  • Most common causes: images without dimensions, late-loading ads and embeds, and web fonts swapping in.
  • Biggest wins: reserve space for every image and embed, and use font-display with size-adjusted fallbacks.

Lab data versus field data

Lighthouse gives you a lab score from one simulated device. Google ranks on field data from real users over the last 28 days, so fixes can take a few weeks to show up in Search Console.

How to measure your own site

  1. Open PageSpeed Insights and enter your URL to see both field and lab data.
  2. Check the Core Web Vitals report in Google Search Console to find groups of failing URLs.
  3. Use Chrome DevTools Performance panel to find the exact element or script causing a problem.

LightLoader automates the most common fixes on all three metrics, including image prioritization, script deferral, and layout reservation, from a single script tag. Whatever tool you use, measure before and after so you know what actually moved.

SEO

Does Page Speed Actually Affect Google Rankings? What the Evidence Says

An honest look at how much page speed and Core Web Vitals influence Google rankings, where speed is only a tiebreaker, and where it pays off anyway.

  • Rankings
3 min read
Tutorials

How to Fix a Slow LCP: The 7 Usual Causes, Ranked by Impact

Find out exactly why your Largest Contentful Paint is slow, then fix the seven most common causes in the order that moves the number most.

  • Core Web Vitals
  • Performance
3 min read
Start optimizing in minutes

Ready to supercharge your website?

Join thousands of websites already using LightLoader to deliver lightning-fast experiences to their users.

No credit card required. Free plan available.

  • Quick Setup

    Install in under 5 minutes

  • Works Everywhere

    Compatible with any platform

  • Instant Results

    See improvements immediately