Optimized Angular apps: smaller, faster, better
summary
Uses concrete Angular tools and numbers: check bundles with source-map-explorer (example removed an unused snackbar and saved ~3.5 KB), build for production, split routes with lazy loading via loadChildren and optional preloading, add offline caching with ng add @angular/pwa and tune performance vs freshness in ngsw-config.json, use SSR or prerendering with Angular Universal for faster first meaningful paint. Performance recipes for change detection: prefer pipes and memoization (lodash.memoize or decorators), set OnPush change detection, run heavy work outside Angular, and use trackBy in ngFor.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:43Maxim Salnikov
- 7:37Use lazy loading
- 10:20Preloading strategy
- 13:58NGSW configuration file
- 14:24Runtime caching
- 14:55Keep in mind
- 24:19Angular change detection (CD)
- 27:40Use pure pipes instead of methods
- 29:14Using method
- 32:04Memoization
- 38:02ChangeDetection Strategy.Default
- 39:29Go for your own CD schedule
- 43:34Angular App Performance
related talks
31mOptimized Angular apps: smaller, faster, better
40mOptimized Angular Apps: Smaller, Faster, Better
23mAngular optimization tips and tricks
20mTools for Fast Angular Applications
17mRethinking Angular Architecture & Performance
27mOptimizing Angular Apps - Techniques for Performance Excellence
43mAngular Performance Workshop
29mOptimizing Angular 2 Apps for Production