Performance is not a feature. It is an operating cost that compounds in multiple directions at once: infrastructure spend, accessibility failures for users on slow networks or older hardware, and resilience margins that shrink every time an unnecessary script adds latency to an already pressured request path.
The fastest efficiency gains still come from repeat-visit behavior. If users are redownloading large assets on every visit because cache policies were never set deliberately, both your infrastructure bill and your environmental footprint scale linearly with traffic. Cache hit rate is the leading indicator to fix first.
THE_REAL_COST_OF_REPEAT_DOWNLOADS
Most web products waste more bandwidth on repeat visits than on first loads. Fonts, stylesheets, and JavaScript bundles get redownloaded because someone set Cache-Control: no-cache conservatively during a debugging session and nobody reverted it. Images that could be served at the rendered viewport size are served at design source dimensions. Decorative animations run on every page visit, consuming CPU and battery on behalf of no perceivable user benefit.
These are not small marginal costs. On high-traffic products, they translate to real infrastructure spend, measurable battery drain on mobile devices, and worse performance for users on constrained connections. Accessibility and sustainability share a cause here — lighter, calmer pages help everyone.
"A performance budget is also a carbon budget."
THE_INP_SHIFT_AND_WHAT_IT_CATCHES
Google replaced FID with INP (Interaction to Next Paint) as a Core Web Vital in March 2024. INP measures responsiveness across all interactions during a page visit, not just the first one. Teams that optimized for FID may have pages that score poorly on INP despite looking fine under old metrics. Long tasks blocking the main thread are the usual culprit — animation loops, heavy synchronous computations, or third-party tag managers firing on every interaction.
- Serve images at the dimensions they will actually be displayed — not design source size, and not 2x when the rendered container is small.
- Audit third-party scripts quarterly and remove any that have no clear measurable benefit. The tag that seemed useful during evaluation rarely gets removed when it turns out to be expensive.
- Review cache policies for static assets — fonts, icons, versioned stylesheets, and versioned JavaScript should have long max-age values with cache busting on deploy.
- Break up long tasks on the main thread: anything above 50ms that could be deferred, chunked, or moved to a worker should be investigated.
SIMPLER_STACKS_LAST_LONGER
Not every team needs to go to extreme lengths. Most have several high-return efficiency improvements sitting in the backlog that nobody has prioritized because there is no shared denominator. A performance and efficiency budget provides that denominator. Treat it the same way you would treat a financial budget — not as a target to hit once, but as a constraint that governs tradeoffs continuously. Simpler stacks also tend to fail more gracefully on constrained devices, which improves both resilience and accessibility at the same time.