Draft — awaiting owner approval · noindex until released
Performance budgets that actually fail builds
Chimbuk studio4 min read
Most teams add Lighthouse CI, stare at a dashboard for a month, and quietly turn it off. The difference between theatre and engineering is simple: the build has to fail when the budget breaks.
Our standing three
- LCP < 2.0s on throttled mobile — the hero must be HTML + one optimized image, never a video.
- JS < 130KB first-load (gzip) — which forces animation discipline: CSS first, libraries only with a written reason.
- CLS ≈ 0 — every media slot ships with an aspect ratio. No exceptions, no 'it looks fine on my machine'.
What breaks first, every time
Third-party chat widgets and tag managers. The honest fix is server-side loading, consent-gated scripts, and a policy that any new vendor tag needs a one-line justification in the PR. It reads bureaucratic; it reads that way because without it the budget loses every argument.
A budget you can waive without review isn't a budget — it's a suggestion with a logo.
Begin the ascent
We build the things we write about.
If the field notes read useful, the work should too — tell us about your project.