Home/Blog/Core Web Vitals Explained: What LCP, INP and CLS Mean for Your Business

// WEB DESIGN

Core Web Vitals Explained: What LCP, INP and CLS Mean for Your Business

Google scores your site on three numbers taken from real visitors on real phones. Here is what they measure, the scores to aim for and which fixes are worth paying for.

Core Web Vitals Explained: What LCP, INP and CLS Mean for Your Business

Google grades the pages of your website on three numbers, collected from real visitors on their own phones and laptops. Most business owners have never looked at them. Core Web Vitals, explained in one sentence: they measure how fast the main content appears, how quickly the page reacts when someone taps, and whether things jump around while it loads.

You don't need to be a developer to read them, and you don't need a perfect score. You need to know what the three numbers mean, where the pass mark sits, how much they really count for rankings and which problems are worth paying to fix.

What Core Web Vitals measure

Core Web Vitals are part of what Google calls page experience. There are three of them, and each one answers a question a visitor would ask if they could.

LCP: how long until the main content shows?

Largest Contentful Paint is the time until the biggest element on the visible screen has loaded. On most business sites that is the hero image, a product photo or a large headline. For the visitor, LCP is the moment the page stops looking empty.

INP: does the page react when I tap?

Interaction to Next Paint measures the delay between a click, tap or key press and the next visible change on screen. A menu that opens half a second late, or a filter that freezes the page, means a poor INP. It replaced an older metric, First Input Delay, in March 2024. INP is stricter, because it looks at every interaction during a visit, not only the first one.

CLS: does the layout stay still?

Cumulative Layout Shift scores how much content moves without warning. You have seen it happen: you go to tap a link, a banner loads above it, and you tap the wrong thing. CLS is a score rather than a time, and lower is better.

The scores Google calls good

Google publishes fixed thresholds for each metric. According to web.dev, Google's site for developers, a page passes when:

  • LCP is 2.5 seconds or less
  • INP is 200 milliseconds or less
  • CLS is 0.1 or less

A page is rated poor above 4 seconds for LCP, 500 milliseconds for INP or 0.25 for CLS. Anything in between is labelled "needs improvement".

Two details matter more than the numbers themselves. Google judges each metric at the 75th percentile, so three out of four visits must hit the target, not just your own visit on the office wi-fi. And mobile and desktop are scored separately. On the sites we build for Bulgarian businesses, phones usually bring most of the traffic, so the mobile score is the one to watch.

Do Core Web Vitals affect Google rankings?

Yes, but less than many SEO tools suggest. Google's own page experience documentation says that Core Web Vitals are used by its ranking systems. The same page adds that Google "always seeks to show the most relevant content, even if the page experience is sub-par."

Relevance comes first. A slow page that answers the searcher's question will usually beat a fast page that doesn't. In our experience, speed works more like a tiebreaker between pages of similar quality, and that situation is common in local searches such as "dentist Sofia" or "accountant Plovdiv". Our guide to what SEO optimisation involves shows where speed fits among the other ranking factors.

The stronger argument for good scores is what happens after the click. In research commissioned by Google, Deloitte found that a 0.1-second improvement in mobile site speed went with an 8.4% rise in conversions for retail sites and 10.1% for travel sites. Google paid for the study, so treat the exact figures with some caution. The direction matches what we see on client sites, though: people leave pages that feel slow.

How to check your Core Web Vitals

You can check your own scores in about ten minutes with three free tools:

  • PageSpeed Insights. Paste in the address of any page. The top section shows field data from real Chrome users over the previous 28 days. The lower section is a lab test run on the spot. If the top section says there isn't enough data, your site has too few visitors for Google to report on, and the lab test is your best guide.
  • Google Search Console. Its Core Web Vitals report sorts your pages into good, needs improvement and poor, for mobile and desktop separately. It is the best view of the whole site rather than one page.
  • Chrome DevTools. Built into the Chrome browser, and useful when a developer needs to see exactly which image or script causes the problem.

Field data covers a rolling 28-day window. After a fix, the report improves gradually over about four weeks, so don't judge a change after two days.

What usually hurts each score, and how to fix it

Most sites that fail share the same handful of problems. The fixes range from an afternoon's work to a rebuild.

Slow LCP

The usual causes are an oversized hero image, slow hosting and a page that waits for several scripts before it shows anything. Compressing images, serving them in modern formats such as WebP or AVIF, adding caching and moving to better hosting fix most cases. A 3 MB photo straight from the camera is still one of the most common problems we find in audits.

Poor INP

INP suffers when the browser is busy running JavaScript. Chat widgets, tracking tags, heavy page builders and sliders all compete for the same processor. On a mid-range Android phone that competition is far more visible than on the laptop where the site was approved. Removing scripts nobody uses is the cheapest fix. Problems built into the theme take longer.

High CLS

Layout shift nearly always comes from images and embeds without a set size, web fonts that load late, and banners or pop-ups that push content down. These are usually quick fixes: reserve space for every image and embed, and show banners over the content instead of above it.

If a site fails all three and runs on an old theme with dozens of plugins, patching can cost more than it saves. At that point a rebuild is often the cheaper option. Our article on website redesign costs helps you decide, and Next.js vs WordPress explains why the platform choice affects these scores from day one.

The verdict

Check your Core Web Vitals every few months and fix them when they turn red, but don't let them become an obsession. Get all three into the green on mobile, then spend the remaining effort on content and offers, which move rankings and sales far more. If you are planning a new site, write passing scores into the brief as a requirement. It costs little at the start and a lot to add later. We test every site we build against all three before launch, as part of our marketing site service, and our pricing page shows what that costs.

Frequently asked questions

What are Core Web Vitals in simple terms?

Three measurements Google uses to judge how a page feels to use: how fast the main content loads (LCP), how quickly the page responds to taps and clicks (INP), and how stable the layout stays while it loads (CLS).

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, reached by at least 75% of visits. A page that meets all three passes the assessment.

Are Core Web Vitals a ranking factor?

Yes. Google confirms that its ranking systems use them. Their weight is modest, though: relevant, useful content still ranks ahead of a faster page that answers the question less well.

Why does PageSpeed Insights give a different score each time?

The 0 to 100 performance score comes from a lab test, which varies with network and server load from one run to the next. The Core Web Vitals assessment at the top uses 28 days of real-user data and changes slowly. Base your decisions on that field data.

Why is there no Core Web Vitals data for my site?

Google only reports field data when a page or site has enough Chrome visitors. Smaller sites often show no data at all. In that case, use the lab results in PageSpeed Insights as your guide.

How long does it take to improve Core Web Vitals?

Simple fixes such as compressing images or reserving space for embeds take hours to days. Because Google's field data covers the previous 28 days, expect the reports to catch up over roughly four weeks after the change goes live.

Find out what is holding your scores back

Send us your site's address. We'll look at its Core Web Vitals, explain what is slowing it down and tell you whether a few fixes or a rebuild makes more sense.

Start the conversation →