Core Web Vitals are a design constraint, not a report card

There are two ways to hold a performance score. The common one: build the site, run Lighthouse, triage the red numbers, ship whatever survives the deadline. The score is a report card — something that happens to you.

The other way is to treat vitals like a structural engineer treats load: a constraint that shapes the design from the first sketch. Every site we ship holds a 90+ performance score not because we're better at optimizing, but because we never create the problems that need optimizing.

LCP is an art-direction decision

Largest Contentful Paint is usually decided the moment someone chooses the hero. A full-bleed 4K photograph with a text overlay has an LCP floor no amount of engineering can dig under — the bytes have to arrive. A typographic hero with generated art renders in the first paint. That's not an engineering trade-off; it's an art-direction decision with an engineering consequence.

This is why our design reviews include a budget column. Every section of every template carries an estimate: what does this cost to render? Designers who see the number make different choices — better ones, usually, because constraints are where style comes from.

CLS is a layout discipline

Cumulative Layout Shift isn't a bug; it's a design that never decided how big things are. Reserved space for images, fonts loaded with fallback metrics, no content injected above what's already read — these are layout decisions. A design system that specifies dimensions eliminates CLS by construction. Ours do, and our sites sit under 0.05 without a dedicated optimization pass.

The compounding return

Fast sites convert better — that's documented everywhere and we see it in every engagement. But the quieter benefit is architectural: a codebase built under a performance budget stays simple. Fewer scripts, fewer dependencies, fewer moving parts. Performance discipline turns out to be complexity discipline wearing a different badge.

The report-card approach treats speed as a feature you add. It isn't. It's a property the site either has by design or acquires at great expense later. Calculate the load before you pour the foundation.