audit-bundle-size — Find and Eliminate Bundle Bloat

Degree of freedom: MIXED — Offender triage and swap choice [HIGH freedom]; Phase 1 production build + analyser [LOW freedom — run exactly].

Audit-and-fix exception. Measure the payload, then shrink it. Runtime slowness → audit-performance.

Every kilobyte of JavaScript the browser must download, parse, and compile before showing anything costs real users real time. A large initial bundle is the #1 avoidable cause of slow LCP and poor Core Web Vitals. Find exactly what is bloating it and fix each item.

How to reason — Observe → Interpret → Classify → Severity

1. Observe — quote First Load JS / chunk gzip and the treemap contributor (file + package)
2. Interpret — is this unused code on the critical path, a duplicate, or a missing split?
3. Classify — giant-vendor / full-library import / missing-lazy / unused-dep / dev-in-prod / duplicate
4. Severity — by gzip on the initial route: >250 KB First Load JS = review; do not delete a feature to save KB