The short answer: your website is slow because it is heavy — it makes the visitor’s phone download and run far more than the page needs. Caching, image compression and better hosting all treat that weight after the fact. They help, and you should have them. But when a site is built on a template or page builder, the weight is structural: it was assembled from parts designed for every possible website, and it carries all of them everywhere. You cannot cache your way out of a bad build.
That sentence is missing from nearly every “fix your slow site” guide, and the reason is worth knowing: most of those guides are written by the people who sell the plugins, the builders, or the hosting. Their answer to a heavy site is another layer. Here is the version with no layer to sell.
Where the weight actually comes from
Open a typical template site and you will find a page-builder runtime, a theme’s entire stylesheet (most of it unused on any given page), a slider library for a slider that was deleted, three font families, a dozen plugins each injecting their own scripts, and images sized for a cinema screen. Each piece seemed harmless when it was added. Together they are megabytes that every visitor pays for — on a mid-range phone, on mobile data, before your first word appears.
A caching plugin makes a heavy page arrive slightly faster. It does not make it light.
What the standard fixes can and cannot do
Do the basics: compress and lazy-load images, remove plugins you do not use, enable caching, use a CDN. On a moderately bloated site these steps produce a real, visible improvement — and if your site was well-built to begin with, they are all it ever needs. But there is a ceiling, and it is the template itself. When the theme’s own machinery costs more than your entire page should weigh, optimisation becomes rearranging cargo on an overloaded truck. The measurements tell you which case you are in: if careful optimisation still leaves the page slow on a real phone, the problem is the construction.
The fix nobody selling plugins will suggest
Rebuild the pages properly: hand-written code that carries only what your site actually uses. This is not exotic engineering — it is the absence of accumulated machinery. Pages built this way are light because nothing unnecessary was ever added, fast on cheap phones because that is what they were designed for, and they stay fast, because there is no plugin stack quietly regrowing the weight. Speed stops being a monthly battle and becomes a property of the site.
We are a senior-led studio that builds sites this way — hand-coded, measured on real devices, to a published standard — working remotely with businesses worldwide. If your site is slow and you want a straight answer about whether it can be optimised or needs rebuilding, send it over; we will tell you honestly, either way.
We take existing sites to a measured 95+ PageSpeed and hold them there — or tell you honestly when a rebuild is the cheaper path.