In 2006, Amazon published an internal study showing that every 100-millisecond delay in page load time cost them 1% in revenue. That study has been replicated, refined and confirmed by Google, Walmart, Pinterest, Mozilla and dozens of independent researchers in the two decades since.

The number that's emerged from this body of research — and been confirmed across small businesses, e-commerce stores, professional services and media sites — is consistent: a 1-second delay in page load time reduces conversions by approximately 7%.

For a website getting 200 visitors a month with a 3% conversion rate, that's 6 enquiries per month. A 1-second delay takes that to 5.6. A 3-second delay — which is below average for most small business websites — takes it to 4.8. Over 12 months, that's 14 leads lost purely to page speed. At an average client value of $800, that's $11,200 per year from one metric that most business owners have never even checked.

Why speed affects conversions so directly

The relationship between speed and conversion isn't just about user frustration. There are several distinct mechanisms at work:

The first impression effect

Research from Google shows that visitors form their impression of a website in 50 milliseconds — before they've read a single word. A slow-loading page creates a negative first impression that colours everything that follows. Even if the site eventually loads and looks beautiful, the visitor has already tagged it subconsciously as "unreliable."

The abandonment threshold

53% of mobile visitors leave if a page takes more than 3 seconds to load. This isn't a preference — it's a hard drop-off. Google's research across millions of mobile sessions shows the relationship is nearly linear: at 1 second, almost nobody leaves due to speed. At 3 seconds, 53% have left. At 5 seconds, 90% are gone. Most small business websites load in 4-8 seconds on mobile.

The trust signal

Speed is a proxy for professionalism. When a law firm's website takes 7 seconds to load, potential clients draw conclusions — consciously or not — about the firm's attention to detail, investment in their business, and overall competence. A fast website signals that the business cares about the experience of dealing with them.

The Google ranking penalty

Since 2021, Google has used Core Web Vitals — which include page speed metrics — as a direct ranking factor. A slow website doesn't just convert fewer visitors — it gets fewer visitors in the first place, because Google deprioritises it in search results. This creates a compounding problem: slow sites rank lower, get less traffic, and convert that smaller traffic pool less effectively.

📊 The Speed-Revenue Data

  • 1-second delay = 7% reduction in conversions (Google/Amazon research)
  • 53% of mobile users leave after 3 seconds (Google, 2026)
  • Pages loading in under 1 second convert 3x better than 5-second pages
  • Core Web Vitals directly affect Google rankings since 2021
  • Average small business website loads in 6.2 seconds (AIWebGrade, 2026)
  • Only 11% of small business websites load in under 2 seconds

How to find out your actual speed

Most business owners don't know their website's speed score. Here are three ways to find out:

  1. Google PageSpeed Insights (pagespeed.web.dev) — free, gives you a score out of 100 for both mobile and desktop, with specific issues identified
  2. GTmetrix (gtmetrix.com) — free, gives a letter grade and more detailed waterfall analysis of what's loading slowly
  3. The Brivex AI scanner (brivexai.com/scan) — includes speed as part of a full 47-point audit, alongside SEO, security and mobile usability

Run your site through one of these right now before continuing. The number you get will give context to everything that follows.

What the scores mean

90-100 — FastExcellent
50-89 — ModerateNeeds Work
0-49 — SlowPoor — Losing Revenue

The average small business website scores 41 — in the "poor" range. Most have never checked.

The 7 most common causes of slow websites — and how to fix them

1. Images that are too large

The most common cause of slow websites. A photo taken on a modern phone is 4-8MB. A website image should be under 200KB. Most websites use unoptimised photos directly from cameras or phones.

Fix: Compress all images using Squoosh (free) or convert to WebP format. Impact: can reduce load time by 40-60%.

2. Too many plugins or scripts

WordPress sites with 20+ plugins — common in template-based sites — load a separate script for each one. Every script adds load time. Many plugins add scripts even on pages where they're not needed.

Fix: Audit and remove unused plugins. Use a caching plugin. Defer non-critical scripts. Impact: 20-40% improvement.

3. Cheap or shared hosting

A $5/month shared hosting plan puts your website on a server with hundreds of other sites. When those sites get traffic, your site slows down. Server response time alone can add 1-3 seconds to load time.

Fix: Move to a quality host (Vercel, Cloudflare Pages for static sites; WP Engine or Kinsta for WordPress). Impact: 1-3 second reduction in TTFB.

4. No content delivery network (CDN)

If your server is in New York and a visitor is in London, every asset loads across the Atlantic. A CDN stores copies of your site in data centres worldwide so every visitor loads from nearby.

Fix: Enable Cloudflare free tier or use a host with built-in CDN. Impact: 30-50% improvement for international visitors.

5. Render-blocking JavaScript

Scripts that load in the <head> of your HTML block the browser from rendering anything until they've fully loaded. Many template sites include multiple render-blocking scripts by default.

Fix: Move scripts to end of body or add async/defer attributes. Requires developer. Impact: 0.5-2 second improvement.

6. No browser caching

Without caching headers, visitors download your entire website from scratch on every visit. With caching, repeat visitors load your site from their browser's local storage — almost instant.

Fix: Add cache-control headers or use a caching plugin. Impact: 80% reduction in load time for repeat visitors.

7. Unoptimised fonts

Loading 6 font weights from Google Fonts adds multiple requests and can block rendering. Many sites load fonts they don't even use.

Fix: Limit to 2 font weights, preload fonts, use font-display: swap. Impact: 0.2-0.5 second improvement.

The priority order: what to fix first

If you're working with a developer to improve your speed scores, address issues in this order for the fastest ROI:

  1. Image optimisation — biggest impact, easiest to implement
  2. Hosting upgrade — affects everything simultaneously
  3. Plugin audit — remove everything unnecessary
  4. CDN setup — significant impact for global traffic
  5. Caching — important for repeat visitors and SEO
  6. Script optimisation — requires developer, but high impact
  7. Font optimisation — smallest impact, do last

"The businesses that reach out to us after running a speed audit are usually surprised by two things: how bad their scores are, and how fixable the problems are. Most of the biggest wins come from changes that take hours, not months."

The rebuild option

For some websites — particularly those built on page builders, old WordPress themes or website builder platforms — the cumulative technical debt is so significant that fixing individual issues is less efficient than rebuilding on a modern, performance-first stack.

A website built on Next.js with proper image optimisation, edge hosting and no unnecessary dependencies will consistently score 90-97 on performance without specific optimisation work. The performance is built into the architecture. This is why modern web agencies can deliver a website that outperforms a 5-year-old custom-built site — it's not about the quality of the original developer, it's about the tools.

Common questions

Is page speed really a ranking factor?

Yes — Google has used Core Web Vitals, which include speed metrics, as a direct ranking factor since 2021, meaning slow sites are penalised in search results independent of their conversion impact.

How quickly can speed issues typically be fixed?

Image compression and hosting upgrades can often be resolved within a day, while more involved fixes like script optimisation may require a developer and take longer.

Is a full rebuild ever necessary?

For sites built on outdated platforms or heavily loaded with legacy plugins, a rebuild on a modern, performance-first stack is often more efficient than attempting to patch accumulated technical debt.

What does your website score right now?

Find out in 30 seconds. The free Brivex AI scanner checks your speed alongside SEO, security, mobile and AI readiness — and tells you exactly what to fix first.

Run My Free Audit →