"Make it faster" is one of the most common requests we get on an existing website, and it's usually the right instinct even when the owner can't say exactly why. Speed isn't a technical vanity metric — it's one of the few things that affects both whether Google shows your site and whether the person who finds it actually sticks around.
The bounce happens before they see anything
A visitor deciding whether to wait for a page is making that decision in the first couple of seconds, often on a mobile connection that isn't as fast as the office wifi a site got built and tested on. Every extra second of load time is a real, measurable chunk of visitors leaving before the homepage has even finished rendering — not because the product or the design was wrong, but because they never saw it.
It's also a ranking factor, quietly
Google's Core Web Vitals — measures of how quickly a page becomes visible, interactive and visually stable — are one of the inputs into search ranking. Not the biggest one, but not nothing either, and it's one of the few ranking factors a business can directly control through the build itself rather than through content or backlinks.
What actually slows a site down
In practice, it's rarely one dramatic issue — it's usually three or four small ones stacked together:
- Unoptimised images. A photo straight off a phone camera can be ten times larger than it needs to be for how it's actually displayed on the page.
- Too many third-party scripts. Chat widgets, tracking pixels and font embeds each add their own request and their own delay, and they add up fast.
- No caching or compression at the server level, so the same assets get re-downloaded in full on every visit.
- Render-blocking code — scripts and stylesheets that force the browser to wait before showing anything at all.
None of these are exotic problems. They're also not one-time fixes — a site that launches fast can quietly slow back down over a year of added plugins, tracking scripts and uncompressed images, which is why we treat performance as something to check periodically, not just at launch.
What we actually optimise for
Sub-two-second loads on mobile networks is the bar we build every website against, not as a marketing number but because it's roughly where the visitor drop-off curve starts to flatten out. Getting there is mostly disciplined basics done consistently — compressed images, minimal third-party bloat, clean markup — rather than one clever trick. The unglamorous stuff is, almost always, the whole answer.
If your site feels sluggish and you're not sure why, that's usually a sign it's worth an actual audit rather than a guess — the fix is often smaller and cheaper than people expect once the real bottleneck is identified.