The slow parts of a website are drawn in week three, long before anyone is asked to make it fast.
Speed is usually treated as a job for the end of a project. The design is signed off, the site is built, and then someone is asked to make it fast.
By then it is too late. The slow parts were drawn in week three.
Where the weight comes from
On the sites we are asked to fix, three things account for most of the wait.
- Images sized for the largest screen and sent to every phone.
- Typefaces in six weights when the design uses two.
- Scripts added for one feature on one page, and loaded on all of them.
None of these is an engineering mistake. Each is a design decision that nobody priced.
A budget, agreed at the start
We now set a budget before any design: how heavy a page may be, and how long it may take to show on a mid-range phone. It sits in the brief beside the page list.
A page that loads in a second feels designed. A page that loads in four feels broken, however it looks.
When a design would break the budget, we see it the same day, because design and code happen in the same room.
What it buys
Every page of the Ironvale site paints in under a second on a phone. Nobody on that project spent a week on performance. It was simply never spent.
Fast is not a feature you add. It is a number you agree to keep.





