Why slow pages quietly cost you enquiries, and the handful of things that actually move the needle.
Speed gets filed under technical, which is why it gets ignored. Nobody loses sleep over a loading time. What they would lose sleep over is the number of people who wanted to contact them and left before the page appeared, and those are the same thing.
Nobody emails to say your site was slow. They just go somewhere else, and you never learn they existed. That is what makes speed such an easy problem to have for years without noticing.
The effect is worst exactly where it hurts most. Someone on a phone, on mobile data, looking for a local service, comparing three options. They are not committed to you. A few seconds of blank screen and they are on a competitor's site, and neither of you knows it happened.
It compounds too. Search engines factor speed into what they show, so a slow site gets seen by fewer people and converts fewer of those it does reach.
Most speed advice is a list of forty items. In practice, on a small business site, four things account for nearly all of it.
Images. Almost always the biggest single problem. A photo straight off a phone can be four or five megabytes. Sized properly for the web it might be under two hundred kilobytes, and look identical on screen. One oversized hero image can outweigh everything else on the page combined.
Third-party scripts. Chat widgets, analytics, tracking pixels, embedded maps, cookie banners. Each one is code from someone else's server, and your page often waits for it. Three or four of these is the difference between a fast site and a sluggish one, and most sites are carrying at least one nobody remembers adding.
Fonts. A custom font is a file the browser must fetch before it can show text properly. One or two weights is fine. Six is a visible delay, and nobody can tell the difference between six weights and two.
Whatever the platform loads for you. On a builder or a heavy template, a large amount arrives whether your page uses it or not. This is the one you cannot fix without changing the underlying approach.
Chasing a green score is not the same as having a fast site. The score is a proxy, and proxies can be gamed while the actual experience stays poor.
Hosting matters, but usually less than the images. Moving to a faster server while still shipping five megabytes of photos gets you very little. Fix the payload first, then look at hosting.
Minifying code is worth doing and rarely the problem. Squeezing a few kilobytes out of a stylesheet while a single image weighs three megabytes is rearranging deck chairs.
Run your homepage through Google's PageSpeed Insights. It is free and takes a minute.
Two things to know when you read it. Look at the mobile tab, not desktop, because that is where your visitors and your problems are. And look at the field data at the top if it appears, since that is real people rather than a simulation.
Then read the opportunities list from the top. The first two or three items usually account for most of the problem, and the rest is noise.
Because we write sites from scratch, the page contains what your page needs and nothing else. There is no framework, no plugin stack and no editor machinery arriving alongside it.
Images are sized and compressed properly before they ever reach the site. Fonts are limited to what the design actually uses. Third-party scripts are added deliberately, one at a time, with someone asking whether the thing it does is worth what it costs.
That is not clever optimisation. It is mostly restraint, and restraint is easier when you control the whole page.
If your site feels slow and you are not sure why, send us the address and we will tell you what is causing it. No charge and no obligation, and if the answer is a straightforward fix you can do yourself, we will say so.