Core Web Vitals, Explained for Business Owners

Core Web Vitals are three scores Google uses to measure how a real person experiences your website: how fast the main content loads, how quickly the page responds when they tap or click, and whether the layout stays still instead of jumping around while it loads. Google uses these scores as a ranking signal, and they line up almost exactly with whether visitors stay or leave. You do not need to understand the engineering to act on them. You need to know what the three numbers mean, whether yours are good, and what to do if they are not.

The name sounds technical, and the official documentation is written for developers, so most business owners skip it and assume it is a problem for the agency to handle. It is not, entirely. Core Web Vitals decide part of where you rank on Google and how many visitors give up before they ever see your offer, and both of those are business outcomes, not engineering trivia. This guide explains the three metrics in plain language, tells you the target for each, and shows you how to check and improve your own site.

What Core Web Vitals actually are

There are exactly three, and each one measures a different part of the loading experience. Google publishes a clear "good" threshold for each, measured on real visitors using your site, weighted toward mobile because that is where most people are.

• Largest Contentful Paint (LCP) measures loading. It is the time until the biggest thing on screen, usually your main image or headline, has appeared. Good is 2.5 seconds or less. This is the "how long until I can see something useful" score.
• Interaction to Next Paint (INP) measures responsiveness. It is how quickly the page reacts when a visitor taps a button, opens a menu, or fills a field. Good is 200 milliseconds or less. This replaced the older First Input Delay metric in 2024 and is stricter, because it watches every interaction, not just the first.
• Cumulative Layout Shift (CLS) measures visual stability. It is how much the page jumps around while it loads, the annoying moment where you go to tap a button and an ad or image shoves it somewhere else. Good is a score of 0.1 or less. Lower is better, and zero is perfect.

A site "passes" Core Web Vitals when all three are in the good band for most of your real visitors over a rolling 28-day window. Passing two out of three is not passing. That matters, because a site can load quickly (good LCP) and still fail because a slow, heavy script makes every tap sluggish (bad INP).

Why Core Web Vitals matter for your business

Two reasons, and both cost you money when the scores are bad. First, ranking. Google has confirmed Core Web Vitals are a ranking signal. They are not the biggest one, content relevance still wins, but when you and a competitor are otherwise close, the faster, more stable site gets the edge. On competitive local searches, that edge is the difference between page one and page two.

Second, and larger, is conversions. These metrics were chosen precisely because they predict behaviour. Research by Google found that as load time goes from one second to three, the chance a visitor bounces rises sharply, and it keeps climbing from there. A layout that jumps while it loads makes people mis-tap and lose trust. A sluggish page makes them think your business is sluggish too. You are not optimising an abstract score. You are removing the friction between a visitor arriving and a visitor contacting you.

How to check your own scores

You can see your numbers in a few minutes, for free, without installing anything. Use whichever of these fits how much detail you want:

1. PageSpeed Insights (pagespeed.web.dev) is the fastest start. Paste your URL and it gives you LCP, INP, and CLS for both real-world data and a lab test, plus a specific list of what to fix. Check the mobile tab, not desktop, because mobile is what Google weights.
2. Google Search Console has a Core Web Vitals report under the Experience section. It groups every page on your site into good, needs-improvement, and poor, using real visitor data, so you can see which templates are dragging you down.
3. Our own free website audit rolls the same performance signals into a single score with the fixes in plain language, in under a minute and with no signup, if you want the summary rather than the raw developer output.

One important distinction: lab data is a single test from Google servers, while field data (labelled as coming from real users) is what actually counts for ranking. If they disagree, trust the field data. It reflects your real visitors on their real devices and networks.

How to fix each one

The good news is that most Core Web Vitals problems come from a short list of causes, and fixing them is usually removing weight rather than adding features. Here is what actually moves each metric.

To improve LCP (loading)

The usual culprit is a large, unoptimised hero image or a slow server response. Compress and correctly size your main image, serve it in a modern format, and make sure it is not waiting behind a pile of scripts to load. Cutting unused JavaScript and CSS helps here too, because the browser downloads less before it can paint your content. In our aggregated audit data, unused code is one of the single most common issues we find.

To improve INP (responsiveness)

Sluggish taps are almost always caused by heavy JavaScript blocking the browser while it tries to respond. Third-party scripts are frequent offenders: chat widgets, analytics, ad tags, and tracking pixels that each add a little delay until the page feels stuck. Audit what is actually running, remove what you do not need, and load the rest so it does not block interaction. Fewer, leaner scripts fix most INP problems.

To improve CLS (stability)

Layout jumps happen when the browser does not reserve space for something before it loads. The fixes are specific and reliable: set explicit width and height on images and video so the space is held, reserve room for ads and embeds, and avoid injecting banners above existing content. Web fonts that swap in late can also nudge the layout, which is a smaller but real cause.

When to worry, and when not to

Do not chase a perfect score for its own sake. The goal is to land all three metrics in the good band for your real visitors, not to hit 100 in a lab test. If your field data already shows green across LCP, INP, and CLS, your Core Web Vitals are doing their job and your time is better spent on content and offers. If one or more is in the poor band, especially on mobile, that is worth fixing soon, because it is quietly costing you both rankings and enquiries. And if you inherited a site built years ago on a heavy platform stacked with plugins, the vitals are often the clearest early sign that the site is carrying more weight than it can afford.

The honest test is simple. Open your own site on your phone, off wifi, and pay attention. Does the main content appear quickly, does the first tap respond instantly, and does anything jump under your finger? If the answer feels wrong, your visitors feel it too, and the numbers will confirm it.

See where your site stands

Core Web Vitals are one of the few ranking factors you can measure precisely and fix without guesswork. Start by checking yours: our free website audit gives you your performance score and the specific issues holding it back, in plain language and in under a minute, with no signup. If it turns up problems you would rather hand off, book a free discovery call and we will walk through your results and the fastest wins together.