People still believe performance gets tuned at the end, by compressing three images and ticking a box. I wish that were true. A slow site is slow by construction: too many scripts, rendering that waits on the server, frames loading other frames. No plugin makes up for that.

What a second costs

One extra second of loading, and a share of visitors leave before they have seen the page. Google measures it and ranks on it. A visitor feels it, even without naming it: a fast site inspires trust, a slow one looks careless before the first word. Performance is not an engineer’s luxury. It is revenue that does not say its name.

Fast by default

I start from static: the HTML arrives ready, waiting on nothing. EVA CSS handles the scaling without JavaScript, with 99% fewer breakpoints. What little script remains loads when it is needed, not before. Pages that appear at once, on mobile as on fibre. Not because I optimised afterwards, but because I decided beforehand.

A slow site's cascade and a page that arrives ready, on one loading axis Two horizontal bands drawn from the same origin, on the left. On top, four blocks of equal width set end to end: waits on the server, too many scripts, frames, then, one line lower and starting where the third one ends, other frames. A vertical accent rule falls at the end of that fourth block, and the words the page is seen read just before it. Below, a single block of the same width, labelled at once, and the same vertical accent rule falls at its end, three blocks earlier, with the same words the page is seen just after it. Under both bands, an axis arrowed to the right carries the word loading and has no graduations. A SLOW SITE BY CONSTRUCTION waits on the server too many scripts frames other frames the page is seen THE HTML ARRIVES READY WAITING ON NOTHING at once the page is seen LOADING
What separates the two markers is not a setting, it is three more blocks.

Restraint as method

Going fast is not stacking optimisations, it is removing the superfluous. Every dependency, every script, every frame has a cost, and the total always ends up showing. The question is not « what do I add to speed this up », it is « what do I take away ». A fast site is first of all a site that carries little.

Five decisions along the project, and the height of their effect A horizontal axis arrowed to the right, between two labels: on the left I decided beforehand, on the right I optimised afterwards. Five vertical bars of decreasing heights stand on that axis, each in its place. The first, the tallest, is drawn in accent and carries the word static; then come EVA CSS, what I take away, when it is needed, and on the far right, almost flat, three images. A vertical axis on the left carries the word effect and has no graduations. I DECIDED BEFOREHAND I OPTIMISED AFTERWARDS THE EFFECT static EVA CSS what I take away when it is needed three images
The later the decision, the less speed it has left to change.

Speed is not a last-minute setting. It is a position, taken from the first line. And it is felt from the first visit.