Core Web Vitals are three numbers that describe how your page feels to visitors. The first tracks how fast the main content shows up. Another tracks how fast the page reacts to a tap. The third tracks how much the page jumps while it loads. Good scores help, but relevance still decides rankings.
What the three numbers track
You saw a warning in Search Console, and it points to three measures of page experience. The first is Largest Contentful Paint. Google's web.dev says LCP measures how long the main content takes to appear, and sites should aim for 2.5 seconds or less.
The second is Interaction to Next Paint. Google's web.dev says INP measures how fast the page responds to a tap, click, or key press, and 200 milliseconds or less means good responsiveness. The third is Cumulative Layout Shift. Google's web.dev says CLS measures how much the page jumps around while loading, and sites should aim for a score of 0.1 or less. Together, these three give you a picture of what a real visitor feels when a page opens on their phone or laptop.
The scores your site should hit
Each metric has a clear target, and the table below shows all three in one place. Keep these numbers handy when you read your report.
| Metric | What it measures | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How fast the page responds to a tap, click, or key press | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
One more detail shapes how these scores get counted. Google's web.dev says each metric is measured at the 75th percentile of page loads, split between mobile and desktop. So your score reflects most visits. A single quick load on a good day won't set the number.
Where the report data comes from
Your report leans on real visits. Google Search Console Help says the Core Web Vitals report shows how pages perform based on real-world usage data, and that data comes from the Chrome UX Report, or CrUX. So the numbers reflect how actual people load your pages.
One recent change is worth knowing. Google's web.dev says INP replaced First Input Delay as a Core Web Vital on March 12, 2024. If you saw an older guide that named First Input Delay, that guide is out of date. INP is the responsiveness metric to watch now.
What good scores do and don't do
Good numbers help. They don't decide everything, though. Google Search Central says good results in the Core Web Vitals report "doesn't guarantee that your pages will rank at the top of Google Search results." It also says, "Google Search always seeks to show the most relevant content, even if the page experience is sub-par."
Speed and stability support your pages, and relevance still steers the ranking. Chasing a perfect score on a page few people visit won't move much. Fix the pages people use most first, because that work reaches the largest share of your visitors and gives you the best return on the time you spend.
How to check and improve your scores
Work through these steps in order. Each one moves you closer to good numbers on the pages that count.
- Open the Core Web Vitals report in Search Console. Read which pages get flagged.
- List those pages by traffic. Put the most visited ones at the top.
- Check each metric against its target. LCP wants 2.5 seconds or less, INP wants 200 milliseconds or less, and CLS wants 0.1 or less.
- Look at mobile and desktop apart. Scores split between the two, so a page can pass on one and fail on the other.
- Fix the top page first. Then work down the list, because the busiest pages reach the most visitors.
- Wait, then recheck. The report uses real visits from CrUX, so new numbers take time to show.
Follow these steps and you spend effort where it helps most. Begin with the busiest pages, and keep relevance in mind while you clean up the scores.
Want a hand with your scores? See our web development service.
