What a slow website actually costs
Load time is usually filed under engineering. It is a marketing number: it decides how much of the traffic you paid for ever sees the offer.
A slow site does not announce itself. Nobody complains; they simply leave, and they leave before anything has been measured well enough to explain why.
Speed is a business number
If a page takes four seconds instead of one, a meaningful share of arrivals never see it. When that traffic is paid, the waste is exact and calculable: you bought the click, the click bounced, and the invoice does not care.
This is why performance work belongs in the marketing conversation. It does not make the offer better. It makes the offer visible to a larger fraction of the people you already paid to bring.
The four things that are usually wrong
- Unsized images. A five-megabyte photograph scaled down in the browser still downloads five megabytes. Resizing at the source is the single cheapest fix available.
- Layout shift. Content that jumps while the page settles costs conversions even when the load is technically fast, because it makes a page feel unreliable.
- Script that blocks the paint. Analytics, chat widgets and font loaders, each individually reasonable, collectively holding the first render hostage.
- Server time. An uncached query on a page that never changes, repeated on every visit.
What we do about it
We measure before touching anything, because performance intuition is unreliable and the bottleneck is rarely where it feels like it is. Then we work in order of cost: images first, because they are usually most of the payload; then render-blocking resources; then the server.
Most sites do not need a rebuild. They need someone to sit down with the waterfall for an afternoon and remove what is not earning its place.
