Steve Souders interviewed at Velocity 2011
summary
Mobile performance is moving from infancy to rough drafts of best practices: many popular sites still miss basics like expires headers on mobile assets, while higher-impact work requires local storage and App cache/manifest rewrites. Expect remote debugging (Weinre, Chrome remote, Opera Dragonfly) and services like Blaze.io MobiTests to be used for hands‑on iteration. Measurement gaps remain: the Web Timing spec and Google Analytics timing aren’t widely available on phones, and HTTP Archive shows modest shifts (Flash ~51% to ~48%).
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:17Mobile performance best practices
- 2:25Mobile performance challenges
- 4:03Mobile performance issues
- 6:05Mobile performance tools
- 9:17Measuring performance
- 12:23HTTP Archive
related talks
07mJoshua Bixby interviewed at Velocity 2010
09mRobert Castley, Lead Solutions Consultant of Keynote Systems: Velocity EU Conference 2013
37mAdapting to the Mobile Web F̶u̶t̶u̶r̶e̶ Present
41mA Decade of Disciplined Delivery
43mThe Mobile Web: MIA
57mHigh Performance Mobile
53mPerformance Checklist for the Mobile Web
50mWeb Performance APIs You (probably) Didn't Know Existed