Somewhere along the way, performance became an afterthought. Here's why the fastest sites aren't the ones with the best infrastructure — they're the ones with the best design decisions.
Performance is a UX discipline, not a DevOps one. When we talk about Core Web Vitals, we're not talking about Lighthouse scores for their own sake — we're talking about the felt experience of using a product. A three-second load isn't just a three-second wait. It's doubt. It's the user wondering if something is broken. It's trust, actively eroding.
“Every 100ms of load time costs conversions. That's not a metric — it's a design decision you didn't know you were making.”
The sites we're most proud of are the ones nobody talks about — because they just work. They're fast on a 3G connection in a moving vehicle. They don't shift layout after images load. They don't block interaction while scripts execute. That invisibility is the achievement. Speed isn't a technical metric. It's a design value.
Where performance is lost
In our experience, most performance problems aren't infrastructure problems. They're design decisions that nobody costed: a hero image that's 4MB because it 'needs to be high quality', a custom font loaded for a single heading, a third-party widget that blocks rendering for two seconds. Every one of these was a choice. Every one could have been made differently.