Designing for Performance
Performance is often treated as an engineering concern, but the biggest wins usually come from design decisions made long before a single line of code is written.
Layout shifts are a design problem
Every time an element jumps as the page loads, trust erodes. Reserve space for images, ads, and embeds. A loading state with the right dimensions is better than a smooth fade-in that pushes content down.
Less is faster
The fastest element is the one you never render. Question every component, every animation, every third-party script. If it doesn't serve the user's goal, cut it.
- Prefer system fonts or self-host a single weight.
- Defer non-critical CSS and JavaScript.
- Lazy-load below-the-fold media.
Measure, don't guess
Designs that feel fast on your laptop can crawl on a budget phone. Test on real devices, watch the field data, and let metrics guide your trade-offs.
"It's not the page weight that matters most — it's how quickly it becomes useful."
Performance is empathy
Every millisecond is a tax on your user's attention and data. Designing for performance is, at its core, designing with respect for the people you're building for.