Creating Performance Impact in a Changing Tech Landscape
summary
Argues for concrete moves: identify the critical rendering path and focus on pages that drive revenue, lean on synthetic + RUM (WebPageTest, SpeedCurve) and Lighthouse, and automate performance budgets in CI to catch regressions. Gives hard numbers: 77% of devs take on more testing, 67% push without testing, and examples that moved business metrics — a 15 kilobyte logo change that raised bookings and a 2 second improvement that nearly doubled mobile conversions; AB tests and benchmark dashboards prove it works.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Work smarter not harder
- 5:17Tech landscape challenges
- 8:10Chasing impact over comfort
- 12:03Focus on performance
- 19:08Prioritize pages and low-hanging fruit
- 23:58Small changes drive results
- 26:29Fighting regression
- 28:58Performance budgets
- 33:09Share the load and build teams
- 35:16Secure executive champion
- 37:44Quantify success
- 40:49Celebrate victories
- 42:34Simple principles
- 43:38Closing and Q&A
related talks
29mWeb Performance Kinetosis
44mThe 7 Habits of Highly Effective Performance Teams
48mPerformance culture through the looking-glass
36mNobody cares about web performance. It's hard, expensive and unneeded
12mPerformance In Context
50mHow to Think like a Performance Engineer
48mThink Fast, First: Empowering a Performance Culture
29mProgressive Testing to Meet the Performance Imperative