Frontend & browser·Modules, bundling and the build
the settings screen's code is not downloaded until someone actually opens the settings screen.
Code splitting
Cutting the bundle so that code is only fetched when it is needed, usually along route or interaction boundaries. It is the highest-leverage size optimisation available because it removes code from the initial load without deleting anything. The cost is a request at the moment of use, so a split at the wrong boundary trades a slow first load for a stutter on every click.