Performance R
summary
Large-scale A/B experiments measure concrete user impact: injecting server-side delays from 50 ms to 2 s cuts engagement — a 2 s delay yields ~2% fewer queries and ~4% lower revenue per user — while 100–400 ms delays at Google produce ~0.2–0.36% fewer searches that grow over weeks and partly persist after stopping. Adding bytes (up to ~5× HTML) lowers clicks ~0.55% in the worst case. Implementing chunked transfer encoding to progressively render the header improves time-to-first-click and lifts clicks and satisfaction by about 7%.
AI-written summary · about
chapters (6)
related talks
57mHigh Performance Mobile
49mEvery Millisecond Counts Performance & UX
31mEvery Millisecond Counts: Performance & UX
01h 01mWeb Performance Deep Dive
34mOnce More with Feeling
04mPerformance is about people, not metrics
28mWhat we talk about when we say "web performances"
22mWhy Performance Matters - JSConf Budapest 201