Why Your Website Is Slow (And How It's Costing You Customers)

Speed Matters More Than You Think

Let's get straight to the point: if your website takes more than three seconds to load, you're losing customers. Not might be losing them. You are losing them.

Google's research found that 53% of mobile users will leave a page that takes longer than three seconds to load. Amazon discovered that every 100 milliseconds of extra latency cost them 1% in sales. When you're a business turning over hundreds of thousands or millions a year, that's not pocket change.

Page speed has been a Google ranking factor since 2018, and it's only getting more important. In 2021, Google introduced Core Web Vitals as official ranking signals. Your website speed directly affects where you appear in search results, which means it affects how many people find you in the first place.

A slow website isn't just annoying. It's actively driving potential customers to your competitors who load faster. While your site is still showing a white screen, they've already clicked back to Google and chosen someone else.

The Most Common Speed Killers

Here's what's actually making your website slow. I see these problems on almost every site that comes to us for help.

Unoptimised Images

This is the big one. Business owners upload photos straight from their phone or camera. A modern smartphone takes photos that are 5MB or larger. Your website only needs that image to be 200KB at most, often less. When someone visits your homepage and it tries to download ten 5MB images, that's 50MB of data. On a slow mobile connection, that could take 30 seconds or more.

The solution isn't using lower quality images. It's using the right format and the right size. A properly optimised image looks identical to visitors but loads twenty times faster.

Too Many WordPress Plugins

WordPress makes it easy to add functionality with plugins. Too easy. I regularly see sites with 30, 40, even 50 plugins installed. Each one adds HTTP requests and JavaScript. Some plugins add ten or more separate files that need to load on every page, whether you're using that plugin's feature on that page or not.

A site with 30 plugins isn't unusual, but it is catastrophic for website performance. Every plugin is another point of failure, another thing that needs to load, another chunk of code slowing everything down.

Cheap Shared Hosting

Your website lives on a server. With cheap shared hosting, that server is home to hundreds of other websites, all competing for the same resources. When someone else's site gets a traffic spike, your site slows down. When their badly written code uses too much memory, your site suffers.

Hosting is the foundation everything else sits on. You can optimise images and reduce plugins all you want, but if your server takes five seconds just to start generating the page, you're fighting a losing battle.

Render-Blocking CSS and JavaScript

When someone visits your site, the browser downloads your HTML file first. Then it finds references to CSS and JavaScript files and downloads those. The problem is, many themes and plugins force the browser to download and process all of these files before it can show anything at all.

This is called render-blocking. The browser is ready to render your page, but it's blocked by files that might not even be needed for what's visible on screen. Modern websites should load critical CSS inline and defer everything else, but most WordPress themes don't do this.

No Caching

Every time someone visits your site, the server has to build the page from scratch: query the database, run PHP code, assemble the HTML, send it to the browser. That takes time and server resources.

Caching means saving a ready-made copy of the page and serving that instead. It's like the difference between cooking a meal from scratch versus reheating leftovers. Both get you fed, but one is much faster. Without caching, your server is cooking every meal from scratch for every single visitor.

How to Check Your Website Speed

Before you can fix your website speed, you need to know what you're dealing with. Here's how to check.

Google PageSpeed Insights

Go to pagespeed.web.dev and enter your website address. Google will test your site and give you a score out of 100 for both mobile and desktop. More importantly, it tells you exactly what's wrong and what to fix first.

You'll see your Core Web Vitals scores, which are the metrics Google actually uses for ranking. You'll see which resources are slowing you down. You'll see opportunities for improvement with estimated time savings.

It's completely free, and it's the same tool Google uses to evaluate your site for search rankings. If PageSpeed Insights says your site is slow, Google thinks your site is slow.

GTmetrix

GTmetrix (gtmetrix.com) gives you a more detailed breakdown. The waterfall chart shows you exactly what loads and when, so you can see which files are the bottleneck. You can test from different locations and different connection speeds to see how your site performs for users in different situations.

The free version is enough for most business owners. It's particularly useful for identifying specific images or scripts that are causing problems.

What the Scores Mean

Here's the simple version:

• 90-100: Great. Your site is fast. You're not losing customers to speed issues.
• 50-89: Needs work. Your site is slower than it should be. You're losing some visitors, and Google isn't ranking you as highly as they could.
• Below 50: Serious problem. Your site is actively hurting your business. Fix this before you spend money on anything else.

Don't obsess over getting a perfect 100. Anything above 90 is good enough. The difference between 95 and 100 won't affect your business. The difference between 40 and 90 absolutely will.

What Good Performance Looks Like

Google ranks websites based on three Core Web Vitals. These are the metrics that matter. Here's what they mean in plain English.

Largest Contentful Paint (LCP)

This measures how quickly the main content appears on screen. Not just anything, but the largest visible element: usually your hero image, your main headline, or your first block of text.

Your LCP should be under 2.5 seconds. Under 2 seconds is better. This is what visitors actually experience when they click through to your site. If your LCP is 5 seconds, they're staring at a mostly blank screen for 5 seconds. Most won't wait that long.

First Input Delay (FID)

This measures how quickly your site responds when someone clicks something. After the page loads, does it react immediately when they click a button or a link? Or is there a delay while JavaScript finishes loading?

Your FID should be under 100 milliseconds. Under 50ms is better. A delay of 200ms or 300ms might not sound like much, but users notice. It makes your site feel sluggish and unresponsive.

Cumulative Layout Shift (CLS)

This measures how much things jump around while the page loads. You know that annoying experience where you're about to click something and an image loads and pushes everything down and you click the wrong thing? That's layout shift.

Your CLS should be under 0.1. Under 0.05 is better. This is mostly about reserving space for images and ads before they load, so the page doesn't jump around when they appear.

Google uses all three of these metrics to rank your site in search results. They're also good indicators of actual user experience. A site that scores well on Core Web Vitals is a site that feels fast and responsive to use.

Quick Wins You Can Do Today

You don't need to be technical to make your website faster. Here are some things you can do right now that will make a real difference.

Compress Your Images

Go through your website and find your largest images. Use a free tool like TinyPNG or Squoosh to compress them. Better yet, convert them to WebP format, which is much more efficient than JPEG or PNG. Resize images to the actual display size. If an image displays at 800 pixels wide on your site, don't upload a 4000 pixel wide version.

This alone can reduce your page size by 60-80%. It's the single biggest quick win for most sites.

Enable Browser Caching

If you're on WordPress, install a caching plugin like WP Rocket or W3 Total Cache. The default settings are usually fine. This tells browsers to save copies of your CSS, JavaScript, and images so they don't have to download them every time.

First-time visitors still download everything, but return visitors load much faster because most files are already saved in their browser.

Remove Unused WordPress Plugins

Go to your WordPress plugins page and deactivate anything you're not actively using. If you're not sure what a plugin does, you probably don't need it. Each plugin you remove means fewer files to load and fewer things that can go wrong.

Be careful with plugins that came with your theme. Some themes break if you deactivate their companion plugins. But that contact form plugin you installed two years ago and never set up? Get rid of it.

Switch to Better Hosting

If you're on the cheapest shared hosting plan your developer could find, consider upgrading. Spending an extra £5-£10 per month on hosting can make a massive difference to website speed. Look for managed WordPress hosting or a VPS if you get decent traffic.

Good hosting providers include Kinsta, WP Engine, or SiteGround's higher-tier plans. Yes, they cost more. But if your site is slow because your server is overwhelmed, no amount of optimisation will fix it.

Lazy-Load Images Below the Fold

Images that aren't visible on screen when the page loads don't need to load immediately. Lazy-loading means they only load when the user scrolls down to them. This speeds up initial page load considerably.

Modern browsers support this natively with a simple attribute. Many WordPress themes and plugins include lazy-loading options. Enable it.

When You Need a Rebuild

Sometimes optimisation isn't enough. Sometimes the site is fundamentally broken and you need to start fresh. Here's when that's the case.

If your site scores below 50 on PageSpeed Insights and you've already tried the quick wins above, the problem is structural. The theme is bloated, the code is inefficient, and patching it will cost more than rebuilding.

If your site is built on a bloated WordPress theme with 30+ plugins just to make it work, that's not sustainable. Every plugin is a maintenance burden. Every plugin update risks breaking something. A clean, custom-built site doesn't need all that.

If load time is consistently over 5 seconds, even after optimisation, the site is costing you business every single day. Five seconds is an eternity online. Most users won't wait that long.

If your hosting company can't tell you what server your site is on or what resources you have, you're probably on the cheapest shared hosting they offer. That's fine for a personal blog. It's not fine for a business that depends on its website.

Sometimes it's genuinely cheaper to start fresh with clean, hand-written code than to patch a fundamentally broken site. A properly built site doesn't need 30 plugins. It doesn't need a page builder that adds 500KB of JavaScript just to display a button. It loads in under a second because it's built right from the start.