Pushing the Limits of Mobile Performance
summary
Mobile Gmail and Docs focus on concrete wins: remove the 300KB parse penalty (old iPhone ~3s, modern browsers ~330ms, lazy parse down to ~40ms), start the XHR within the first 14KB to save up to 2s on 3G, and prefer large tap targets plus touchend handlers to avoid the 360ms click delay. DOM creation for 5,000 nodes costs tens to low hundreds of ms so method matters less; avoid inline events (Chrome can allocate ~10MB); use appcache patterns carefully and reset timeouts on progress events (2.5–5s between bites covers ~99%).
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:34About Andrew
- 3:16Cordova - 2013
- 4:13Fast App Demo
- 8:01JS Parsing
- 11:49Creating DOM
- 17:06Registering Events
- 20:13Event Delegation
- 25:02Offline-Only AppCache
- 28:40Network Matters - Page Load
- 31:21Network Matters - Format
- 38:28Use your time wisely
- 38:59#perfmatters
related talks
37mMobile Web Performance
37mAdapting to the Mobile Web F̶u̶t̶u̶r̶e̶ Present
32mResponsible Javascript
37mIt's just too Slow: Testing Mobile application performance
28mThe Browser Hackers Guide To Instantly Loading Everything
57mHigh Performance Mobile
43mThe Mobile Web: MIA
53mPerformance Checklist for the Mobile Web