Alex Russell, describing a prototype of “Never-Slow Mode” in Chrome:
… blocks large scripts, sets budgets for certain resource types (script, font, css, images), turns off document.write(), clobbers sync XHR, enables client-hints pervasively, and buffers resources without Content-Length set.
Craig Hockenberry, posting an idea to the WebKit bug tracker:
The situation I’m envisioning is that a site can show me any advertising they want as long as they keep the overall size under a fixed amount, say one megabyte per page. If they work hard to make their site efficient, I’m happy to provide my eyeballs.
Sometimes name-and-shame is an effective tactic to spark change.
Addy Osmani writes about an ESLint rule that prohibits particular packages, of which you could use to prevent usage of known-to-be-huge packages. So if someone tries to load the entirety of lodash or moment.js, it can be stopped at the linting level.
from CSS-Tricks https://css-tricks.com/the-bottleneck-of-the-web/