Thinking Beyond Core Web Vitals
summary
After a year working on web apps for Nigeria and Kenya the claim is that Core Web Vitals target a privileged fast‑connection user and miss people on slow networks and low‑end phones so a new concrete metric patience — how long someone waits before deciding a site is broken — gets proposed. Practical tools used include Network Information API, service workers, preconnect/prefetch/preload, back‑forward cache and DevTools layers, plus progressive enhancement and breaking long tasks. A PWA case shows real wins: 33% higher conversion, 50% lower bounce, 12× more users versus native, less data and storage.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:47Core Web Vitals limits
- 2:48African market harshness
- 8:27High latency challenges
- 13:43Mobile-first markets
- 17:00Patience metric
- 18:45Visibility for users
- 23:25Progressive enhancement
- 25:14Resource hints and caching
- 28:09Image and video optimizations
- 30:41Network Information API
- 31:27Third-party resource limits
- 32:33Service workers benefits
- 34:02Excessive browser layers
- 35:48Breaking long tasks
- 36:28Key optimizations summary
- 37:55Empathy and real user data
- 39:19Q&A animations
- 40:45Testing harsh conditions
- 43:15Performance universal benefits
- 44:43Building empathy remotely
related talks
15mCore Web Vitals – Measuring Performance Like a Pro
29mCore Web Vitals: Put Your App into Orbit with Best Practices
25mCore Web Vitals under control
27mThe Secret Web Performance Metric No One Is Talking About
39mCore Web Vitals under control
34mOptimizing Web Applications with Core Web Vitals
31mHacking Web Performance
23mPerformance Optimizations for Progressive Web Apps