Fix Core Web Vitals on a small-business site in an afternoon

• Core Web Vitals is a tiebreaker signal, not a primary ranking factor — but slow sites lose rankings indirectly via user behaviour.
• LCP (load speed) is usually the biggest and most fixable problem — start there.
• Most small-business wins come from image compression, lazy-loading and cutting unused scripts — no rebuild required.
• Measure on real field data (Search Console / CrUX), not just lab tools, because real users are what Google counts.

Let's set expectations first, because the SEO industry oversells this one: Core Web Vitals will not, by itself, rocket you up the rankings. Google has been clear that it's a tiebreaker — when two pages are otherwise equal, the faster, more stable one wins. What actually hurts you is the indirect damage: a slow, janky site makes people bounce, and those bad user signals drag your rankings down across the board.

The good news is that for a typical small-business site, clearing the thresholds is usually an afternoon's work, not a rebuild. Here's how, in order of effort-to-impact.

TL;DR

There are three Core Web Vitals: LCP (how fast the main content loads), CLS (how much the layout jumps around), and INP (how quickly the page responds to taps and clicks). LCP is usually the biggest problem and the easiest to fix — start by compressing images, lazy-loading what's below the fold, and cutting scripts you don't use. Measure with real field data, not just a lab score.

First, measure the right thing

Run your homepage and one key landing page through Google's PageSpeed Insights, but pay attention to the field data (real Chrome user measurements) at the top, not just the lab score below. Field data is what Google actually counts. You can also see it in Search Console under "Core Web Vitals". Our free SEO audit tool flags the worst offenders if you want a quick first pass.

Note which of the three metrics is failing. Usually it's LCP.

Fix LCP first (the big one)

Largest Contentful Paint is how long until the main thing on the page — usually your hero image or headline — appears. On small-business sites it's almost always dragged down by oversized images and render-blocking scripts. The afternoon fixes:

• Compress and resize images. The single most common culprit is a 4MB hero photo displayed at 800px wide. Resize to the dimensions actually shown and compress (WebP or AVIF format). This one change often fixes LCP on its own.
• Lazy-load below-the-fold images so the browser loads what's visible first and defers the rest (loading="lazy").
• Preload the hero image so the browser fetches it immediately rather than discovering it late.
• Cut or defer unused scripts. Chat widgets, multiple analytics tags, heavy sliders and unused fonts all delay the main content. Remove what you don't need; defer what you do.

For most small sites, those four changes move LCP from "poor" to "good".

Fix CLS (the jumpy layout)

Cumulative Layout Shift is that annoying jump when you go to tap a button and the page shifts because an image or ad just loaded above it. The fixes are simple:

• Set explicit width and height (or an aspect-ratio) on images and embeds so the browser reserves the space before they load.
• Reserve space for anything injected late — banners, cookie notices, ads.
• Preload web fonts (or use font-display: swap carefully) so text doesn't reflow when the custom font arrives.

Fix INP (responsiveness)

Interaction to Next Paint measures how quickly the page reacts when someone interacts. On a typical brochure site this is usually fine; when it isn't, the cause is heavy JavaScript blocking the main thread. Reduce third-party scripts, break up long tasks, and remove anything that runs on every interaction unnecessarily. If your site is a simple WordPress or static build, you'll rarely need to touch this.

When it's not an afternoon job

If your site is built on a bloated theme with a dozen plugins, or a page builder that ships 2MB of JavaScript, the honest answer is that patching Core Web Vitals is treating a symptom. At that point a lean rebuild — which is how we approach web design — fixes speed, CLS and maintainability in one move and usually pays for itself in conversion alone.

Where this sits in the bigger picture

Speed is a supporting act, not the headline. Get it into the "good" band so it stops working against you, then put your energy into content, local signals and authority — the things that actually move rankings. If you want a structured pass over the whole site, our SEO checklist walks through the technical foundations, and our Sydney SEO service covers the ongoing work.