Angular comes with two built-in preloading strategies:

— NoPreloading (default): Disables preloading entirely. Lazy-loaded modules are only fetched when the user navigates to them.
— PreloadAllModules: Preloads all lazy-loaded modules in the background after the initial app load. This is ideal for smaller applications with limited routes, where preloading everything won’t overwhelm the network.

— Custom Preloading Strategies: Taking Control of Performance

Angular allows you to define custom preloading strategies to preload specific routes based on your app’s requirements. This gives you fine-grained control over which modules should be loaded in the background and under what conditions.