sdcorejs-review-performance-budget

To block regressions, you define numeric thresholds for Core Web Vitals and bundle size, then wire automated Lighthouse verification commands into your CI pipeline to block releases that fail these performance gates.

A performance budget converts subjective latency concerns into measurable numeric targets for API response times and DB queries. It uses automated verification commands to enforce these hard gates, eliminating debates over whether an app feels slow.

Yes, you can detect memory leaks and N+1 DB queries by defining backend performance budgets. The verification process uses query logging to identify N+1 issues and monitors RSS memory sampling to catch leaks during load testing.

Yes, this approach works for both frontend and backend. It defines per-metric thresholds for Lighthouse mobile checks and bundle size, while simultaneously applying backend verifier coverage via load testing, query logging, and memory RSS monitoring.

You apply per-track exceptions by letting stack skills inherit universal budgets and add specific probes. This process explicitly defines exceptions for each track, preventing silent divergence from the baseline performance thresholds.