New Perspectives on Performance
summary
Defines web performance as three measurable goals: visibility interactivity responsiveness and insists on a baseline that is measurable repeatable stable before changing code. Recommends Firebug + YSlow, using Google Analytics custom events to record DOMReady times, console.profile to find slow document.ready handlers, delaying initialization with jQuery.one, and using Ben Alman’s throttle/debounce (500ms) to cut events and Ajax calls. Gives a concrete win: switching to 8‑bit PNGs with alpha saved ~200 KB on one site.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:30Defining performance pillars
- 3:17Establishing a baseline
- 5:15Visibility optimization
- 9:00Interactivity improvements
- 12:12Responsiveness and feedback
- 16:32The business of performance
related talks
21mState of Performance
33mRedefining Web Performance
29mThe Road to Web Performance in 3 Critical Steps
30mPerformance as a Religious Experience
30mMeasuring Web Performance - Metrics & Tools
01h 04mNeed for speed 8, performance tuning of your web application
19mPerceived Performance, And Why It Matters
31mWe're All Doing the Best We Can