Measuring what matters
summary
Explains that the User Timing API lets developers record exact start and end points for critical sections so changes map to the things users actually notice, demonstrates using it to time DOM work and resource handling, and reports adoption at 23% of top sites from HTTP Archive; cites the Filament Group result where simply prioritizing visible content improves perceived UX without changing traditional load metrics, notes tooling like SpeedCurve and Akamai integrations, and calls for making user timing easier and more widespread.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:34Marshmallow Cannon
- 1:29How we measure
- 2:13Web performance
- 3:14Changing the user experience
- 4:05User timing
related talks
48mHow I learned to stop worrying and love UX metrics
06mMeasurement is Not Enough: Rise of Performance Analytics
36mMoneyball for Performance Metrics
01h 02mWeb Performance Tuning with browser APIs
18mWebsite performance from user perspective
39mGiving you ways to increase, but also explain site performance, to your boss.
50mWeb Performance APIs You (probably) Didn't Know Existed
35mWeb Application Performance Testing from Users Perspective