Performance Checklist for the Mobile Web
summary
Mobile web performance is about more than load time: 40% of users abandon pages after 3 seconds and variable frame rates (30–45fps) crash engagement; decode + resize of an oversized image can cost ~80ms (51ms decode + 29ms resize). Checklist items include use WebP when possible, enable gzip/SPDY on the server, batch network requests to avoid the cellular radio 1–2s wake cost, reduce render weight (avoid costly CSS combos), batch DOM reads/writes, pre-allocate or use object pools to minimize GC, and use Chrome tracing, DevTools Timeline, PageSpeed and WebPageTest to measure.
AI-written summary · about
chapters (23)
- 0:00Intro
- 3:50User Truth
- 6:52Performance
- 7:37Network Performance
- 10:38Responsive Design
- 13:25High Data Traffic
- 15:07Performance Tools
- 16:47HTML5 Devcom
- 17:48Rendering Performance
- 21:53Image Size
- 22:42Image Resolution
- 23:56Reflows
- 26:39Backlash Tracing
- 27:33Timeline
- 28:03Memory
- 32:37Know Your Growth Rate
- 37:21Resources
- 37:47Questions
- 40:29Memory Management
- 41:12Garbage Collector
- 44:08Garbage Collection
- 45:58Dev Tools
- 49:11QA
related talks
37mMobile Web Performance
43mThe Mobile Web: MIA
37mAdapting to the Mobile Web F̶u̶t̶u̶r̶e̶ Present
23mPerformance Optimizations for Progressive Web Apps
40m“Performance by Design”
57mHigh Performance Mobile
39mGiving you ways to increase, but also explain site performance, to your boss.
13mMobile Web Performance and User Experience