Journal · 29 August 2026
Why website speed matters more than your design
A slow site loses customers before they see a pixel of your branding. What "slow" actually means, and what makes a site fast.
People leave before they judge the design
Google's own numbers have been consistent for years: as a page's load time goes from one second to three, the chance someone leaves roughly doubles. At five seconds it's worse again. Those people never saw your hero image, your carefully chosen font, your headline. They saw a white screen and a spinner, and went back to the search results.
So the first thing a website has to be is fast. Everything else is second.
What "slow" actually is
Not "it feels a bit laggy". Specific things:
- A big first download. Every image, script and font the browser fetches before it can show anything. A lean page is under 500KB all up. Plenty of small-business sites are 3–6MB, most of it uncompressed photos and third-party scripts.
- Render-blocking junk. Chat widgets, popup tools, analytics, A/B testing, font loaders — each is a request that can hold up the page. Five "harmless" add-ons is a slow site.
- Work the phone has to do. Heavy JavaScript frameworks make the browser assemble the page on the device. On a three-year-old Android that's a visible wait. On your new iPhone you'll never notice.
- Slow hosting. Cheap shared hosting can take half a second just to start replying, before anything downloads.
What makes a site fast
- Send less. Compress every image and size it for how it's actually shown. Self-host one or two fonts, no more. Cut the scripts you don't truly need.
- Send finished HTML. A page that arrives ready to display, instead of a bundle of code the browser has to run first, shows up faster on every device. That's the whole idea behind static sites.
- Serve from a CDN. Files delivered from a machine near the visitor, not one box in a data centre somewhere. Most good static hosts do this by default, free.
- Measure it honestly. Run PageSpeed Insights on your real site, look at the mobile score, not desktop. Then open the site on your own phone on mobile data, away from wifi.
The trade-off that isn't one
People assume fast means plain. It doesn't. You can have big type, full-bleed photography, motion, all of it — as long as the images are compressed properly and the page isn't dragging twenty scripts it never uses. Fast is a build decision, not a design limit.
Every site I build is meant to load in about a second on a mid-range phone on mobile data. That's the baseline, before we talk about how it looks. Here's how I work.