Optimized Angular apps: smaller, faster, better
summary
Clear, measurable tactics: use AOT and Build Optimizer plus bundle splitting and lazy loading to shrink initial bytes, verify results with source-map-explorer or webpack bundle analyzer, add the Angular Service Worker (ng add / PWA schematics) to cache assets and enable offline, consider server‑side rendering for faster first meaningful paint, and cut CPU work with OnPush change detection, pure pipes, memoization, ngZone.runOutsideAngular and manual detach/reattach of change detection.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:38Web App Performance
- 3:45Network performance strategy
- 4:41Build the app using prod
- 8:13Use lazy loading
- 11:39Preloading strategy
- 14:29NGSW configuration file
- 15:12Runtime caching
- 16:07Keep in mind
- 21:20Angular change detection (CD)
- 22:58Code performance strategy
- 23:17Use pure pipes instead of methods
- 24:52Memoization
- 25:59Use OnPush CD strategy
- 29:47Angular App Performance
related talks
40mOptimized Angular Apps: Smaller, Faster, Better
45mOptimized Angular apps: smaller, faster, better
23mAngular optimization tips and tricks
20mTools for Fast Angular Applications
17mRethinking Angular Architecture & Performance
43mAngular Performance Workshop
31mAngular Performance: Your App at the Speed of Light
29mOptimizing Angular 2 Apps for Production