Skip to content
Aventine

Why your website is slow, and what actually fixes it

If your website takes ages to load on a phone, you have probably already tried to fix it. Someone suggested a bigger hosting plan. Someone else suggested an optimization plugin. Maybe both helped for a month, and then the site was slow again. This post explains, in plain terms, what is actually slow on most business websites, why the usual fixes wear off, and what fixes the problem permanently.

What happens when someone opens your site

Picture one visitor. They tap a link to your homepage on their phone. On a typical page-builder or CMS site, meaning a site assembled by software running on a server, here is the chain of events that tap sets off.

The server wakes up and asks a database, which is a kind of filing cabinet for your content, for the text and settings that belong on your homepage. Then it assembles the page: the theme supplies the layout, and each plugin bolts on its piece. Only when all of that is finished does the server send the page to your visitor.

The page does not travel alone. Every plugin ships its own scripts, small programs that the visitor’s phone now has to download and run before the page settles down and becomes usable.

By default, that entire chain runs again for every single visit. One tap, and your page is manufactured from scratch, one more time, on a server that may be busy doing the same thing for a hundred other sites.

Why the usual fixes do not hold

The common fixes all treat one symptom of the same disease. The disease is that your pages are manufactured on demand.

A caching plugin keeps ready-made copies of some pages so the server can skip part of the assembly. An image optimizer shrinks your photos. A bigger hosting plan gives the server more muscle to do the same wasteful work a little faster.

Each of these can help for a while. But the patches are software too. They need updates, they conflict with each other, and they add weight of their own. Meanwhile the site keeps growing: another plugin here, another popup there. A few months later the site is slow again, and the advice is to buy the next fix.

If you have been through this cycle more than once, the problem was never you, and it was not really the plugins either. The approach itself has a ceiling. You cannot patch your way out of doing the work on every visit.

The fix: build the page before anyone asks for it

There is a different way to build a website. Instead of assembling each page at the moment a visitor asks for it, every page is prepared once, in advance, as a finished file. When someone visits, the server has exactly one job left: hand over a file that is already complete.

Sites built this way are called static sites. The name sounds like a drawback, but static here does not mean the site cannot change. It means prepared in advance. You can update a static site whenever you like; the pages are simply rebuilt at that moment instead of at every visit.

For your visitor, nothing is queried, nothing is assembled, and there is almost nothing for their phone to run. The speed comes from removing the unnecessary work, not from a trick or a plugin.

What this means for your hosting bill

Handing over finished files is close to the cheapest thing a server can do, and mainstream hosting providers offer it free on standard plans. Those are not trials or introductory offers. They are ordinary plans that a small business site fits inside comfortably.

That changes what a website costs to run. Once a static site is built, the recurring bill is the domain name, which is the address you already pay for today. This website runs exactly that way, and the work page breaks the running cost down line by line if you want to check.

How to check your own site

You do not have to take any of this on faith. Google publishes a free tool called PageSpeed Insights that anyone can use on any website. Paste in your address and it runs Lighthouse, a public auditing tool built into the Chrome browser, against your site and hands back a performance score out of 100.

Look at the mobile score first, because a phone on a mobile connection is how most visitors arrive, and it is where slow sites suffer most. This is the same public tool behind the scores on my own work page, so you can compare like for like.

If your score is low, you now know the reason: your pages are being manufactured on demand, and no plugin changes that. If you want to know what a rebuild would fix, send me the address and I will tell you.