A primer on performance
summary
Claim: images account for the largest bytes on a page (average image ~654 KB) so shaving one‑fifth of an image buys room for libraries like jQuery (86 KB). Tools and steps are concrete: use ImageOptim/TinyPNG/Imagemin and SVGOMG, serve with Picturefill, inline critical CSS with Penthouse, concatenate/minify via gulp, and run PageSpeed Insights or the Chrome timeline. Goals are specific: keep initial payload <1 MB, hit ~60 fps to avoid jank, and set a performance budget ~20% faster than competitors.
AI-written summary · about
chapters (24)
- 0:00Start
- 2:27Frustrated by Poor Performance
- 2:47Web Stress and the Doorway Effect
- 3:34Sensory Memory
- 5:54Ui Design
- 6:13Image File Types
- 8:04Compression
- 8:56Compressive Images
- 10:21Reading Images
- 10:53Picture Fill
- 12:48Css Triggers
- 14:26Style Audit
- 14:59Inverted Triangle Css
- 15:41Front-End Development
- 15:56Delivery
- 16:08Waterfall Graph
- 17:24Minify
- 17:52Critical Rendering Path
- 20:53Testing Tools
- 21:31Page Speed Index
- 22:37Google Pagespeed Insights
- 23:30Pagespeed Insights Go
- 24:13Performance Budget
- 24:42Review
related talks
25mDelivering Fast and Beautiful Images and Video
29mSpeed Essentials: Key Techniques for Fast Websites
48mFast and Beautiful: Modern Image Delivery Techniques
08mThe Performance Alphabet
32mBanish Image Bloat: Achieving Peak Performance with Image Performance Budgets
30mFast and Beautiful: Modern Image Delivery Techniques
46mFast and Beautiful Modern Image Delivery Techniques
31mDelivering Fast and Beautiful Images and Video
