A potential customer searches for your service, finds your site, and waits. Three seconds pass. Four. They're gone. You've just lost a lead, and you never even knew they were there.
Speed isn't a nice-to-have anymore. It's the difference between a website that converts and one that haemorrhages traffic to faster competitors. For Norwich small businesses, where local search is often the first point of contact, a slow site is a closed door.
What 'fast enough' actually means in 2026
Two seconds. That's the threshold. If your homepage takes longer than that to become interactive, you're asking visitors to wait in a queue they never agreed to join.
Google's Core Web Vitals, the metrics that directly influence search rankings, measure three things: how quickly the largest piece of content appears (LCP), how soon a user can click or tap something (INP), and whether the page jumps around as it loads (CLS). All three matter, but the first two are deal-breakers.
A two-second delay can cut conversions by up to half, and most users won't wait longer than three.
This isn't abstract. A two-second delay can cut conversions by up to half, and most users won't wait longer than three. For a Norwich café taking online orders or a surveyor booking appointments, every extra second is revenue walking out the door.
The usual culprits slowing you down
Most performance problems come from a handful of fixable issues. Here's what we see most often:
- Oversized images: A 4MB hero image that looks crisp on your laptop is a five-second wait on a phone in a Norwich car park with patchy 4G.
- Too many scripts: Every third-party widget, chat box, analytics snippet and social feed adds another request. Ten of them can double your load time.
- Cheap hosting: Shared hosting might cost £3 a month, but if your server takes two seconds just to respond, no amount of optimisation will save you.
- No caching: If your site rebuilds the same page from scratch for every visitor, you're working ten times harder than you need to.
What actually works
You don't need a complete rebuild to fix a slow site. Start with the basics:
Compress and resize every image
Use modern formats like WebP or AVIF. Serve different sizes to different devices. A phone doesn't need a 2000-pixel-wide banner. Tools like ImageOptim or Squoosh make this trivial, and most modern frameworks handle it automatically if you set them up properly.
Audit your scripts
Open your browser's developer tools and look at the network tab. Every line is a request. Do you really need that Instagram feed on every page? Is that chat widget actually converting anyone, or just sitting there eating bandwidth?
Use a CDN
A content delivery network stores copies of your site in data centres around the world (or at least around the UK). When someone in Norwich loads your site, they're pulling it from a server in London, not California. The difference is measurable.
Pick a host that cares about speed
Managed hosting costs more than bargain-basement shared plans, but the performance difference is night and day. Look for hosts that offer server-level caching, SSD storage, and UK-based servers.
When to start from scratch
Sometimes optimisation isn't enough. If your site is built on a bloated theme with dozens of plugins, or if it's running on a platform that was never designed for speed, you're fighting physics.
Modern frameworks like Next.js, the stack we use for clients like Surplush and NR Surveyors, are built for performance from the ground up. They prerender pages, lazy-load images, split code so users only download what they need, and handle caching automatically. The result is sites that load in under a second, even on slow connections.
Why this matters more in Norfolk right now
With plans for a 150MW data centre near Norwich making headlines and nearly 5,000 people signing petitions, there's a lot of talk about infrastructure and digital capacity in the region. But while data centres handle the back end, your website's performance is entirely in your control.
Local businesses compete with national chains that have entire teams optimising their sites. You don't need a team. You just need to care about speed as much as you care about design.
Key takeaways
- Aim for under two seconds to interactive, measured with real tools like PageSpeed Insights
- Cut image sizes, audit third-party scripts, and use a CDN
- If your platform can't be fixed, consider rebuilding on a modern stack designed for speed
Your website is often the first impression a customer gets. Make sure it's a fast one.
