Your homepage loads in 8 seconds. That's why you don't rank.

Every audit we run gets a speed section, and one pattern repeats: sites that "look fine" to their owners but load in 6, 8, sometimes 12 seconds on a phone. The owner never sees it — they visit on office Wi-Fi with a warm cache. Their customers see it on 4G, cold.

Here's the uncomfortable math: studies have shown conversions drop roughly 7% for every extra second of load time, and by eight seconds, more than half your visitors are gone before they saw your headline. Google knows this. That's why speed isn't a vanity metric — it's a ranking input with receipts.

5.2sLCP

Typical slow-homepage LCP

Illustrative example of a common small-business pattern. Google targets under 2.5s. Every second past that is visitors — and crawl equity — bleeding out.

What an 8-second homepage actually costs

Critical

Largest Contentful Paint fails

LCP is how long the biggest visible element — usually your hero image or headline — takes to appear. Fail it, and you fail Core Web Vitals, which Google uses directly as a ranking signal. A slow LCP on your homepage taxes the rankings of your entire domain.

The fix: compress and properly size hero images, add fetchpriority="high", preload the LCP asset, kill render-blocking scripts above the fold.

Critical

Uncompressed hero images

The most common culprit in small-business sites: a 4 MB PNG that a smartphone resizes to 400 pixels wide. The visitor downloads 40× more bytes than they can see — often more than the rest of the page combined.

The fix: WebP/AVIF at correct dimensions, ~100–200 KB for above-the-fold heroes, srcset for everything else.

Warning

Render-blocking scripts in <head>

Every blocking <script> in the head is a red light: the browser must stop, download, execute — only then paint your page. Three analytics snippets stacked up top can silently add 2–3 seconds.

The fix: defer or async everything non-critical, host locally, and audit third-party tags quarterly.

Warning

No caching or CDN

Serving every asset from one origin with Cache-Control: no-store means every visitor re-downloads everything, every visit — and Googlebot burns crawl budget re-fetching static files.

The fix: long max-age on hashed assets, HTML served no-cache, CDN in front if your audience is spread out.

Enhancement

Web fonts loading late

Two font families × four weights, fetched from a third-party origin with no preconnect — text renders invisible or late, and CLS racks up penalties.

The fix: preconnect to font origins, font-display: swap, subset to the weights you actually use.

The speed fix checklist

Get LCP under 2.5s — compress the hero, preload it, defer everything that isn't paint.
Set a byte budget — homepage under ~1.5 MB total is a good first target.
Audit third-party scripts — every tag has a cost; delete the ones nobody reads reports from.
Cache like you mean it — hashed assets get months, HTML gets seconds.
Test on 4G, cold cache — the experience your customers get, not your office Wi-Fi.

Speed is a feature you ship, not a score you chase

Here's the part most speed guides skip: you don't need a perfect 100 Lighthouse score. Going from 8 seconds to 3 captures nearly all the ranking and conversion benefit; squeezing the last 500ms is diminishing returns. Fix the critical items, re-run the audit, move on to content.

The sites that win aren't the fastest sites on the internet. They're the ones that never made their visitors wait for a headline.