26 Oct Real-world Web Performance Budgets for #mobile apps suggests max of 170KB per page
TL;DR: performance budgets are an essential but under-appreciated part of product success and team health. Most partners we work with are not aware of the real-world operating environment and make inappropriate technology choices as a result. We set a budget in time of <= 5 seconds first-load Time-to-Interactive and <= 2s for subsequent loads. We constrain ourselves to a real-world baseline device + network configuration to measure progress. The default global baseline is a ~$200 Android device on a 400Kbps link with a 400ms round-trip-time (“RTT”). This translates into a budget of ~150-170KB of critical-path resources, depending on composition — the more JS you include, the smaller the bundle must be.
Sourced through Scoop.it from: infrequently.org
WHY IT MATTERS: we all think bandwidth is infinite but real world tells us that networks are very slow – even 3G – and that developers should be more careful about their page size to ensure they load fast and give users an enjoyable experience. Been doing web and digital for 20+ years and I am still surprised that we have to fight for every single KB we put on a page.