Why your website needs to load in under two seconds.

Someone searches for what you do, finds your site and waits. Three seconds pass. Four. They're gone, and you never knew they were there.

Speed isn't a technical detail. It's the first impression and the patience test, all at once. For local businesses, where a quick search on a phone is often the first contact, a slow site is a closed door. Here's what we think "fast enough" really means, what usually slows sites down, and what to ask for.

What "fast enough" means

Our rule of thumb is two seconds. If the main content of your page takes longer than that to show up on a phone, you're asking people to wait in a queue they never agreed to join.

Google measures this with three numbers it calls Core Web Vitals. They describe what people actually feel when they use your site, and they feed into search rankings:

• Largest Contentful Paint (LCP): how long until the main content appears. Google calls under 2.5 seconds good. We aim for under 2 seconds on mobile.
• Interaction to Next Paint (INP): how quickly the page responds when you tap or click. Under 200 milliseconds is good.
• Cumulative Layout Shift (CLS): whether the page jumps about as it loads. A score under 0.1 means it stays put.

These aren't abstract benchmarks. They're the difference between a site that feels smooth and one that feels sluggish or annoying. For a café taking online orders or a surveyor taking bookings, every extra second is a chance for the customer to give up.

One thing worth knowing: your site probably feels quick on your office wifi and a new laptop. Your customers might be on an older phone, on a train or in a village with one bar of signal. Always test on mobile, because that's where the problems show up first.

A visitor who waits three seconds is already weighing up whether to leave.

What usually slows a site down

Most slow sites share the same handful of problems. The good news is that most of them can be fixed.

Oversized images

A 4MB hero image that looks crisp on your laptop is a long wait on a phone in a car park with patchy 4G. A single photo saved straight from a camera can weigh more than a whole page should.

Too many scripts and requests

Every font, chat box, analytics snippet, tracker and social feed is another trip to a server. Each one adds a bit of delay, and they add up quickly. Most small business sites need far fewer of these than they have.

Files loading in the wrong order

If CSS and JavaScript files load in the wrong order, the browser sits waiting before it can draw anything. A good developer sets things up so the visible content appears first.

Cheap or distant hosting

Shared hosting might cost £3 a month, but if the server takes ages just to respond, no amount of tweaking will save you. A server on another continent adds delay too, and some cheap plans slow your site down when traffic picks up.

No caching

If your site builds the same page from scratch for every visitor, it's doing far more work than it needs to.

What actually works

You often don't need a full rebuild to fix a slow site. Start with the basics.

Compress and resize every image

Use modern formats like WebP or AVIF, which are much smaller than old JPEGs and PNGs at the same quality. Serve different sizes to different screens. A phone doesn't need a 2000-pixel-wide banner. Load images further down the page only when someone scrolls to them. Tools like Squoosh or ImageOptim make this easy, and most modern frameworks do it for you if they're set 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 the chat widget bringing in work, or just sitting there slowing things down? If it's not earning its place, take it out.

Use a CDN

A content delivery network keeps copies of your site in data centres in lots of places. Someone loading your site in Norwich gets it from a server in London, not California. If your customers are spread across the UK or further, it's well worth having.

Pick a host that cares about speed

Managed hosting costs more than bargain shared plans, but the difference in speed is usually obvious. Look for server-level caching, fast storage and UK-based servers. If your site runs on WordPress, a decent caching plugin such as WP Rocket or LiteSpeed Cache can make a real difference with little setup.

When to start again

Sometimes tweaks aren't enough. If your site sits on a heavy theme with dozens of plugins, or on a platform that was never built with speed in mind, you're fighting the tools.

We build with Next.js and React, the same setup we've used for clients like Surplush and NR Surveyors, because speed is built in. Pages can be prepared ahead of time, images are resized automatically, code is split so visitors only download what they need, and caching is handled for you. Speed is a requirement from day one, not something we try to bolt on at the end.

What to ask for

If you're commissioning a new site or improving the one you have, put these in the brief:

• A target LCP of under 2 seconds on mobile, measured before launch.
• Responsive images in modern formats, sized for each device.
• A CDN if your audience is spread across the UK or beyond.
• As few third-party scripts as possible.
• Regular speed checks after launch. Speed isn't a one-off fix. New images, plugins and scripts creep in over time.

It's also fair to ask any developer what LCP and INP scores their sites usually get. If they don't know what those are, we'd keep looking.

You're often up against national chains with whole teams working on their sites. You don't need a team. You just need to care about speed as much as you care about how the site looks. Your website is often the first impression a customer gets, so make it a quick one.