How to Improve Website Loading Speed (And Why It Costs You Customers)

A one-second delay in load time reduces conversions by an average of 7%. For a website generating 40 enquiries a month, that is several lost customers — every single month — just because a page loads one second slower than it needs to. The damage is double: worse rankings, because Google treats load time as a ranking factor, and fewer conversions, because impatient visitors leave before the page has even finished loading. This article covers how fast a website actually needs to be, the five causes behind most performance problems, and what you can fix yourself versus what needs a developer.

How fast should a website actually be?

Google no longer measures speed as a single number. It uses the Core Web Vitals — three specific metrics that feed directly into search rankings.

The free test for this is Google PageSpeed Insights (pagespeed.web.dev). Enter your URL and within seconds you get a score from 0 to 100 plus a concrete list of what's slowing the page down — reported separately for desktop and mobile, which matters because most websites score noticeably worse on mobile than on desktop.

The 5 most common causes of slow websites

1. Uncompressed images. By far the single biggest factor. A photo straight from a camera or stock library is often several megabytes — a website typically needs only 100 to 300 kilobytes for the same visible quality. On pages with several uncompressed images, this alone is the difference between a one-second and an eight-second load time.

2. Too many plugins and third-party scripts. Every WordPress plugin, embedded chat widget, and tracking script loads additional code that the browser has to execute, whether or not a visitor ever uses it. Ten plugins mean ten extra loading processes that can end up blocking each other.

3. Poor hosting. A cheap shared-hosting plan shares server resources with hundreds of other websites. During traffic spikes elsewhere on that same server, response time suffers for every site hosted there — including yours.

4. No caching or CDN. Without caching, every page is rebuilt from scratch on the server for every single visit, instead of serving a ready-made version from memory. Without a CDN (Content Delivery Network), every request is served from a single data center regardless of where the visitor is — someone in another country waits for data to travel from wherever that one server happens to sit.

5. Render-blocking JavaScript. If the browser has to fully load and execute a large JavaScript bundle before it is allowed to display anything, visitors experience a noticeable delay — even when the actual text and images were ready to show much sooner.

Laptop screen showing a PageSpeed dashboard with a large green circular gauge indicating a high speed score

What you can do yourself

Not every fix requires a developer. Some of these you can tackle without any technical background:

• Compress your images. Free tools like squoosh.app or TinyPNG cut file size by 60–90% with no visible quality difference in the browser.
• Disable unused plugins. Go through what's actually needed and remove the rest — every plugin you drop is a load-time improvement with zero downside.
• Check your hosting tier. If PageSpeed Insights consistently flags a high server response time (Time to First Byte) regardless of your images, that's often a sign your hosting plan is undersized.

What a developer needs to fix

Other causes sit deeper in the technical architecture and can only be resolved through development work:

• Code-splitting — loading only the JavaScript a given page actually needs, instead of shipping the entire site's script on every page.
• Lazy loading — images and content further down the page only load once a visitor actually scrolls to them.
• Critical CSS inline — embedding the styling rules for the visible area directly in the HTML, so the browser doesn't have to wait on a separate CSS file before rendering anything.
• WebP images instead of JPEG/PNG — the same image at the same visible quality with 25–50% less file size.
• Proper CDN setup — serving content from multiple geographically distributed servers so every visitor is served from a location near them.

Why the underlying technology matters

This is where a structural difference emerges that goes beyond individual fixes: a WordPress site running 20 active plugins is structurally slower than a cleanly built custom site on a modern framework like Next.js — regardless of how well the individual images are compressed. WordPress executes PHP code, database queries, and the full plugin stack on every page request before anything even reaches the visitor. A modern framework, by contrast, can pre-generate pages statically and serve them in milliseconds.

That doesn't mean WordPress is fundamentally unfit for purpose — for plenty of use cases it's more than adequate. But when performance is a real competitive factor, for example because you're fighting for every second of advantage in a crowded local market, the underlying technology is the single biggest lever available — bigger than any after-the-fact optimisation applied to a structurally slow platform.

The PageSpeed score is therefore also a useful proxy for the overall quality of a website build: if it sits persistently below 70 despite clean images and a lean plugin count, that's rarely a minor detail. It usually means the technical foundation itself has hit its limits.