Skip to content
digitalaudits.com.au

Core Web Vitals in plain English, and how to pass them

By · 5 min read · Published · Updated

Core Web Vitals in plain English and how to pass them

You type your address into Google’s PageSpeed Insights and the first thing on the screen is a red banner: “Core Web Vitals Assessment: Failed”. Underneath sit three abbreviations you’ve never needed to know, each with a coloured bar and a number to three decimal places.

It reads like a verdict. Google has marked your site down, and the page gives no hint of whether that costs you customers this week or whether it matters at all. Most owners either panic and call their web developer, or close the tab and hope it goes away.

A failed Core Web Vitals assessment is a to-do list, and Google hasn’t penalised you for it. Most small business sites fail on one fixable thing, and once you know which one, the job is usually smaller than the red banner suggests.

What the Core Web Vitals measure

Core Web Vitals are Google’s measurements of how a page feels to the person using it. Each one turns a common frustration into a number, and Google publishes bands for every one of them, running from good to poor.

Largest Contentful Paint, or LCP, is how long it takes for the biggest thing on the screen to appear. On most small business sites that’s the hero image at the top of the homepage or the main heading. It’s the closest single number to “how long did I wait?”, and it’s the one behind the load times in your report.

Interaction to Next Paint, or INP, is how quickly the page reacts when someone taps a button or types in a form. A page can look loaded while the phone is still busy running code in the background, and every tap in that time feels ignored. INP can only be measured from real visitors, because it needs someone to tap.

Cumulative Layout Shift, or CLS, is how much the page jumps around while it loads. It’s the one you’ve felt when an image loads above a button just as you reach for it, and your thumb lands on something else. It’s a score with no units, and lower is better.

Core Web Vitals bands
MeasureGoodNeeds workPoor
Largest Contentful Paint (LCP)2.5 seconds or lessUp to 4 secondsOver 4 seconds
Interaction to Next Paint (INP)200 milliseconds or lessUp to 500 millisecondsOver 500 milliseconds
Cumulative Layout Shift (CLS)0.1 or lessUp to 0.25Over 0.25

What “Core Web Vitals assessment: failed” means and how to fix it

The assessment at the top of PageSpeed Insights comes from Google’s records of real Chrome users who visited your page, or your whole site, over the last 28 days. Google looks at the experience three quarters of those visits beat, and if any of the measures it has data for falls outside the good band, the assessment fails.

That has two consequences. The first is that a small site often sees “No data” instead of a pass or a fail, because Google only publishes figures once enough people have visited. The second is that a fix won’t turn the banner green the next day. The assessment catches up as new visits replace old ones, so give it about four weeks after a change before you judge it.

To fix a failed assessment, expand the report and find the measure shown in red or orange. Fix that one first and leave the others alone until it’s in the green. For LCP, start with the hero image, which is usually far larger than it needs to be. For CLS, give every image and embed a set width and height so the browser can save space for it before it arrives. For INP, remove the plugins and chat widgets you don’t use, because each one adds code the phone has to run before it can respond to a tap.

Our scan shows the same real-visitor data beside your score as a “Real visitors” rating whenever Google publishes it. A rating of Good there means your site passes Google’s Core Web Vitals assessment.

Why most small sites fail on one thing

Small business sites fail the assessment in a predictable way. Someone uploaded photos straight from a phone or a stock library, and nobody resized them. The hero image ends up as a 4 MB file shown in a space that needs a tenth of that, and LCP fails on its own while everything else passes.

CLS is the next most common failure, and it usually comes from one element, such as a banner that loads late or a review widget that pushes the page down when it appears. Once you’ve found which element moves, the fix tends to take minutes.

INP problems are rarer on simple sites. They build up on sites that have collected plugins over the years, where a slider, a popup, an analytics tag and a booking widget all compete for the same phone. You don’t need to understand the code to fix most of them. Switch off one plugin at a time and test again.

A fix order that works

Start with a lab test, because it gives you an answer straight away while the real-visitor data takes weeks. Run a website speed test on your homepage and your busiest service page, and look at which numbers are marked Poor or Needs work. Our scan loads your page from Sydney on a fast connection, so if it’s slow even there, the page itself is too heavy.

Fix the biggest item first. For most sites that’s images, and our guide to image optimisation for non-designers covers how to resize and compress them without a designer. If images aren’t the problem, why is my website slow? walks through the other usual causes, from slow hosting to scripts that hold up the first paint.

Test again after each change, so you know which fix made the difference. Then leave it for four weeks and check the real-visitor rating. If it’s still failing, the lab test will usually show you what’s left.

How much the assessment matters

Core Web Vitals are one of many signals Google uses to rank pages, and a small one next to whether your page answers what someone searched for. Between two similar pages from two similar businesses, the one that loads quickly and stays still has an edge. The bigger effect is on the visitors themselves, who leave slow, jumpy pages before they ever see your phone number.

Aim for a site that doesn’t lose people while it loads. Passing the assessment is a reliable sign that yours doesn’t, and a perfect score adds little on top.

Fix the red one first, and check again in a month.

Want the full picture? See what our free speed audit checks

Common questions

Does a failed Core Web Vitals assessment hurt my rankings?

A little, at most. Core Web Vitals are one of many signals Google uses, and a page that answers the search well will still outrank a faster page that doesn't. The bigger cost is visitors leaving slow or jumpy pages before they contact you.

Why does my speed score change every time I test?

Every test is one load of your page at one moment, and your hosting, your scripts and the network all vary a little from run to run. Look at the trend over a few tests and the fixes, not a few points either way.

What's the difference between lab data and field data?

Lab data comes from a test run at one moment, which is what our scan does from Sydney. Field data comes from real Chrome users visiting your site over the past 28 days, and Google only publishes it once a site has enough visitors.

How long does it take to pass after I fix something?

The assessment uses the last 28 days of real visits, so allow about four weeks for a fix to show. A lab test, like our scan, shows the improvement straight away.

Run a speed audit

See your real results and the fixes that matter most.