Core Web Vitals are Google's three measurements of how a page feels to use: how fast the main content appears, how quickly the page responds when you interact with it, and how much the layout jumps around while loading. They are ranking signals, they are measurable for free, and on most small business sites they are worse than the owner thinks. This guide explains each metric in plain English, how much they really matter, and the fixes that usually move the numbers.
The three metrics, translated
LCP: Largest Contentful Paint
How long until the biggest thing on the screen, usually your hero image or headline, actually appears. Google's threshold for "good" is 2.5 seconds on a typical phone connection. This is the metric visitors feel most: past a few seconds, people start leaving before they ever see your pitch.
INP: Interaction to Next Paint
When someone taps a menu or a button, how long before the page visibly responds. Under 200 milliseconds feels instant. Slow INP usually means the page is busy running JavaScript it did not need, and it makes a site feel broken even when it eventually works.
CLS: Cumulative Layout Shift
How much the page jumps around while loading. You have felt this: you go to tap a button and an ad loads above it, shoving everything down, and you tap the wrong thing. Google scores the total movement; under 0.1 is good. Shifts are usually caused by images and embeds that load without reserved space.
How much do they matter for rankings?
Honestly: they are a real ranking signal, but a modest one. Great Core Web Vitals will not rescue thin content, and a genuinely better answer with mediocre scores will usually still outrank a fast page with a weak one. Content and relevance come first.
But that framing undersells the business case. Page speed affects every visitor, not just Google's crawler. Slow pages lose customers directly: people leave, forms go unfilled, calls do not happen. Fixing Core Web Vitals is one of the few SEO tasks that pays even if rankings never moved, because more of the traffic you already get turns into business. In competitive local markets where everyone's content is similar, it is also a genuine tiebreaker.
How to check your scores
Run your homepage and your most important service page through PageSpeed Insights (free, from Google). Look at the "field data" section first: that is real visitor experience, where lab tests are simulations. Also check the Core Web Vitals report in Search Console, which shows which groups of pages pass and fail across the whole site.
The fixes that usually move the numbers
For slow LCP
- Compress and resize images. The most common problem on small business sites is a photo straight off a phone, ten times larger than needed. Modern formats and sensible dimensions often halve load time alone.
- Better hosting. Bargain shared hosting adds seconds before the page even starts. Moving a slow site to decent hosting is often the single biggest LCP win.
- Cut render-blocking extras. Every plugin, font, and script that loads before content delays it.
For slow INP
- Remove JavaScript you do not need. Old chat widgets, sliders, tracking scripts from campaigns long finished. Page builders and theme bloat are the usual culprits on small sites.
- Load third-party tools only when used. A booking widget can load when someone clicks "book", not on every page view. Ours works exactly that way.
For layout shift
- Give images explicit dimensions so the browser reserves their space before they load.
- Reserve space for embeds and ads, or remove the ones that pay less than they cost in customers.
- Watch late-loading banners. Cookie bars and promos that push content down are classic CLS offenders.
Myths worth retiring
- "I need a perfect 100 score." No. The lab score in testing tools is a diagnostic, not the ranking input; Google uses real-visitor thresholds, and "good" is the bar, not perfection. Chasing 98 to 100 is usually procrastination with charts.
- "My site feels fast on my phone." You are on good wifi with the site cached, probably on a recent phone. Your customers include someone on a mid-range Android on one bar of signal in a parking lot. The field data represents them; trust it over your thumb.
- "A cache plugin fixed it." Caching helps repeat views and time-to-first-byte; it does not shrink a 4MB hero image or delete a bloated script. Plugins patch symptoms; the fixes above remove causes.
- "Speed is a one-time project." Sites regain weight the way kitchens regain clutter: one new widget, one uncompressed photo at a time. Re-test quarterly and after any redesign, which has its own SEO checklist for exactly this reason.
What we do on our own site
We practice this: the site you are reading scores at the top of the range on all three metrics, with layout shift at zero, because it was built that way from the start. Retrofitting is harder than building clean, but it is almost always possible to get a small business site into the green without a rebuild. That work is the core of our technical SEO service.
Where to start
Test your two most important pages today. If they are already green, move your energy to content and links; speed is not your bottleneck. If they are orange or red, fix images and hosting first, strip unused scripts second, and re-test. And if you would rather have the diagnosis done for you, a free audit includes your Core Web Vitals scores with the fixes ranked by impact.