Core Web Vitals Explained for Small Business Owners

If anyone has run a speed test on your website, you have probably been handed a report full of acronyms, colored circles and a score out of a hundred. It is easy to come away thinking your site is either fine or doomed, with nothing in between. Core Web Vitals are a more useful way to think about it, because they measure three specific things your visitors actually feel.

Google introduced Core Web Vitals as a small set of measurements of real-world experience: how quickly the main content appears, how quickly the page reacts when someone taps it, and how much the layout jumps around while it loads. Google uses them in its ranking systems, and, more importantly, they describe the difference between a site that feels solid and one that feels broken.

The three measurements

Largest Contentful Paint (LCP) is the time until the biggest piece of content in view, usually a hero photo or a headline, has appeared. It is the closest thing to 'how long until the page looks loaded.'

Interaction to Next Paint (INP) measures how quickly the page responds when someone taps a button, opens a menu or types in a box. It replaced an older measurement, First Input Delay, in March 2024, because it looks at every interaction during a visit rather than only the first one. A page with poor INP feels sticky: you tap 'Call' and nothing seems to happen.

Cumulative Layout Shift (CLS) measures how much things move around unexpectedly. If you have ever gone to tap a link and had an image load above it, shoving it down so you tapped an ad instead, you have experienced layout shift.

What the thresholds mean

Google publishes clear lines for each measurement. LCP is good at 2.5 seconds or less and poor above 4 seconds. INP is good at 200 milliseconds or less and poor above 500. CLS is good at 0.1 or less and poor above 0.25. Anything between is 'needs improvement.'

The important detail is how they are judged. Google looks at the 75th percentile of real visits over the previous 28 days. In plain terms, your page needs to hit the green line for three out of every four visitors, including the ones on older phones and patchy connections. That is a fairer test than a single lab run on a fast office computer, and for a business serving rural Yavapai County, where plenty of visitors are on a single bar of LTE, it is the test that matters. We wrote more about designing for those conditions in Building for Ranch-Road LTE.

Where to see your own numbers

There are two kinds of data, and it helps to know which you are looking at.

So if your PageSpeed score is 62 but your field data shows all three measurements in the green, your real visitors are fine. If the score is 95 but the field data is red, something about real-world use (a slow third-party chat widget, a heavy page that only some visitors reach) needs attention.

What usually causes slow LCP

On small-business sites, a slow Largest Contentful Paint almost always comes down to a handful of causes:

What usually causes poor INP and CLS

Poor INP is mostly about JavaScript. Every script on the page competes for the phone's attention; when a chat widget, two analytics tools, a review carousel and a page builder are all busy, a tap has to wait its turn. The fix is usually subtraction: remove what you don't use, delay what isn't urgent, and keep the code that runs on each tap small.

Layout shift is the easiest of the three to fix. Give every image and video its dimensions in the code so the browser can reserve the space before it arrives. Don't insert banners or cookie notices above content after the page has loaded. Load web fonts in a way that doesn't make text jump when the font arrives.

How much does it matter for ranking?

Honestly: less than relevance, and more than nothing. Google says it uses Core Web Vitals in its ranking systems, but it also says a great experience does not outrank a page that is far more relevant to the search. A fast page about the wrong thing still loses.

The stronger reason to care is your visitors. A page that appears quickly, responds instantly and doesn't jump around is a page people stay on long enough to call you. Our article on what a slow website costs walks through that arithmetic.

A simple plan

Check the Core Web Vitals report in Search Console once a month. If there is field data, fix whatever is red first, starting with the pages that bring in the most visitors. If there isn't enough field data, use PageSpeed Insights on your most important pages and treat the lab results as a guide. After a fix, field data takes up to 28 days to fully reflect the change, so give it time before judging.

If you would like to know where your own site stands, the free audit is a quick start, or ask us to look at the field data with you.