Suggest an editImprove this articleRefine the answer for “What is lazy loading of routes?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Lazy loading of routes** is a way to load parts of the application only when they are actually needed, instead of loading everything at startup. **Key point:** it is deferred, on-demand loading that helps avoid pulling in the whole project at startup.Shown above the full answer for quick recall.Answer (EN)Image**Lazy loading of routes** is a way to load parts of the application **only when they are actually needed**, instead of loading everything at startup. --- ### Why it's needed: - Reduces the initial weight of the application - Speeds up the first load - Makes large projects more flexible and scalable --- ### How it works: 1. You have an `AdminModule` that not every user needs right away. 2. Instead of a direct import, you point to it from the routing config: ```ts { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) } ``` 3. When the user navigates to `/admin`, Angular **lazily loads the module and its components.** --- **Summary:** Lazy loading is **deferred, on-demand loading** that helps avoid pulling in the whole project at startup.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.