Web performance APIs you (probably) didn't know existed
summary
Shows which concrete browser APIs reveal real causes and how teams use them: subscribe to PerformanceObserver entries for layout shifts, element timing and first-input to attribute jank; read server-timing header values to pinpoint backend stalls; detect long tasks (>50 ms) and use self‑profiling or the memory API to find leaks (example: a map drawing 100k points). Describes native lazy loading, resource hints, priority hints and the emerging scheduler primitives like isInputPending and postTask to keep UIs responsive; cites mobile long tasks being up to 12× worse and >50% abandonment after 3s.
AI-written summary · about
chapters (18)
- 0:00Start
- 8:44MEASURING
- 13:35LAYOUT INSTABILITY
- 17:45EVENT TIMING
- 19:02LONG TASKS
- 21:08UserAgentSpecific Memory
- 21:42MEMORY LEAKS
- 24:00RESOURCE TIMING
- 25:11SERVER TIMING
- 27:02BATTERY STATUS
- 27:34NETWORK INFORMATION
- 30:50RESOURCE HINTS
- 32:31DNS PREFETCH
- 34:01PRIORITY HINTS
- 38:03SCHEDULING & THE WEB
- 39:05NATIVE SCHEDULER
- 51:00BANDWIDTH MIX
- 54:01BUSINESS OUTCOMES
related talks
50mWeb Performance APIs You (probably) Didn't Know Existed
22mWeb Perf APIs That You (Probably) Never Knew Existed
01h 02mWeb Performance Tuning with browser APIs
43mPlanet of the APIs: A Tale of Performance and UX
58mA Look At Modern Web APIs You Might Not Know
16mCoding Session: Stunning Performance
29mWatch your back, Browser! You're being observed
18mWebsite performance from user perspective