Core Web Vitals Explained: LCP, INP and CLS in Plain English
Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how fast the main content loads (LCP), how quickly the page responds when someone taps or clicks (INP), and how much the layout jumps around while loading (CLS). A page is considered "good" when it hits 2.5 seconds or less for LCP, 200 milliseconds or less for INP, and 0.1 or less for CLS, measured for at least 75% of visits.
That is the whole idea. The rest of this guide explains what each number means in plain English, where to check your own scores for free, and the fixes that usually make the biggest difference. If you only have ten minutes, read the table and the "fix first" section.
What Are Core Web Vitals?
Core Web Vitals are a small set of user-experience metrics defined by Google's web performance team. They exist because "fast" is vague. Instead of one speed score, they ask three practical questions: did the page show up quickly, does it react when I use it, and does it stay still while I read it?
Google describes them as part of page experience and says its ranking systems reward content that provides a good page experience. It also says it recommends site owners achieve good Core Web Vitals for success in Search. Google does not publish how much weight they carry, so treat them as one useful signal, not a magic switch. Great content on a slightly slow page can still rank; a frustrating page makes people leave, which hurts you whatever the algorithm does.
The Three Core Web Vitals at a Glance
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed | 2.5 s or less | Over 4 s |
| INP (Interaction to Next Paint) | Responsiveness | 200 ms or less | Over 500 ms |
| CLS (Cumulative Layout Shift) | Visual stability | 0.1 or less | Over 0.25 |
Scores in between the "good" and "poor" lines are labelled "needs improvement." Google evaluates the 75th percentile of real page loads, split by mobile and desktop, so a handful of fast visits on your own laptop will not tell the full story.
What Is LCP (Largest Contentful Paint)?
LCP measures how long it takes for the largest visible element, usually a hero image, a big heading, or a video poster, to appear on screen. It is the closest single number to "when did the page look ready?"
The most common causes of a slow LCP are oversized images, slow server responses, and files that block the page from drawing (large stylesheets and scripts loaded at the top).
What Is INP (Interaction to Next Paint)?
INP measures how long the page takes to visually respond after a visitor taps, clicks, or presses a key. It looks at interactions across the whole visit and reports one of the slowest, so a single sluggish menu or button can drag the score down.
INP became a stable Core Web Vital in 2024 and replaced the older First Input Delay (FID). If an article still talks about FID as a current vital, it is out of date. A slow INP is usually caused by too much JavaScript running at once, heavy third-party scripts, or large page structures that take the browser a long time to update.
What Is CLS (Cumulative Layout Shift)?
CLS measures unexpected movement. You have felt it: you go to tap a link, an image loads above it, and everything shifts down so you tap the wrong thing. CLS adds up how much visible content moves and how far.
The usual culprits are images and videos without set dimensions, ads or embeds that load late and push text down, and web fonts that swap in with a different size.
How to Check Your Core Web Vitals for Free
You do not need paid software. Use these in order:
- Google Search Console: the Core Web Vitals report groups your URLs into good, needs improvement, and poor using real visitor data. If you have not set it up yet, start with our beginner's guide to Google Search Console.
- PageSpeed Insights: paste in any URL. The top section shows real-user data when enough visits exist; the lower section is a lab test with specific suggestions.
- Chrome DevTools and Lighthouse: useful for testing a fix before you publish it. Lighthouse cannot measure INP directly because it does not click anything, so it reports Total Blocking Time as a stand-in.
Understand the difference between the two kinds of data. Field data comes from real visitors and is what Google evaluates. Lab data is a simulated test, good for debugging but not the final verdict. A small or new site may have no field data yet; that is normal and does not mean something is broken.
How to Improve LCP
- Compress and resize images. Serve modern formats such as WebP or AVIF, and never upload a 4000-pixel photo to display at 800 pixels.
- Do not lazy-load the main image. Lazy loading is for images below the fold. The hero image should load first.
- Improve server response. Quality hosting, caching, and a content delivery network (CDN) cut the wait before anything can load.
- Trim what blocks rendering. Remove unused CSS and defer scripts that are not needed for the first screen.
How to Improve INP
- Remove scripts you do not need. Every chat widget, tracker, and pop-up tool adds work for the browser. Audit them once a quarter.
- Delay non-essential third-party code until after the page is usable.
- Keep pages lean. Huge, deeply nested pages take longer to update after each tap.
- On WordPress or site builders, deactivate plugins you no longer use; they are a frequent source of heavy scripts.
How to Improve CLS
- Set width and height on every image and video so the browser reserves space before they load.
- Reserve space for ads, banners, and embeds. A fixed-size slot stops content jumping when they appear.
- Load fonts carefully. Choose a fallback font of similar size so text does not reflow when the real font arrives.
- Never insert new content above what someone is already reading unless they triggered it.
Which Core Web Vital Should You Fix First?
Start with whichever one Search Console or PageSpeed Insights flags as "poor." If everything is in the "needs improvement" range, this order tends to pay off fastest for typical small sites:
| Priority | Fix | Typical effort |
|---|---|---|
| 1 | Compress and resize images (helps LCP) | Low |
| 2 | Add image dimensions (helps CLS) | Low |
| 3 | Remove unused plugins and scripts (helps INP and LCP) | Medium |
| 4 | Upgrade hosting or add a CDN (helps LCP) | Medium |
Make one change at a time and re-test. Field data in Search Console updates over a rolling window of roughly four weeks, so give changes time to show up before judging them.
Do Core Web Vitals Really Affect Rankings?
Yes, as one signal among many, and Google says so directly. But relevance and helpfulness of the content still come first. A fast page with thin content will not outrank a genuinely useful page that is a little slower. Think of Core Web Vitals as removing friction: they protect the traffic you already earn from being lost to a page that hangs, jumps, or ignores taps. For the bigger picture of how these pieces fit, see our plain-English guide to SEO.
Core Web Vitals FAQ
What is a good Core Web Vitals score?
LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, for at least 75% of page visits.
Did INP replace FID?
Yes. INP replaced First Input Delay as a Core Web Vital in 2024 because it captures responsiveness across the whole visit, not just the first tap.
Why does my score differ between tools?
Lab tests simulate one visit on one device and connection. Field data reflects thousands of real visits. Trust the field data when you have it.
Do I need a developer to fix these?
Not always. Image compression, removing unused plugins, and setting image sizes are all doable without code. Script and server issues may need technical help.
How long until improvements show in Search Console?
Expect several weeks, because the report uses a rolling window of real-user data.
The Bottom Line
Core Web Vitals come down to three promises to your visitor: the page shows up fast, it responds when touched, and it holds still. Check your numbers in Search Console and PageSpeed Insights, fix the "poor" ones first, and keep pages lean. If you would like a second pair of eyes on your site, you are welcome to get in touch.