This post has originally been published on https://juristr.com/blog/2019/08/ngperf-route-level-code-splitting. Go to juristr.com/blog for more content
This article is part of my "Angular Performance Week" series, where I publish a new video each day based on the performance articles on web.dev/angular. Today we're taking a look at route-level code splitting to increase the TTI of our application.
Note: this article and attached Egghead video lesson are based on the articles on web.dev/angular by Minko Gechev and Stephen Fluin. Full credit goes to them 👍
Angular Performance Series
- Route Level Code Splitting
- Preload Lazy Routes in Angular
- Performance budgets with the Angular CLI
- Optimize Angular's Change Detection
- Virtual Scrolling for large lists with the CDK
- Precaching with the Angular Service Worker
Don't miss the other videos by subscribing to my newsletter.
Route Level Code Splitting
TTI (Time to interactive) is an interesting metric that measures how long it takes for your app to be responsive, s.t. the user can interact. This is a good performance indicator. One way to improve TTI is to only load the minimum necessary part of our app, and then consequently "lazy load" other parts as they are needed.
In this video lesson we're going to implement route-level code splitting and lazy loading, step by step.
Bonus: Showing a loading indicator for lazy routes
Original web.dev article
Wanna read the original web.dev article? Check it out here!.
Top comments (0)