Every Millisecond Counts: Performance & UX
summary
Shows concrete, measured impacts and fixes: 1% revenue per 100ms (Amazon), 0.5s → 20% fewer searches (Google), images make 63% of page weight so compressing and format-negotiating (WebP/JPEG‑XR) saves massive bandwidth. Demonstrates using WebPageTest API and Speed Index to drive scaling, SSIM/dSSIM to pick perceptual compression thresholds, CDN/Edge Side Includes for partial caching, and HTTP/2 features (multiplexing, server push, dependencies) plus preload/prefetch to reduce request overhead and improve perceived load time.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:36Open Source Contributor Release Manager for PHP 7.1
- 1:5216.30 FOR EVERY SINGLE PERSON ON EARTH
- 3:17CONCLUSION
- 6:21DESIGNERS
- 6:43SYSADMINS/DEVOPS
- 7:25USE THE CLOUD TO SCALE BASED ON PERCEIVED PERFORMANCE
- 9:39BACKEND DEVELOPERS
- 9:54DATABASE CACHING
- 10:11EDGE SIDE INCLUDES (ESI)
- 11:50IMAGE COMPRESSION
- 12:02FORMAT NEGOTIATION
- 12:56PERCEIVED QUALITY
- 16:45PERCEPTIVE QUALITY THRESHOLD
- 17:05FRONTEND DEVELOPERS
- 17:17PREDICTIVE BROWSING
- 18:29DNS PREFETCH
- 21:34NEW ARCHITECTURES
- 23:19MULTIPLEXING CAN USE ONE CONNECTION FOR PARALLEL REQUESTS
- 23:31SERVER PUSH
- 23:48WEIGHTS
- 25:35PERFORMANCE MATTERS
related talks
49mEvery Millisecond Counts Performance & UX
46mWeb Performance: Autobahn or Pedestrian Zone?
36mMoneyball for Performance Metrics
20mReal metrics for front-end performance
28mWhat we talk about when we say "web performances"
18mWebsite performance from user perspective
30mPerformance as a Religious Experience
41mHigh Performance Kick-Ass Web Apps