Skip to content

Journal

Why your site speed is quietly costing you customers

Why a slow website makes it harder to win customers, what Core Web Vitals actually measure, and the practical fixes I start with.

By / / 5 min Updated

You’ve done it yourself. Open a site, wait for it to load, give up and try somewhere else. Your customers can do the same thing. They don’t email you to complain. They just leave.

Speed is the most invisible problem in web design, because the people it costs you never arrive.

What “slow” actually comes from

It’s almost never one big thing. It’s a pile of small ones:

  • Bloated themes and page builders that load code for features you’ll never use.
  • Unoptimized images, a 4MB photo straight off a phone where a 120KB version would look identical.
  • A dozen third-party scripts for chat widgets, analytics, and pop-ups, each one phoning home.
  • No caching, so every visitor rebuilds the whole page from scratch.

Individually, none of these feels like a problem. Together they turn a snappy site into a sluggish one.

Why Google cares (and why that means you should)

Google’s Core Web Vitals guidance covers how quickly your main content appears, how the page responds to a tap, and whether things jump around while it loads. Those are useful things to fix for the person using your site, too.

A fast site still needs to answer the customer’s question. A good score isn’t a promise of higher rankings or more sales, and there’s no universal percentage of revenue you lose for every extra second. Check your actual visitors and enquiries alongside the speed tests.

How I build for speed from the start

Performance isn’t something I bolt on at the end. It’s the foundation:

  • Static-first architecture where it fits, so pages can be pre-built instead of assembled on every request.
  • Modern image formats sized exactly for where they appear, lazy-loaded below the fold.
  • Almost no JavaScript shipped to the browser unless a feature genuinely needs it.
  • A page-weight budget, so a nice design doesn’t quietly turn into a huge download.

Then I test it. A simulated mobile test is a useful starting point. Real visitor data, when there’s enough of it, shows what happens across different phones and connections. They’re different views of the same problem.

If your site feels slow, start with the free speed check. If you’re not sure what the results mean, send me the link. I’ll help you figure out what actually needs attention.

Written by Ian

Founder of Northern Web Dev. Twenty years designing, building and ranking sites, by hand. More about me.

Keep reading

Want this handled for you?

Send me your site and tell me what you want to improve. I'll take a look and we can talk about where to start.

Book a free call