Core Web Vitals Explained for Small Business Owners

If you’ve ever run your website through a speed test and been handed a red score and a list of jargon, you’re not alone. Core Web Vitals are Google’s way of measuring whether a page feels fast and stable to real people. They’re worth understanding because they describe what your customers actually experience, especially on phones.

This guide explains the three metrics in plain English, how to check them, and what to ask your developer for.

The three metrics

LCP: Largest Contentful Paint (loading)

LCP measures how long it takes for the biggest thing in the visible screen, usually a hero image or main heading, to appear. It’s the moment a visitor feels the page has loaded.

Good: 2.5 seconds or less.

INP: Interaction to Next Paint (responsiveness)

INP measures how quickly the page responds when someone taps, clicks or types: opening a menu, pressing “Get a quote,” choosing a date. A slow INP is the frustrating moment where you tap a button and nothing seems to happen.

Good: 200 milliseconds or less.

INP replaced an older metric, First Input Delay, in 2024. If you read advice mentioning FID, it’s out of date.

CLS: Cumulative Layout Shift (visual stability)

CLS measures how much the page jumps around while loading. You’ve seen it: you go to tap “Call now,” an ad or image loads above it, the button moves, and you tap the wrong thing.

Good: 0.1 or less.

How Google measures them

The scores that count are from real visitors using Chrome, collected in the Chrome User Experience Report. Google looks at the 75th percentile: to pass, at least three out of four visits need a good experience. That’s deliberately strict, because it makes sure the experience is good for most people, including those on older phones and patchy connections.

This is why you can get different answers from different tools:

• Field data is what real visitors experienced over the past 28 days. This is what Google uses.
• Lab data is a single simulated test on one device and connection. It’s useful for diagnosing problems, but it isn’t your score.

Low-traffic sites may not have enough visitors for field data. In that case, lab tests are your best guide.

How to check your site for free

1. Search Console → Core Web Vitals. Shows groups of URLs on mobile and desktop as good, needs improvement or poor, based on field data. Start here.
2. PageSpeed Insights (pagespeed.web.dev). Enter a URL to see field data at the top (if available) and a lab test with specific suggestions below.
3. Your own phone. Load your key pages on mobile data, not office Wi-Fi. If it feels slow to you, it feels slow to customers.

What usually goes wrong on small business sites

We see the same handful of causes again and again.

Oversized images

A 4 MB photo straight from a camera, used as a hero image, is the most common LCP problem. Images should be resized to the size they’re displayed at and saved in a modern format like WebP or AVIF.

Too many plugins and scripts

Every chat widget, tracking pixel, slider, popup and font adds code that the phone has to download and run. Heavy JavaScript is the main cause of poor INP. Some of those tools may no longer be in use at all.

Page builders

Drag-and-drop builders make editing easy but often produce bloated pages. That doesn’t mean you must abandon one, but it’s often why a simple page is slow.

Cheap shared hosting

If your server takes a second or more to respond before anything loads, no amount of image optimization will get LCP to good. Fast hosting with a content delivery network (CDN) makes a real difference. It’s one reason we include hosting in our website care plans.

Missing image dimensions and late-loading content

Images without width and height, ads, cookie banners and embedded maps that push content down cause most CLS problems.

Fixes to ask your developer for

You don’t need to know how to do these yourself. Asking for them by name will get a better response than “make it faster”:

• “Resize and convert images to WebP, and lazy-load images below the fold.”
• “Preload the hero image and don’t lazy-load it.”
• “Add width and height to all images and reserve space for embeds and banners.”
• “Remove unused plugins and scripts, and delay non-essential scripts until after the page loads.”
• “Self-host our fonts and limit them to the weights we use.”
• “Check server response time and put the site behind a CDN.”

After changes, field data takes up to 28 days to fully update. Search Console has a “Validate fix” button so you can track progress.

How much does it matter for rankings?

Core Web Vitals are part of how Google assesses page experience, but relevance and content quality matter more. A fast page with nothing useful on it won’t beat a slower page that answers the question. Think of speed as removing a handicap, not as a ranking shortcut.

The business case is stronger anyway: a page that loads quickly and doesn’t jump around on a phone is easier for customers to use and call from. That’s true whether or not it moves rankings.

Building it right from the start

Fixing speed on an old site is often slower and costlier than building a lean one. If your site is due for a rebuild, read our website redesign SEO checklist, browse our sample sites, or see how we approach SEO web design: fast hosting, compressed images and clean code are part of every build.