Follow the critical request
Take a content page with one heading, an image and a navigation menu. Open it with the cache empty and inspect the request sequence. If the browser must download a script before it can discover the image, the image has acquired a dependency that has nothing to do with its content.
Place the primary content in the first HTML response when its meaning is already known. Give the image its dimensions and a real source. Reserve eager fetching for the material that matters in the first viewport.
Count work as well as bytes
A small compressed script can still take time to parse and execute. On a busy phone that work competes with taps, scrolling and the next paint. Transfer size alone cannot describe the interaction cost.
Try the page under CPU throttling and operate the navigation while it loads. A useful budget includes a behavioural test, such as opening the menu as soon as it becomes visible, alongside an asset limit.
Write down the exception
A rich editor may deserve a substantial client bundle. A reading page probably has a different budget. Keep the rationale next to the route so the next engineer understands what the expenditure buys.
Repeat the measurement on a production build. Compare the same viewport, cache state and network conditions. Field measurements after release answer a different question: how the page behaves across the devices that actually visit.