← Topics
Topic · Performance

Web performance by construction

Speed as an architectural decision: load time, robustness, cost.

1 project · 2 notes

The speed of a site is not an end-of-project setting, it is an architectural decision.

A statically generated site, served from a CDN, with no database to query and no admin layer to wake up, starts with a lead that no late optimisation ever makes up. Images weigh exactly what they need to, JavaScript only shows up where it genuinely serves something.

What that changes for you: pages displayed before you have had time to wait, search rankings that are not penalised, and hosting costs that stay negligible on the day traffic takes off.

Featured
Salomon Golden Trail Series
Project

Salomon Golden Trail Series

Salomon's world trail running circuit, from the design to the JS.

See the project →

Notes

All notes →
04 JUL 2026Static never goes downA static site is HTML files served as they are. No application server computing on every visit, no exposed database, no plugin full of holes. People sometimes…
Front-endPerformance
30 JUN 2026Speed is a decision, not a settingPeople 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…
PerformanceStrategy

Other topics

All topics →
Design46Front-end25SCSS9CMS8No-code8EVA CSS7Motion design7UX7Fluid CSS6Strategy6Method5Open source4AI3CSS3Prototype3Shopify1
Contact
Your project becomes the next point of focus.
Turn on at least 2 areas of expertise to reach me