Why Is My Website So Slow? Causes and How to Fix Them

Slow websites lose business in a way that is almost invisible. Nobody emails to say they left because the page took six seconds. They just leave, and the analytics records a visit that went nowhere.

This article covers what “slow” actually means in measurable terms, the handful of causes responsible for most slow business websites, and what can realistically be fixed without a rebuild.

What counts as slow

Google publishes concrete thresholds through Core Web Vitals, measured on real visits rather than lab tests. Largest contentful paint, which is how long the main content takes to appear, should be under 2.5 seconds. Interaction to next paint, which is how quickly the page responds when someone taps or clicks, should be under 200 milliseconds. Cumulative layout shift, which measures how much the page jumps around while loading, should be under 0.1.

Those are the numbers worth testing against. It is also worth testing on a mid-range phone on mobile data rather than on a desktop with fast broadband, because that is closer to how most visitors experience the site.

Images are the usual culprit

On most slow business websites, images account for the majority of the weight. The common pattern is photographs uploaded straight from a camera or phone at full resolution, displayed in a space a fraction of that size.

Three fixes cover almost all of it. Serve images in a modern format such as WebP, which typically cuts file size substantially at the same visual quality. Resize them to the dimensions they are actually displayed at, with a higher-resolution version for retina screens rather than one enormous file for everyone. And load images below the fold lazily so they do not block the first view.

Hero images deserve particular attention, because on most pages the hero image is the largest contentful paint element. If that single file is three megabytes, nothing else you do will bring the number under 2.5 seconds.

Too much code, loaded too early

The second major cause is the volume of CSS and JavaScript a page loads before it can display anything.

This accumulates rather than arriving all at once. A theme ships with a full framework. A page builder adds its own stylesheets and scripts to every page, whether or not the page uses them. A slider plugin adds a library. Analytics, a chat widget, a cookie banner, a heat-mapping tool and a conversion pixel each add a third-party script that the browser has to fetch from somebody else’s server.

The audit worth doing is simple: list every script running on the site and ask what each is for and whether anyone looks at its output. A surprising number of slow sites are carrying tracking tools nobody has opened in a year, and chat widgets nobody answers.

Fonts

Custom fonts are a small but common contributor, particularly when a site loads several families and multiple weights. Each one is a separate file, and if text is hidden while they load, the page appears blank for longer than it needs to. Loading two weights of one family, with a sensible fallback while they arrive, is usually enough and is noticeably faster.

Hosting that cannot keep up

Everything above concerns what the browser has to do. Server response time concerns what happens before that, and it sets the floor for every other metric.

Cheap shared hosting puts hundreds of sites on the same machine, so your response time depends partly on what everyone else’s site is doing. If the server takes a second to begin responding, a 2.5 second target is already difficult. Geography matters too: a site hosted a continent away from its customers starts every request at a disadvantage.

Caching helps considerably, by serving a prepared version of the page rather than building it for every visitor, and a content delivery network helps with distance. Neither rescues genuinely inadequate hosting.

Database and plugin load

On older WordPress sites in particular, the database accumulates: post revisions, expired transients, orphaned data from plugins removed years ago. Combined with a large number of active plugins, each running queries on every page load, the time to build a page creeps up.

The useful work is removal rather than optimisation. Deactivating and deleting plugins that are not needed does more than any caching configuration, and it reduces the security surface at the same time.

What you can fix, and in what order

Work in this sequence, because it reflects both impact and effort.

First, compress and resize images and serve them in a modern format. Second, remove scripts, plugins and third-party tools nobody uses. Third, add proper caching and a content delivery network. Fourth, reduce fonts. Fifth, review hosting if server response time is still high after the rest.

For most business sites, the first two steps alone produce the majority of the improvement, and neither requires a developer.

When speed is a build problem rather than a tuning problem

There is a point where optimisation stops working. If a site is built on a heavy page builder that outputs deeply nested markup and loads its full stylesheet everywhere, you can cache and compress and still not reach the thresholds. The weight is structural.

That is the honest moment to consider a rebuild rather than another plugin. The decision framework is in our guide to planning a website redesign, and the costs involved are covered in what a small business website should cost.

Why it matters beyond the score

Speed affects two things that show up in revenue. People abandon slow pages, particularly on mobile, and particularly at the point where they were about to act. And page experience feeds into how your pages perform in search, which compounds the traffic loss.

The businesses that feel this most sharply are the ones paying for traffic. Every pound spent sending people to a slow landing page is partly spent on visitors who leave before it renders, which is one reason underperforming ad campaigns so often turn out to have a site problem rather than a targeting problem.

Finding out what is actually slowing your site

Page speed tools produce long lists of recommendations, most of which are minor, and it is easy to spend weeks on items worth fractions of a second while missing the three-megabyte hero image.

Send us your URL and we will tell you what is actually costing you the time, in order of impact, and whether it can be fixed on the current build or needs a different foundation. Our technical SEO work covers performance and crawling together, and where the answer is the build itself, website design and development is where that gets addressed.