Core Web Vitals Explained Simply — The 3 Speed Scores Your Website Must Pass

Ask ten business owners whether website speed matters and all ten will say yes. But "speed" is a vague word. Does it mean how fast the page appears, how quickly the buttons respond, or how stable the layout feels while you read? Google's answer to that question is Core Web Vitals: three specific measurements that describe what it actually feels like to visit a page. They are not secret formulas or tools you have to buy. They are three named scores — loading, interactivity, and visual stability — and Google publishes clear pass thresholds for each. If you run a business website, these three scores are worth understanding, because they are part of how Google assesses your site's page experience, and more importantly, they describe real frustrations your visitors may already be having.

The Two-Minute Answer: What Must My Website Pass?

Core Web Vitals consist of exactly three metrics. Largest Contentful Paint (LCP) measures loading: the largest visible element on the page — usually a hero image or headline block — should render within 2.5 seconds of the page starting to load. Interaction to Next Paint (INP) measures interactivity: when a visitor taps a button, menu, or link, the page should respond visually within 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability: elements on the page should not jump around as it loads, and the shift score must be 0.1 or less. Google evaluates these against real user visit data at the 75th percentile, separately for mobile and desktop, and a page only passes when all three metrics meet their targets. All three metrics are currently at what Google calls the "Stable" lifecycle stage, meaning they are established, reliable measurements rather than experimental ones.

The 3 Metrics, in Visitor Terms

Forget the technical names for a moment. Here is what each metric feels like from the visitor's chair — which is exactly the perspective that matters for your business.

1. LCP — How Long the Visitor Stares at a Blank Screen

Largest Contentful Paint is the loading score. It measures the time between the moment the page starts loading and the moment the largest piece of content — typically a hero image, a large heading, or a banner — becomes visible. If your homepage takes five seconds before anything meaningful appears, your LCP is poor, and many visitors will leave before they ever see your offer. A good LCP is 2.5 seconds or less from the start of the page load. The most common cause of a slow LCP is oversized or uncompressed images, especially large hero images that were uploaded at full camera resolution. On mobile connections, those giant files take noticeably longer to arrive.

2. INP — Whether Buttons Actually Respond When Tapped

Interaction to Next Paint is the interactivity score. It measures how quickly the page visually responds when a visitor interacts with it — tapping a menu, clicking "Add to Cart", or typing into a contact form. If a visitor taps a button and nothing visibly happens for a second, they will tap it again, get confused, or assume the site is broken. A good INP is 200 milliseconds or less. The usual culprit behind poor interactivity is heavy scripts running on the page: too much JavaScript, chat widgets, pop-ups, and analytics tools all competing for the browser's attention can delay the page's response to a tap or click.

3. CLS — Whether the Text Jumps While Someone Is Reading

Cumulative Layout Shift is the visual stability score. It measures how much the page's layout moves around unexpectedly while it loads. Everyone has experienced this: you are about to tap a button or read a line of text, and the page suddenly shifts, pushing the content somewhere else. It is annoying on a blog and dangerous on a checkout page, where a layout jump can make a customer tap the wrong button. A good CLS is 0.1 or less. The typical causes are images added to a page without defined dimensions and web fonts that load late, forcing the browser to rearrange everything once they arrive.

How the Scores Are Judged: the 75th Percentile Rule

One thing that surprises many owners is that these scores are not measured in a lab on a fast office connection. They are measured from field data — real visits by real users on real devices and real networks. Google looks at the 75th percentile of page loads, which roughly means the score must be good for at least three-quarters of actual visits, not just the average visit. The measurements are also segmented across mobile and desktop, because a page can load fine on a desktop with broadband and still fail badly on a mid-range phone with a weak connection — and in India, the mobile experience is usually the one that decides whether a customer stays. A page passes only when all three metrics meet their targets at the 75th percentile. All three metrics currently sit at the "Stable" lifecycle stage, which simply means Google considers them established and dependable measurements, not experiments that might change next month.

Check Your Own Website in Two Minutes

You do not need to hire anyone to find out where your site stands. Google offers a public tool called PageSpeed Insights: type in your website address and it reports your Core Web Vitals scores along with plain-language guidance on what is slowing the page down. Check your homepage and at least one other important page, such as your services or contact page, and look at both the mobile and desktop results separately. If a metric shows up in the red or amber range, that is a concrete signal — not a vague feeling — that visitors on that page are having a poor experience. Make a note of which of the three metrics is failing, because that tells you exactly where the fix should start.

Typical Fixes, Explained Simply

You may not fix these yourself, but understanding the fix categories helps you have an intelligent conversation with whoever builds or maintains your site. The common remedies are refreshingly straightforward.

For a failing LCP, the usual answer is image discipline: compress images before uploading them, serve them at the size they will actually be displayed (not ten times larger), and make sure the most important content — the hero section — loads before everything else. A page whose hero image is a 6 MB file can often drop under the threshold just by serving a properly sized, compressed version.

For a failing INP, the usual answer is script discipline: reduce the amount of JavaScript the page has to chew through before it can respond. That means removing unnecessary pop-ups and widgets, deferring non-essential scripts, and keeping the page's interactive code lean. Sites that bolt on tool after tool over the years are the classic offenders here.

For a failing CLS, the usual answer is layout discipline: give images explicit width and height dimensions so the browser reserves the right amount of space before the image arrives, and handle web fonts so text does not reflow when the font loads. These are small code-level habits that cost nothing but prevent the most visible kind of page jank.

Why This Matters When Choosing a Website Vendor

Core Web Vitals are part of how Google assesses page experience, which feeds into how your site is evaluated — but be careful about how vendors talk about this. Nobody can promise you a top ranking just by fixing these scores; they are one part of a much larger picture, alongside your content, relevance, and overall SEO foundations. (If you want to understand those foundations first, Google's own starter guidance is a good starting point — see our summary of SEO basics for small business websites.) What you can and should do is treat performance as a requirement, not a bonus. When comparing vendors, ask directly: how do you handle image optimisation, how do you keep scripts light, and will you show me the PageSpeed results before handover? A vendor who builds fast, stable pages is giving you a site that converts better regardless of any search ranking discussion. Our website development cost guide for India explains what to expect at different budget levels, so you can judge whether performance work is included or an extra.

Frequently Asked Questions

Are Core Web Vitals a guaranteed ranking factor?

No. They are part of Google's page-experience assessment, not a guaranteed path to higher rankings. Think of them as the experience foundation: passing them removes a handicap, but rankings still depend heavily on content quality, relevance, and many other signals. Any vendor who promises top rankings from speed fixes alone is overselling.

My site feels fast on my own phone. Why does it fail?

Because your phone, your cached visit, and your Wi-Fi are not your customers' reality. The scores are measured at the 75th percentile of real user visits, including slower devices and weaker connections. Your own experience is the best-case scenario, not the typical one.

How often should I check these scores?

Check after any major change — a redesign, new features, added plug-ins — and then periodically, perhaps once a quarter. Scores drift over time as content and tools accumulate, which is exactly how a once-fast site slowly becomes a slow one.

Can a non-technical owner fix failing scores?

Sometimes partially: compressing images before uploading and removing unused widgets are genuinely within reach. But layout and script issues usually need a developer. The important part is that you can diagnose the problem yourself with the public tools, so you know exactly what to ask your developer to fix.

Sources

• Google web.dev, "Web Vitals" — official documentation, published 4 May 2020, last updated 31 Oct 2024 — https://web.dev/articles/vitals

Ready Multi Service helps small businesses get online with professional website design and digital services — built to load fast, stay stable, and turn visitors into customers. Talk to us about your website.