Journal · Performance

Core Web Vitals for small business sites: a plain-English guide

Core Web Vitals in plain English for small business websites: what LCP, INP and CLS mean, what good looks like, how to check yours, and what usually slows sites down.

Picture someone on a bus, opening a tutor’s website on their phone. They’re ready to book a trial lesson. The page is slow to appear, so they wait. Then, just as they go to tap “Book now”, a photo finishes loading, the whole page jumps down, and they tap something else entirely.

They wanted to book. The page got in the way. Nobody at the tutor’s end ever finds out it happened.

That little moment, slow to load, slow to respond, jumpy as it settles, is exactly what Google’s Core Web Vitals measure. If you’ve seen the term in Search Console, in an email from your host or in an agency’s sales pitch and wondered whether to worry, this guide explains what they are, how to check yours, and what usually causes problems on small WordPress sites.

I’ve looked after WordPress websites since 2018, mostly for small service businesses. This guide sticks to plain English, and every number in it comes from Google’s own published guidance.

What Core Web Vitals are, in one paragraph

Core Web Vitals are three measurements Google uses to describe how a page feels to real visitors: how quickly the main content appears, how quickly the page responds when you tap or click, and how much the layout jumps around while it loads. Google describes them as metrics that “measure real-world user experience for loading performance, interactivity, and visual stability”.

The three measurements (and what “good” means)

Measurement What it means in real life “Good” is
LCP (Largest Contentful Paint) How long until the biggest thing on screen (often your main photo or headline) appears 2.5 seconds or less
INP (Interaction to Next Paint) How long the page takes to react after someone taps or clicks 200 milliseconds or less (a fifth of a second)
CLS (Cumulative Layout Shift) How much things jump around while the page loads 0.1 or less

Source: web.dev, Web Vitals (Google’s Chrome team).

A few things worth knowing:

  • These are measured on real visits, not just in a test. Google looks at the experience of most of your visitors (the 75th percentile, meaning three in every four visits should hit “good”), separately for phones and computers.
  • INP is fairly new. It replaced an older measurement called FID as a Core Web Vital in March 2024. If you read an older guide that talks about FID, it’s out of date.
  • Phones matter most. Sites often score worse on phones than on computers, because phones and mobile connections tend to be slower, and many of your clients may find you on their phone first.

Do Core Web Vitals affect Google?

Honest answer: they’re one ingredient, not the recipe.

Google says it “highly recommend[s] site owners achieve good Core Web Vitals for success with Search”, and that this, along with other page experience signals, “aligns with what our core ranking systems seek to reward” (Google Search Central).

What that doesn’t mean: fixing your scores won’t, on its own, put you at the top of Google. Helpful, clear content that answers what people search for still matters far more. I can’t promise any change in where you appear, and nobody honestly can.

The better reason to care is simpler. A page that loads fast, responds instantly and doesn’t jump is a page people can actually use. That’s good for your visitors whatever Google does.

How to check your Core Web Vitals

Option 1: Google Search Console (best for real-world data)

If your site is set up in Google Search Console (it’s free), look for Core Web Vitals under Experience in the left-hand menu. It groups your pages into “Good”, “Needs improvement” and “Poor”, for mobile and desktop.

Don’t panic if it says there isn’t enough data. The report is built from real Chrome visitors, so smaller sites often don’t have enough visits yet for Google to show a result. That’s normal for many coaches, therapists and tutors, and it doesn’t mean anything is wrong.

Option 2: A page-by-page test

Google also offers a free tool called PageSpeed Insights, where you paste in one page address. If Google has real-visitor data for that page, it shows it at the top. Underneath, it runs a simulated test, which is useful for spotting problems but isn’t the same as real visits. Treat the simulated score as a clue, not a verdict.

What usually causes problems on small WordPress sites

Slow LCP (the main content takes too long to appear)

  • A huge photo at the top of the page. A picture straight off a phone or camera can be many times bigger than it needs to be.
  • Sliders and carousels that load several large images before showing the first.
  • Slow hosting, especially very cheap shared plans.
  • No caching, so your server builds every page from scratch for every visitor.

Poor INP (the page is slow to react)

  • Too much JavaScript, often from page builders, pop-ups, chat widgets, booking embeds and tracking scripts all loading at once.
  • Lots of plugins each adding their own code to every page, even pages that don’t need it.

High CLS (things jump around)

  • Images without a set size, so the page doesn’t know how much space to save for them. WordPress adds sizes automatically to images from your Media Library, but images added in other ways may miss out.
  • Cookie banners, pop-ups or announcement bars that push content down after it appears.
  • Embeds (videos, booking calendars, social feeds) that load late and shove everything below them.
  • Web fonts that swap in late and change the size of your text.

Where to start (the order I’d go in)

  1. Check Search Console first. If it says “Good” or “not enough data”, don’t spend money chasing scores.
  2. Shrink the big image at the top of your homepage. It’s often the single biggest win for LCP.
  3. Look at what you’ve added over the years: sliders, pop-ups, chat widgets, old tracking codes. Remove what you don’t use.
  4. Make sure caching is switched on, usually through your host or one caching plugin (never two).
  5. Check your cookie banner doesn’t push the page down when it appears.
  6. Test on your own phone, on mobile data, not just on your office Wi-Fi.

Back up before changing anything, and check your contact form and booking links still work afterwards.

For the practical, step-by-step version of all this, read my guide on how to speed up a WordPress website.

Three of the usual fixes each have their own guide: the best caching plugins for small UK businesses, WordPress image optimisation and WordPress hosting for speed. A cookie banner loads on every page too, so it’s worth adding a cookie consent banner the right way.

FAQ

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, for at least three in four visits. A page passes when it meets all three.

Why does Search Console say there’s not enough data?

The report uses real visits from Chrome users. Smaller sites often don’t have enough of those yet. It’s common, and not a sign of a problem.

Do I need a developer to fix Core Web Vitals?

Not always. Shrinking images, removing unused plugins and widgets, and switching on caching are all things many owners can do themselves. Deeper problems, such as a heavy theme or page builder, may need more help.

Why is my score different every time I test?

Simulated tests vary with network conditions and server load at that moment. Real-visitor data in Search Console is steadier, because it’s based on many visits over time.

Not sure where your site stands? Start with a free Website Check

Send me your website address and I’ll look it over and tell you, in plain words, what’s working and what’s holding it back. It arrives within 24 to 48 hours, Monday to Friday. Nothing to sign, no call needed, and nothing on your site gets changed.

Get your free Website Check

Whenever you’re ready, I’m here.

Tell me a little about where you are and where you’d like to be. I’ll reply personally.

Get in touch