Core Web Vitals and site speed for SMBs

TL;DR

Core Web Vitals measure loading speed (LCP), responsiveness (INP) and visual stability (CLS). Small businesses improve them by compressing images, reserving image space, trimming scripts, and using caching with fast hosting.

Key takeaways

  • LCP should be under 2.5 seconds, INP under 200 ms, CLS under 0.1.
  • Heavy images slow LCP, heavy JavaScript slows INP, unsized media causes CLS.
  • WebP images sized to display, plus reserved dimensions, fix most problems.
  • Caching and fast hosting are the foundation of good vitals.
  • Measure with PageSpeed Insights and Search Console, then fix one issue at a time.

Core Web Vitals are Google’s way of measuring how a page feels to a real visitor: how fast it shows content, how quickly it responds, and how stable it is while loading. For a small business, getting them right means a faster site, happier visitors and a small ranking edge. This guide explains each metric in plain language and what to actually do about it.

The three metrics, plainly

Largest Contentful Paint (LCP)

LCP measures how long until the biggest visible element, usually a hero image or heading, finishes loading. Aim for under 2.5 seconds. Slow LCP usually comes from heavy images or slow hosting.

Interaction to Next Paint (INP)

INP measures how quickly the page responds when someone taps or clicks. Aim for under 200 milliseconds. Heavy JavaScript is the usual culprit.

Cumulative Layout Shift (CLS)

CLS measures how much the page jumps around as it loads. Aim for under 0.1. The classic cause is images and ads without reserved space, which push content down as they appear.

Why they matter for SMBs

A faster page is not vanity. Visitors abandon slow sites, and for a hotel or restaurant that means lost bookings. Search also uses these signals, so a fast, stable site has a small but real advantage over a sluggish competitor. The effect compounds with good conversion focused design.

Concrete fixes that move the needle

  • Convert images to WebP and size them to how they actually display. A 4000 pixel photo shown at 800 pixels wastes bandwidth.
  • Reserve space for images by setting width and height, which kills layout shift.
  • Defer or remove non essential scripts, especially chat widgets and trackers you do not use.
  • Use a caching layer and a fast host. We cover this in caching explained and managed EU hosting.
  • Optimise images further with the tips in our image SEO guide.

A real example

A typical Elementor restaurant site we see scores poorly because of a full screen autoplay slider and an uncompressed 6 MB hero. Replacing the slider with one optimised WebP image and reserving its dimensions often moves LCP from over 4 seconds to under 2.5, and CLS from a visible jump to nearly zero.

How to measure

Use PageSpeed Insights for a one off check and Google Search Console’s Core Web Vitals report for real visitor data over time. Test on mobile, since that is where most problems and most visitors are. Fix one issue, re measure, repeat. If you would rather have it handled, our maintenance service keeps performance healthy month after month.

Frequently asked questions

What are good Core Web Vitals scores?

A largest contentful paint under 2.5 seconds, an interaction to next paint under 200 milliseconds, and a cumulative layout shift under 0.1, all measured on mobile.

Do Core Web Vitals really affect Google rankings?

They are a real ranking signal, though a modest one. Their bigger value is keeping visitors from abandoning a slow page, which protects bookings and sales.

What is the fastest way to improve site speed on WordPress?

Compress and resize images to WebP, enable a caching layer, remove unused scripts, and host on a fast managed server.