Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. A page passes when LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less, measured across most real visits. Hitting those numbers makes your site feel fast and solid, which helps both visitors and search performance.
This guide explains each metric in plain language, what usually causes a poor score, and what fixing it involves, without needing a developer’s vocabulary.
Why Business Owners Should Care
Core Web Vitals are part of Google’s page experience signals. They won’t lift a weak page above a much more relevant one, but when competing pages are similar, a better experience can help. More importantly, the problems these metrics catch are the same ones that make people hit the back button: a hero image that takes forever, a menu that doesn’t respond, a button that jumps just as you tap it.
Google measures these from real Chrome users visiting your site (called field data). That means your scores reflect your actual customers on their actual phones and connections, not a perfect test in an office.
LCP: Largest Contentful Paint (Loading)
What it measures: how long it takes for the biggest visible element in the first screen to appear. On most business sites that’s the hero image, a banner video poster or a large headline.
Target: 2.5 seconds or less is “good.” Between 2.5 and 4 seconds “needs improvement.” Over 4 seconds is “poor.”
Common causes of a slow LCP:
- A huge, uncompressed hero photo straight off a camera.
- Slow server response, often from cheap shared hosting or no caching.
- The hero image being lazy-loaded, so the browser waits to fetch the most important picture on the page.
- Render-blocking scripts and stylesheets that must load before anything shows.
- Sliders that load several large images before displaying the first.
Plain-language fixes: resize and compress the hero image to modern formats like WebP or AVIF, tell the browser to load it first, use page caching and a solid host, and cut or defer scripts that aren’t needed for the first screen. Replacing a rotating slider with one strong image is often a quick win.
INP: Interaction to Next Paint (Responsiveness)
What it measures: how quickly the page visibly reacts when someone taps, clicks or types. INP looks at interactions throughout the visit and reports one of the slowest, so a single sluggish menu can drag the score down.
Target: 200 milliseconds or less is “good.” Up to 500 milliseconds “needs improvement.” Above that is “poor.”
INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. FID only measured the delay before the first interaction started processing; INP measures the full time to a visible response for interactions across the whole visit, which is a much better reflection of how responsive a page feels.
Common causes of a poor INP:
- Too much JavaScript: chat widgets, multiple tracking tags, heavy page builders, popup tools all competing for the browser’s attention.
- Third-party scripts that run long tasks when someone interacts.
- Complex menus, filters or forms that do a lot of work on every tap.
- Very large pages with thousands of elements for the browser to update.
Plain-language fixes: remove plugins and tags you don’t use, load chat and review widgets only after the page settles or when someone asks for them, and simplify interactive elements. On a phone with a mid-range processor, every extra script costs more than it does on your office computer.
CLS: Cumulative Layout Shift (Visual Stability)
What it measures: how much content unexpectedly moves around while the page loads. You’ve felt this: you go to tap “Call Now” and a banner loads above it, pushing the page down so you tap something else.
Target: 0.1 or less is “good.” Up to 0.25 “needs improvement.” Higher is “poor.” CLS is a score, not a time.
Common causes:
- Images and videos without set dimensions, so the browser doesn’t reserve space for them.
- Cookie banners, promo bars or ads injected at the top after the page has drawn.
- Web fonts that load late and change the size of text.
- Embedded maps, review widgets or social feeds that pop in at a different size.
Plain-language fixes: give every image and embed a defined width and height (or aspect ratio), reserve space for banners or show them as overlays that don’t push content, and configure fonts so the fallback is close in size to the final font.
Quick Reference Table
| Metric | What it asks | Good | Poor | Usual suspects |
|---|---|---|---|---|
| LCP | How fast does the main content appear? | 2.5 s or less | Over 4 s | Heavy hero images, slow hosting |
| INP | How fast does the page respond to taps? | 200 ms or less | Over 500 ms | Too much JavaScript, third-party widgets |
| CLS | Does the layout stay put? | 0.1 or less | Over 0.25 | Images without sizes, late banners |
How Google Decides You Pass
Google evaluates each metric at the 75th percentile of real page visits over the previous 28 days. In plain terms, at least three out of four visits need to hit the “good” threshold for that metric. That’s why a page can feel fast on your Wi-Fi and still fail: many of your visitors are on phones with weaker connections.
Mobile and desktop are assessed separately. Since most local searches happen on phones, the mobile result usually matters more, and Google indexes the mobile version of your site anyway, as explained in our post on mobile-first indexing.
To see your own numbers, check the Core Web Vitals report in Google Search Console or run a page through PageSpeed Insights. If those reports look like alphabet soup, our walkthrough on reading a PageSpeed Insights report explains which sections to trust and what to fix first.
Frequently Asked Questions
Why does my site show “no data” for Core Web Vitals?
Field data comes from real Chrome users, and Google only reports it when a page or site has enough visits. Smaller sites often see “not enough data” for individual pages. In that case, use lab tests as a guide and check the site-wide (origin) data if it’s available.
If I pass Core Web Vitals, will I rank higher?
Not automatically. Relevance and content quality come first. Passing removes a possible disadvantage and improves the experience for visitors, which supports conversions whether or not rankings move.
Does FID still matter?
No. INP officially replaced FID as a Core Web Vital in March 2024, so any report or tool still emphasizing FID is out of date. Focus on INP for responsiveness.
Turning Green Scores Into a Better Site
The three vitals are really a checklist for a site that feels good to use: load the important thing first, respond instantly, and don’t move things around. Fixing them usually means trimming bloat rather than adding anything new. If your scores are stuck in the red and you’d like them diagnosed and fixed properly, our website speed optimization service focuses on exactly these metrics.