Speed Is an Aesthetic
Performance is not an engineering concern applied after design. It is part of how the work feels.
4 min
read
Studios treat performance as something that happens after the design is approved. Engineering optimises. Designers move on. But the perceived quality of an interface is inseparable from its responsiveness. A beautiful page that takes four seconds to become useful is not a beautiful page. It is a slow one with good screenshots. Most of the weight is decided in design, not in code. Image counts. Font loading. The number of distinct components on a first view. The decision to autoplay video above the fold. By the time it reaches engineering, the budget is already spent.
THE FIRST VIEW IS THE WHOLE ARGUMENT
Users form a judgement before the page finishes loading. What they see in the first second sets their expectation for everything after.
This makes the hero the most expensive real estate on the site, in both senses. It is where designers want the largest imagery and where the load cost hits hardest.
A single unoptimised hero image can outweigh every other asset on the page combined. Serving it at the right dimensions, in a modern format, with explicit sizing to prevent layout shift, costs nothing visually and changes the experience entirely.
Fonts deserve the same scrutiny. Every additional weight is another blocking request, and most projects ship weights they never use.
DESIGN THE LOADING STATE
Loading is a state, and unstated states get designed by default — usually badly.
Content that jumps as images arrive reads as broken even when nothing is wrong. Reserving space is a layout decision, made in design, not a patch applied later.
Skeleton screens are overused. They are useful when the shape of the content is predictable and the wait is genuinely short. When the wait is long, they simply animate the frustration.
Sometimes the honest answer is to show less. A page that renders its text immediately and brings imagery in behind it will feel faster than one that waits for everything to be perfect.
Speed is not the absence of design. It is a constraint that produces better decisions, in the same way a tight grid does.
