There's a perception problem in the web industry: performance is treated as a technical concern, separate from design. Designers design. Developers optimise. But this separation is false and costly. Performance is a design decision. Every image, every animation, every font choice, every component has a performance implication.
Speed Is a Feeling
When a website loads instantly, it feels premium. When it lags, it feels cheap — regardless of how beautiful the design is. Users don't consciously think 'this website is 2.3 seconds slower than average'. They feel it as friction, and they associate that friction with your brand.
Apple, Linear, Stripe — the most admired digital brands prioritise performance as a feature. Not because it's technically impressive, but because it communicates care. It says: we thought about your experience down to the millisecond.
The Performance Budget
We work with a performance budget on every project: a set of targets for page weight, load time, and Core Web Vitals that we commit to hitting before the site ships. This isn't an afterthought — it's a constraint we design within, just like the visual constraints of a grid system.
Our standard performance targets:
- Largest Contentful Paint (LCP): under 2.5 seconds
- Cumulative Layout Shift (CLS): under 0.1
- Interaction to Next Paint (INP): under 200ms
- Total page weight on home: under 500KB
- Lighthouse performance score: 90+ on mobile
A one-second delay in page load time results in a 7% reduction in conversions, 11% fewer page views, and a 16% decrease in customer satisfaction. Performance is a revenue issue.
Design Decisions That Kill Performance
Large hero videos. Custom fonts loaded from Google Fonts without preloading. Animations triggered by scroll that force layout recalculations. Full-width parallax effects. These are design choices — and they all have performance costs. A performance-conscious designer makes these decisions with eyes open, knowing the trade-offs and choosing accordingly.
The best designs are often the most performant. Restraint — knowing what not to include — is both a performance strategy and an aesthetic one. A clean, focused page with a single hero image and crisp typography will always outperform a visually busy page with video backgrounds and multiple animation libraries.
Building for the Real World
Most of your users aren't on a MacBook Pro with a 1Gbps connection. They're on a mid-range Android phone on a 4G network in a city with variable signal. Building for the ideal case means failing for the typical case. Performance-first design means building for real conditions — and delivering an excellent experience even under constraints.
