Back to the Blog

Why speed is a design decision

By Olaitan Adebayo. 1 September 2026. A 4-minute read.

People talk about website speed as if it were plumbing: something you call a specialist about after the house is built. It is not plumbing. It is the front door, and every extra second is a second the door stays shut.

When a page takes four seconds to show anything, the visitor has already decided something about you. Not consciously, and not fairly, but firmly: this will be hard. Everything the page says after that is said to someone who is already leaving.

Speed is a design decision because every slow site got that way through choices. The hero video that autoplays at full resolution. The four font families. The carousel nobody asked for. The tracking scripts stacked six deep. None of those were engineering mistakes. They were design decisions made without counting their cost.

So I count. Every element on a page has to earn its weight in the same way it has to earn its place in the layout. If a picture cannot justify its bytes, it is not a design decision to include it; it is a design failure with a nice visual.

The sites I build are fast because speed is designed in, not tuned in later. The layout is decided knowing what it will cost to load. The images are sized for where they sit. The scripts are there because they do something for the visitor, not for a dashboard.

You do not need a faster developer. You need a designer who counts.