Let's make the web faster - tips from trenches @ Google
summary
Average pages load slowly because they balloon to about 1 MB and 84 requests and real users see desktop means over six seconds and mobile means over ten. Practical instrumentation uses the navigation timing API and Google Analytics (sample up to 10k visits) to break DNS, TCP, server and render times and produce histograms not averages. Use Chrome DevTools, WebPageTest videos and the speed index to measure visual completeness, and automate fixes with mod_pagespeed or PageSpeed Service.
AI-written summary · about
chapters (14)
- 0:00Introduction and web speed goals
- 2:30Why web performance matters today
- 7:24How slow are today's web pages
- 10:38Measuring user-perceived latency
- 14:15Using Navigation Timing API for diagnostics
- 16:21Google Analytics for performance insights
- 24:43Chrome DevTools for page optimization
- 31:09Remote debugging Chrome on any device
- 38:41WebPageTest for cross-browser analysis
- 44:25Speed Index and visual completeness
- 45:27Google PageSpeed tools and recommendations
- 49:19Automating optimizations with mod_pagespeed
- 51:30PageSpeed as a service and future tools
- 53:14Key takeaways and next steps
related talks
55mI Feel the Need for Web Page Speed
39mGiving you ways to increase, but also explain site performance, to your boss.
18mWebsite performance from user perspective
27mVelocity 2010: Urs Holzle
31mEvery Millisecond Counts: Performance & UX
33mDemystifying Web Performance Tooling
49mDemystifying web performance tooling and metrics
48mWeb Performance: How Fast Are We Going Now?