Slow website? The 7 most common causes (and how to fix them).

1. Cheap hosting

The number one cause, almost always. Overcrowded servers costing tens of euros a year can’t be fast: the site is slow before it even loads the first image. The solution is hosting sized for the project: often the intervention with the best cost/benefit ratio. The problem is that these plans share the same server among hundreds of sites: when one of them has a traffic spike, all the others slow down too, yours included, and there’s nothing you can do about it. Moving to hosting sized for the project costs a few tens of euros more a year, but it’s often what turns a slow, frustrating site into one that responds instantly.

2. Images that are too heavy

Photos uploaded straight from a smartphone at 5 MB each: three are enough to sink a page. They should be resized, compressed and served in modern formats (WebP/AVIF) with lazy loading. The paradox is that the eye notices no difference: a photo optimised to a few hundred kilobytes looks identical to the 5 MB original, but loads in a fraction of the time. Automating this process, so that every uploaded image is resized and compressed on its own, stops the problem from returning every time someone updates the site.

3. Too many plugins (and the wrong ones)

On WordPress every plugin adds code, queries and potential conflicts. Above 20–25 plugins suspicion is in order; and a single badly written plugin can add two seconds of loading on its own. It’s not just a matter of number: the quality of what you install matters far more. Better a few well-chosen plugins kept up to date than a collection accumulated over the years, where perhaps two do the same thing and a third, abandoned by its developer, slows everything down and opens a security hole too. A periodic review of what’s really needed is time well spent.

4. No cache

Without a cache, the server rebuilds every page from scratch on every visit. A correct page- and browser-cache configuration is the single most effective technical step, and is often missing entirely. In practice, the cache means the server prepares the page once and then serves it ready to all following visitors, instead of rebuilding it each time: the time saving is enormous, especially at busy moments. It’s also one of the least invasive steps — it doesn’t change the look of the site — and for that reason one of the first worth sorting out.

5. Bloated themes and heavy page builders

“Do-everything” themes load megabytes of code for features you’ll never use. A bespoke theme loads only what’s needed: it’s one of the reasons our sites fly. “Do-everything” themes try to suit any kind of site, and to do so they load a huge amount of code and options you’ll never use in your specific case, but which the browser still has to download and process. Building only what’s needed, with no frills, is more work upfront but pays off every day with light, fast pages.

6. Third-party scripts

Chat, maps, video, advertising pixels: every external service adds requests that block loading. They should be loaded deferred — or removed, if they don’t add value. The point is to ask an honest question for each one: does this external service bring me enough value to justify the milliseconds it adds? Often you find yourself dragging along for years a chat no one uses, an old advertising pixel or a map nobody consults. Removing the superfluous and loading the rest intelligently makes the site faster without taking away anything useful.

7. No maintenance

Databases never optimised, obsolete PHP versions, plugins not updated: sites slow down as they age, like everything else. Regular maintenance keeps day-one performance. A site isn’t an object that, once built, stays identical forever: software ages, content piles up and the database grows heavier, and without care performance slips away little by little, almost unnoticed. Regular maintenance — updates, database cleanup, version checks — is what keeps the site fast over time, instead of having to “revive” it every couple of years.