I once worked on a frontend app where total loading time went from 15 seconds to 1.1 seconds. The strange part was that the app looked optimized. It already had lazy loading, preloading, and caching. On paper, the usual boxes were checked. But in practice, it still loaded too much code upfront, preloading managed to make loading slower, and cache kept dying each time we did a new deployment. The tools were there. The loading architecture was not. So I stopped treating loading as a bundler setting and started treating it as part of the app architecture: what must load now, what can wait, what can start earlier, what should stay independent, and how to keep cache useful for longer. Stop Loading Unused Code The first step is obvious, but still important: use lazy loading. The impact can be large. In a large production app I worked on, the generated static files were more than 22 MB in total. Before any lazy loading, opening any page required the browser to download code for the whole application.…