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.
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.
Speed is not a last-minute setting. It is a position, taken from the first line. And it is felt from the first visit.
