Core Web Vitals for Small Business Sites: The 20% That Moves Rankings

Core Web Vitals get discussed as though they were the whole of SEO. They are not — relevance and links matter far more. But they are a genuine tiebreaker between comparable pages, and more importantly, a slow site quietly costs you conversions whether or not it costs you rankings.

The three metrics, without the jargon

LCP — Largest Contentful Paint

How long until the biggest thing on screen appears. Usually your hero image or headline. Target: under 2.5 seconds. This is the one small business sites fail most often, and it is almost always an oversized hero image.

INP — Interaction to Next Paint

When someone taps a button, how long before something visibly happens. Target: under 200 milliseconds. Failures here come from heavy JavaScript blocking the main thread — chat widgets, popup builders, and analytics stacks are the usual suspects.

CLS — Cumulative Layout Shift

How much the page jumps around while loading. Target: under 0.1. Caused by images without dimensions, ads inserted after load, and web fonts swapping in late.

The fixes that account for most of the gain

1. Compress and resize your images. The most common single failure we find is a 3 MB hero photo scaled down in the browser. Serve WebP or AVIF, sized for the largest slot it actually occupies. This alone often fixes LCP outright.
2. Set width and height on every image. Two attributes. Reserves the space so nothing jumps. Fixes most CLS in one pass.
3. Preload the LCP image and stop lazy-loading it. Lazy-loading the hero is self-defeating — it is the element being measured.
4. Audit your third-party scripts. Open the network tab and count. Most small business sites carry two or three tags nobody has needed for a year. Each one competes for the main thread.
5. Use `font-display: swap` and self-host your fonts. Removes a render-blocking round trip to a third-party domain.
6. Put a CDN in front of the site. Cloudflare's free tier is genuinely sufficient for most small business traffic, and it removes a large chunk of latency for visitors outside your hosting region.

What is not worth your time

• Chasing a perfect 100 score. The difference between 92 and 100 is invisible to users and to rankings.
• Micro-optimising CSS delivery on a site that still ships a 3 MB image.
• Switching frameworks for performance reasons alone. The framework is rarely the bottleneck; the assets are.

A realistic order of work

Run PageSpeed Insights on your three most important pages, on mobile. Fix images first, then layout shift, then scripts. Re-measure after 28 days — field data is a rolling four-week window, so changes do not show up immediately no matter how well they worked.

Then stop. Once you are inside the thresholds, further speed work has almost no ranking value, and your effort is better spent on content and links.