Page speed

One number hiding a stack of small delays

Page speed reads like a single figure, but it is really a queue. The server has to answer. The browser has to fetch every piece the page asks for: images, fonts, stylesheets, scripts. Then it has to draw all of that into something a person can read and press.

Any one of those steps can be the slow one, and it is rarely the step anyone checks first. A common version: a photo dropped straight off a phone camera onto a homepage, several megabytes of it, shrunk down in the browser so it looks fine. On office wifi it is invisible. On a phone at the edge of your service area, it is the entire wait.

On the sites we get asked to look at, the weight tends to sit in four places: photos nobody resized, a font family loaded in six weights when the page uses two, tracking and chat scripts that arrived one at a time over several years, and a page builder that ships the code for every block it could have used rather than the ones you used.

Before any of that, the server has to answer at all. Crowded shared hosting can sit thinking before the first byte leaves, and nothing you trim on the page gets that time back.

The scores out of a hundred that testing tools hand back are a diagnostic, not the goal. The goal is seconds. If a tool says you gained four points and the customer still waits the same four seconds, nothing happened.

What slow costs when you are paying for the traffic

A visitor who leaves before the page appears never sees your phone number, your reviews, or the list of towns you cover. That is true whether they came from a search result, a map listing, or an ad. The ad case just stings more, because the money was already spent on a visit that never happened.

There is an honest tradeoff underneath this. Speed is bought by removing things, and some of the things you could remove are the things that get you calls. Pulling out a booking widget to gain a few points is a bad trade. Compressing the hero photo nobody ever sized is a good one. Most sites have plenty of the second kind left before they need to touch the first.

If you want to know which kind you are sitting on, our free website report card grades speed alongside the rest of the page, and it is one of more than 50 free tools published at kellywm.com/tools with no email wall.

The moving parts behind the number

Lazy loading holds images back until they are about to be seen, so the top of the page does not wait on the bottom. Minification strips the spacing and comments out of code files so there is less to send. Browser caching lets a returning visitor reuse the files they already have. A CDN keeps copies of those files on servers near the visitor instead of in one city.

None of that is exotic, and none of it is a one-time job. Sites get slower the way garages get full. One thing at a time, each one reasonable on its own.