Pushing Pixels
summary
Argues that delivery should target visible pixels not pages, claiming an SPA shoved hundreds of resources so a hero image appears ~10.5s while static HTML renders under a second; advocates breaking UI into islands architecture (uses Astro as an example) and loading interactivity per-island. Demonstrates measurement work: SpeedCurve’s hero times idea led to Chrome’s element timing implementation, recommends instrumenting specific elements, shows iterative cross‑discipline builds and a CDN/static-first pipeline that actually speeds real sites. Also uses MidJourney images.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:07Personal journey
- 5:09AI and web language
- 8:21Limitations of page metaphor
- 11:53Breaking content into islands
- 12:37Collaborative teams
- 17:10Web as time-based medium
- 19:42Organizing islands
- 20:03JavaScript frameworks rise and fall
- 22:57Islands architecture
- 24:22Astro framework benefits
- 27:18Critical rendering path
- 31:54Islands in practice
- 32:39Measuring user experience
- 36:59Core Web Vitals challenges
- 39:12Critique of Core Web Vitals
- 44:17Web performance working group
- 46:04Element timing metric
- 49:14Key takeaways
- 51:00Q&A
related talks
01h 04mFrom Zero to Hero - Web Performance
46mSpeed Matters: Client Side Performance Improvement Tips & Tricks
39mPeeling an orange: progressive website loading
01h 03mBetter performance === greater accessibility
31mBack to boring
01h 03mSpeed up your Web Application
40m“Performance by Design”
48mThink Fast, First: Empowering a Performance Culture