Performance Matters
summary
Bundle size is the main driver of startup slowness—examples include a 15 MB app shrinking dramatically after extracting SVGs—and common fixes are concrete: set sourceMap and namedChunks true in angular.json, run source-map-explorer to see who contributes kilobytes, use bundle budgets (warning/error) to prevent backslide, prefer lazy loading with loadChildren dynamic imports, enable gzip compression (900 KB → ~240 KB over network), serve over HTTP/2 and consider differential serving or Angular Universal prerendering.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:13Values
- 4:30Web Vitals
- 9:45Bundle Budgets
- 10:43Stay Up To Date 10.0.0 (2020-06-24)
- 13:05Be careful what you import
- 14:32Bundle Size Demo
- 22:46Maximize the code run
- 24:12Content Compression
- 25:36HTTP2
- 26:37Throughput
- 27:16Extra Round Trip
- 27:503. Server Push with Firebase
- 28:08Differential Serving & Loading
- 28:33Differential Loading
- 28:53Angular Universal
- 29:23Consider SSR / Prerendering
- 29:51Universal Today
- 30:36Universal Options
- 30:55More Lazy Loading!
- 31:26Have fun!
related talks
28mDebugging the Performance of 4,860 Angular Apps
16mBest Practices
18mA Guide to Instant Loading Angular Apps
20mTools for Fast Angular Applications
40mOptimized Angular Apps: Smaller, Faster, Better
22mBuilding Fast Angular Applications from End
17mRethinking Angular Architecture & Performance
31mOptimized Angular apps: smaller, faster, better
