From nothing to a video under 2 seconds
summary
Goal is sub‑2s time to first frame on the Watch page; engineering focuses on reducing real payloads and prioritizing playback. Three load classes — cold/warm/hot loads — drive different strategies: small initial HTML chunks and JSON streaming so the browser can start rendering while backend queries run, a single 350 KB monolithic player that is initialized only once, and a lazy image scheme (green/yellow/red zones). Use QUIC/SPDY, Closure compiler, and chunked navigation; results: chunked navigation gives ~40% faster time‑to‑play and 13% fewer requests, and WebP ~20% savings in thumbnails (≈10% total page payload).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:03Performance metrics
- 12:59Page load types
- 17:18YouTube player optimization
- 20:33Video preview optimization
- 24:06WebP image format
- 27:21Module loading prioritization
- 30:10SPAce navigation framework
- 33:00Hot loading experiments
- 35:09Performance tools metrics
- 37:58Summary recommendations
- 40:06Q&A
related talks
31mDelivering Fast and Beautiful Images and Video
41mDelivering Fast Video without the Buffering
48mFast and Beautiful: Modern Image Delivery Techniques
23mOptimizing page load speed on front end side
36mHacking Web Performance
46mWeb Performance in 2018
42mBuilding quick apps in 2018
25mDelivering Fast and Beautiful Images and Video