Fast By Default: Modern Loading Best Practices (Chrome Dev Summit 2017) 

Here are some of the links: Real-world performance budgets: infrequently.org/2017/10/can-you-afford-it-real-world-web-performance-budgets/ JavaScript parse costs: medium.com/reloading/javascript-start-up-performance-69200f43b201 HTTP Archive: beta.httparchive.org Chrome User Experience report: developers.google.com/web/tools/chrome-user-experience-report/ Preload: www.smashingmagazine.com/2016/02/preload-what-is-it-good-for/ Network information API: developer.mozilla.org/en-US/docs/Web/API/Network_Information_API Font Display: developers.google.com/web/updates/2016/02/font-display New PWAs: pinterest.com (logged in), tinder.com Webpack Bundle Analyzer: www.npmjs.com/package/webpack-bundle-analyzer ~ Addy

- mozjpeg - github.com/mozilla/mozjpeg - WebP - developers.google.com/speed/webp/

I think it's because that it does not change very often, it only includes utils and scaffold

We ship critical CSS in-line from the server side markup instead of client side resource, and the html markup will be cached by service worker based on different resource combinations (JS/CSS/manifest ...etc)

Roderick Hsiao thanks for answer