Delivering Responsibly
summary
Shows concrete steps: extract and inline critical CSS inlining from full stylesheets, use loadCSS/loadJS polyfills and link rel=preload to avoid render-blocking, and detect fonts with FontFaceObserver font-loading so text appears instead of a blank page. Uses WebPageTest and PageSpeed; measures a 9 MB page whose start-render drops from 12.5s to ~4s without shrinking asset weight. Notes HTTP/2 server push will replace many workarounds but current tooling and build-time extraction prove the approach works now.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:30Delivery Problems
- 6:36Optimizing Files
- 8:21Reducing Dependencies
- 11:23Render Blocking
- 23:34JavaScript
- 28:31Custom Fonts
- 36:31Weight of Assets
- 37:17Looking Ahead
related talks
42mDelivering Responsibly
32mStay Away From My Path!
29mHigh Performance in the Critical Rendering Path
38mCSS and the first meaningful paint
01h 03mBetter performance === greater accessibility
30mHigh Performance in the Critical Rendering Path
23mOptimizing page load speed on front end side
28mCSS and the Critical Path