Someone waiting for a page to load is not thinking “it will be here soon”. They are thinking about going back and clicking the next search result. And you never find out they were there.
Most slow sites are slow for the same handful of reasons. Let’s go through them.
First: check it yourself
Do not take anyone’s word for it, look at the number. Google’s PageSpeed Insights is free — put in your address and you get a report. Look at the mobile result separately; it is almost always worse, and it is what most people actually use.
Do it twice: once on the homepage, once on an inner page. Sometimes the homepage is nicely optimised and the rest of the site is not.
Cause 1: images
By far the most common, and also the easiest to fix.
The typical case: someone uploaded a phone photo, 4000 pixels wide and 6 megabytes, and the page displays it 400 pixels wide. The browser still downloads all 6 megabytes.
What to do: resize images to a sensible size before uploading and save them in a modern format (WebP or AVIF). That alone can cut page weight several times over. If you have many images, add lazy loading so images further down are not fetched until someone scrolls to them.
Cause 2: too many plugins
This mainly affects WordPress sites. Every plugin brings its own JavaScript and CSS file, and these are usually loaded on every page, including pages where that plugin is not used at all.
What to do: go through the plugin list and ask of each one, “do I use this?”. Remove the ones you do not — not deactivate, remove. Very often the site gains more from this than from any other trick.
Cause 3: cheap hosting
If your site sits on a shared server with two hundred others, you share their load too. The tell: the site is sometimes fast and sometimes slow for no visible reason.
What to do: check the server response time (PageSpeed reports it). If it is over half a second, the problem is not your site but what is underneath it. Moving host is tedious, but it is a one-off job.
Cause 4: too many fonts
Every typeface and every weight is a separate file. Three typefaces in four weights each is twelve files that must download before text displays properly.
What to do: stick to two typefaces, and only the weights you actually use.
Cause 5: third-party scripts
A chat widget, a cookie banner, two analytics tools, social buttons, a map embed. Each is a request to someone else’s server, and each can hold your page up when that server is having a slow day.
What to do: review what is genuinely needed. Chat widgets especially are heavy — if you get no enquiries through it, it is costing you speed for nothing.
What counts as “fast enough”?
I am not going to promise a single number here, because it depends on what your site does. But there is a simple practical test: if you open your site on a phone on mobile data and it feels slow, it is slow. That feeling is more reliable than any score.
And worth saying: a perfect score is not a goal in itself. The last few points cost disproportionate effort and no customer ever notices them. The goal is for the page to feel instant — not for a chart to be green.
When a rebuild is worth it
Most things on this list are fixable without replacing the site, and that is always where to start. A rebuild makes sense when:
- the site is built on a template bent so far that nobody dares touch it;
- every small change takes someone hours;
- you fix one thing and another breaks;
- or you simply cannot change anything yourself any more.
If you want us to look at your site and say which of the two makes sense in your case, write to us — we will look and tell you honestly if it is fixable.