Performance: what Happens After the Backend?

on YouTube ↗42m

" summary

Examines what happens to web performance after the backend responds: discusses browser-side factors such as networking, resource loading, rendering, and JavaScript execution that affect perceived speed. Describes technologies and stages involved (HTTP, caching, CDN, browsers’ loading and painting processes) and how they impact overall performance beyond server-side optimizations.

AI-written summary · about

" chapters (14)

1. 0:00Introduction
2. 2:53Network analysis with WebPageTest
3. 10:02Critical path and user rendering
4. 13:18HTTP/1.1 vs HTTP/2 comparison
5. 16:53HTTP/2 limits and complexities
6. 17:14Extreme server-side optimizations
7. 19:01JavaScript interactivity issues
8. 22:37Measuring JavaScript execution
9. 27:12Client-side JavaScript profiling
10. 30:31Bundle and dependency analysis
11. 33:01Optimization validation
12. 33:44Third-party scripts impact
13. 34:45Ecological and societal stakes
14. 36:32Q&A

" related talks

• 42mFront-End PerformanceAna Encinar · JSDayES 2018
• 42mMaximum performanceEduardo Sada · FrontFest 2017
• 28mWhat we talk about when we say "web performances"Mattia Tommasone · Codemotion Milan 2017
• 30mPerformance as a Religious ExperienceAndrea De Carolis · CSS Day 2017
• 47mRendering Web PerformanceEduardo Sada · Commit Conf 2019
• 45mFrontend Architecture and PerformancePavel Pavelko · HighLoad++ Siberia 2018
• 22mNew Perspectives on PerformanceMenno van Slooten · jQuery Conference 2012 San Francisco
• 29mThe Road to Web Performance in 3 Critical StepsHernán Magrini · AmsterdamJS Conference 2017