What makes a fast website? A guide for business owners

Why website speed matters more than you think

Website speed isn't just a technical metric for developers to obsess over. It directly affects two things every business owner cares about: how many people find you and how many of them become customers.

Google has used page speed as a ranking factor since 2018. Slow sites rank lower. It's that simple. If you're trying to show up for “plumber Halifax” or “accountant Leeds” and your site takes 6 seconds to load, you're fighting with one hand tied behind your back.

Then there's the human side. Research from Google shows that 53% of mobile visitors leave a site that takes longer than 3 seconds to load. For every additional second of load time, conversion rates drop by roughly 4.4%. A slow website doesn't just annoy people. It actively drives them to your competitors.

What Google PageSpeed actually measures

Google PageSpeed Insights is the standard tool for measuring website performance. You can test any site for free at pagespeed.web.dev. It gives you a score from 0 to 100 and breaks down exactly what's fast and what's slow.

But the score is made up of several specific metrics. Here's what they mean in plain English:

Largest Contentful Paint (LCP)

This measures how long it takes for the main content of your page to appear. Think of it as: when does the page look “loaded” to a visitor? Google considers anything under 2.5 seconds as good. Most business websites on WordPress hit 4–8 seconds on mobile.

First Input Delay (FID) / Interaction to Next Paint (INP)

This measures how quickly the page responds when someone interacts with it: tapping a button, clicking a link, typing into a form. If there's a delay between tapping and something happening, that's a poor FID/INP score. Under 100 milliseconds is the target.

Cumulative Layout Shift (CLS)

Have you ever been reading a page on your phone, then an image loads and everything jumps around? That's layout shift, and it's infuriating. CLS measures how stable your page layout is as it loads. A good score is under 0.1. Sites with unoptimised images, late-loading ads, or fonts that swap in after the page renders score badly here.

First Contentful Paint (FCP)

How quickly does anythingappear on screen? Even if the full page isn't loaded, seeing something quickly reassures the visitor that the site is working. Under 1.8 seconds is the target.

Total Blocking Time (TBT)

This measures how long JavaScript blocks the main thread, preventing the page from responding to user input. Heavy JavaScript frameworks and bloated plugins are the usual culprits. Under 200 milliseconds is good.

The most common speed killers

If your website is slow, it's almost certainly because of one or more of these issues:

1. Unoptimised images

This is the single biggest performance killer on most business websites. A single unoptimised hero image can be 3–5MB. That's the equivalent of loading a small application just for one picture. Images should be compressed, served in modern formats like WebP, and sized correctly for the screen they're displayed on.

A 2000x1500 pixel photo uploaded straight from your phone has no business being on a web page. It should be resized to the exact dimensions needed and compressed to under 100KB in most cases.

2. Page builder bloat

WordPress page builders like Elementor, Divi, and WPBakery generate enormous amounts of CSS and JavaScript. They load their entire framework on every page, even if you're only using a fraction of its features. A simple 5-page brochure site ends up loading the same amount of code as a complex web application.

This is the main reason most WordPress business sites score between 25 and 55 on mobile. The page builder is the bottleneck, and no caching plugin can fully solve it.

3. Too many plugins and scripts

Every plugin on a WordPress site potentially adds its own CSS file, JavaScript file, and database queries. Analytics trackers, chat widgets, social media embeds, cookie consent popups. Each one adds weight. Twenty plugins each adding 50KB of JavaScript means an extra megabyte of code before the page even starts rendering.

4. Cheap or shared hosting

Budget hosting (£3–£5/month shared hosting) means your website shares a server with hundreds of other sites. When the server is busy, your site slows down. Time to First Byte (TTFB), how quickly the server responds to a request, can be 2–3 seconds on cheap hosting before the browser even starts receiving content.

5. No caching strategy

When a browser loads your site, it shouldn't have to download everything from scratch every time. Proper caching tells the browser to reuse files it's already downloaded. Without it, returning visitors experience the same slow load times as first-time visitors.

6. Render-blocking resources

Some CSS and JavaScript files block the page from rendering until they're fully downloaded and processed. If your site loads 15 CSS files and 12 JavaScript files before showing anything on screen, visitors stare at a blank page while their browser works through the queue.

How to check your score

It takes 30 seconds. Go to pagespeed.web.dev, type in your website address, and hit Analyze. Pay attention to the mobilescore, not desktop. Mobile is what Google uses for ranking, and it's always lower.

Here's what your score means:

• 90–100 (green): Excellent. Your site is fast and Google likes it. This is where you want to be.
• 50–89 (orange): Needs improvement. You're not terrible, but you're losing some visitors and ranking potential.
• 0–49 (red): Poor. Your site is actively hurting your business. Visitors are leaving, and Google is ranking you lower because of it.

For context, the average score for small business websites is around 35 on mobile. Most sites we're asked to replace score between 20 and 50.

What a genuinely fast website looks like

A fast website isn't just about the score. It's about the experience. When you visit a fast site, pages appear almost instantly. There's no flash of unstyled content, no jumping layout, no loading spinners. You click a link and the page is there.

Every site we build at Webvise scores 95+ on Google PageSpeed, on mobile. That's not a theoretical benchmark. You can test any site on our portfolio page right now and verify it yourself. We achieve this through:

• Static site generation: Pages are pre-built as HTML files, not generated on-the-fly from a database.
• Minimal JavaScript: We only ship the code that's actually needed. No page builder framework, no plugin overhead.
• Optimised images: Every image is compressed, correctly sized, and served in modern formats.
• Edge hosting: Sites are deployed to a global CDN, so they load fast regardless of where the visitor is.
• Zero render-blocking resources: Critical CSS is inlined, non-critical resources are deferred.

Can you fix a slow site, or do you need a rebuild?

It depends on the architecture. If your site is built on a lightweight WordPress theme without a page builder, you might be able to optimise it to a reasonable score with image compression, caching, and some code cleanup. Scores of 70–80 are achievable with effort.

If your site uses Elementor, Divi, or any heavy page builder, you're fighting the technology itself. You can install every optimisation plugin available and still struggle to break 60 on mobile. At that point, a rebuild on a modern framework is the smarter investment.

The honest answer? If your mobile PageSpeed score is under 40, optimisation alone probably won't get you where you need to be. A rebuild isn't just about speed. It's about starting with an architecture that's designed for performance from the ground up.

Speed is the foundation

Great design, compelling content, and solid SEO all matter. But they're built on a foundation of performance. A beautifully designed site that takes 8 seconds to load is a beautifully designed site that nobody sees.

If you're curious about the technology behind our approach, read our comparison of WordPress and Next.js. Or if you already know your site is slow and want to fix it, get in touch. We'll test your current site, tell you honestly what's wrong, and whether a rebuild makes sense for your business.