Performance budget enforced in build
Why it matters
Without an enforced performance budget, bundle size drifts upward with each feature addition. A new charting library here, a heavier date picker there — after six months, your initial bundle has grown from 200KB to 600KB with no single commit being obviously culpable. ISO 25010:2011 time-behaviour captures the gradual degradation; an enforced budget makes the growth visible immediately, when a single PR pushes past the threshold, rather than during a quarterly performance audit.
Severity rationale
Low because performance budget enforcement is a preventive control — its absence does not immediately degrade performance, but allows gradual regression to accumulate undetected across multiple PRs.
Remediation
Add size-limit to your project and configure it with a 250KB threshold for the initial JavaScript bundle. Wire it into your CI pipeline so PRs fail if they exceed the budget.
// .size-limit.json
[
{
"path": ".next/static/chunks/pages/index-*.js",
"limit": "250 KB",
"gzip": true
}
]
In package.json scripts: "size": "size-limit", then add npm run size to your CI workflow after npm run build.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Performance Deep Dive Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · time-behaviour — Time Behaviour (performance efficiency)
Taxons
History
- 2026-04-18·v1.0.0·Initial import from performance-deep-dive·automated