Angular: The Interactive Journey Angular Intermediate

Shipping: budgets, lazy routes, and a11y

Performance and accessibility are product features

Bundle size, time-to-interactive, and keyboard accessibility are not polish — they are the product. Angular's build pipeline has opinions: configure bundle budgets, lazy-load feature routes, run accessibility audits on real devices, and treat regressions as bugs.

  • Set bundle budgets in angular.json — warn when a chunk grows unexpectedly.
  • Lazy load feature routes that are not needed on first paint.
  • Prefer standalone components to keep tree-shaking aggressive.
  • Run Lighthouse on production builds; fix the top accessibility issues first.

Takeaways

  • Budgets turn perf discussions into CI signal.
  • Performance regressions and a11y issues are real bugs.
  • Ship small, ship often, measure honestly.

Enjoying This Lesson?

Your support helps create more comprehensive courses and lessons like this one. Help me build better learning experiences for everyone.

Support Awashyak