Web Performance: The African Case
summary
Maps African constraints to concrete numbers: slow costly 3G, phones with ~2 GB RAM, 15 GB monthly plans that cost up to 4× minimum wage in Zimbabwe, and a hypothetical 30 MB SPA bundle that can eat a month’s pay. Shows tools and outcomes: Qwik’s resumability with per‑interaction JS chunks, a 1 KB global listener, service worker caching of needed chunks, and demoed lazy execution that fetches only the interaction code — demo runs and pages become interactive far sooner. Presents conversion lifts: 850 ms → +7%, 100 ms → +1%.
AI-written summary · about
chapters (12)
- 0:00Web performance in Africa
- 1:07Internet penetration in Africa
- 3:49Why performance matters
- 5:33How Google measures performance
- 7:16Poor performance impact
- 9:30Conversion rates impact
- 10:32Single page apps evolution
- 13:45JavaScript and performance
- 16:12Introducing resumability
- 21:18Resumability reduces execution
- 24:34Demo: resumability with Quick
- 30:19Q&A
related talks
24mWeb Performance: The African Case
32mSolving Problems for African Soil
46mWeb Performance in 2018
27mThe Secret Web Performance Metric No One Is Talking About
37mMobile Web Performance
30mEmpathy Driven Development: Boosting performance by implementing for unfavorable conditions
31mJS in Extreme Conditions: WebApps for the Refugee Aid Movement
37mAdapting to the Mobile Web F̶u̶t̶u̶r̶e̶ Present