Before it had live measurement tooling in place to check itself against, Braindoos wrote down an explicit, numeric performance budget for its own corporate website theme — Core Web Vitals thresholds and Lighthouse score floors, sourced from Google’s published guidance, with each threshold marked mandatory or advisory according to how confidently it could be stated without a live measurement behind it.
Applying that budget as a checklist surfaced a real violation: both the light and dark variants of the site’s header logo were being transferred on every single page load, together representing 386,723 bytes, regardless of which variant a visitor would ever actually see. The fix was not a blanket change. On the three registered pages configured without a hero image, the duplicate transfer was eliminated outright. On hero pages, where a scroll-driven crossfade effect genuinely needs both images present, the duplicate was instead mitigated through lazy-loading — a scoped fix rather than a one-size-fits-all one.
Two further changes followed the same budget: font delivery moved from a third-party CDN to locally self-hosted files, with one entirely unused font family dropped rather than hosted; and default WordPress scripts served to every anonymous visitor, regardless of need, were removed.
No automated mechanism enforces any of this today. Every change was checked against a written verification checklist and explicitly accepted by the site owner before being committed — manual, owner-accountable verification, stated plainly as such. No specific Lighthouse score or before/after improvement figure is claimed anywhere in this account; the discipline demonstrated is holding a written standard before the tooling exists to prove you’re meeting it.