I'm very glad someone posted that
Can You Afford It?: Real-world Web Performance Budgets
especially after what have been said in the Chrome dev summit 2017 keynote
where they heavily mention how PWA (Progressive Web App) is all the rage.
Here the intro
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 ~130-170KB of critical-path resources, depending on composition — the more JS you include, the smaller the bundle must be.
Anyway, it is a good read, the hacker news comments also, where people wonder "do we need all this JS?".
As a quick comment I would say it is still the same problem: web apps try to replace desktop apps and imho they fail, and also why I think it's where Adobe AIR and AS3 win.