Mobile Web Performance

on YouTube ↗37m

" summary

Mobile pages balloon from 0.7 MB to 3.3 MB average, while many phones ship with 32–1,200 MB RAM and tiny batteries, so CPU, decoding and DNS latency kill perceived performance. Concrete fixes: shrink images with srcset/WebP, remove unused JS, gzip text, serve via CDN, chunk long work to under 50 ms tasks (RAIL), and avoid autoplay video or heavy analytics. Uses Lighthouse + WebPageTest + DevTools and an experimental page that drops load time from ~1.2s to 0.28s after removing analytics.

AI-written summary · about

" chapters (28)

1. 0:00Introduction
2. 4:12Mobile Devices
3. 6:46Mobile Performance Concerns
4. 7:48Story Time
5. 9:42Web Performance
6. 14:03Rail
7. 14:59Navigation Timing
8. 16:11Website Speed
9. 16:50Rules
10. 17:27Lighthouse
11. 20:52Solutions
12. 21:45Zoom
13. 22:21Optimize Images
14. 22:59Resize Images
15. 23:46Size Image
16. 24:40Image Source Source Set
17. 25:11Image Compression
18. 26:24CSS Effects
19. 27:55Optimize Video
20. 29:11Source Attribute
21. 30:20Everything Else
22. 30:34Style Sheets
23. 30:49JavaScript
24. 32:20Minimize DOM nodes
25. 32:39Squish vs Responsive
26. 33:03HTTP
27. 34:13AMP
28. 34:37Conclusion

" related talks

• 37mIt's just too Slow: Testing Mobile application performanceDoug Sillars · QA Fest 2019
• 53mPerformance Checklist for the Mobile WebColt McAnlis · HTML5DevConf 2013
• 41mMaking The Mobile Website FasterEiji Kitamura · JSConf.Asia 2013
• 35mRevitalising the Web - The Importance of Web PerformanceTamas Piros · Developers Summit 2021
• 43mThe Mobile Web: MIAAlex Russell · JSCamp Romania 2019
• 57mHigh Performance MobileSteve Souders · Mobilism 2011
• 33mRedefining Web PerformanceTim Kadlec · DeltaV Conference 2018
• 36mNobody cares about web performance. It's hard, expensive and unneededVitalii Ruban · VinnytsiaJS 2021