Lazy loading postpones loading a dependency until it is needed or otherwise appropriate. This can keep code that never runs from consuming download bandwidth and parsing time. section 1.4.1
ES modules make dependencies explicit, allowing tools to identify unused code and defer loading dependencies. For code not needed on the initial render, `import()` can move modules into separate chunks. section 13.1 section 13.3.1
When deciding when code should load:
- Keep code needed for the initial render available; lazy-load code that is not needed yet. section 13.3.1
- Consider prefetching a lazy-loaded chunk so it is cached before the user triggers its import. section 13.3.1
A sign-up funnel
A site could split its landing and sign-up pages into separate chunks, then prefetch the sign-up chunk from the landing page. section 13.3.1











