Building a Performant Web Application in 2018
summary
Builds a demo web app called "oh my god dogs" using the Dog CEO API, shows a naive Promise.all then experiments with Promise.race and a generator-based buffer to make images appear sooner and finds the buffer noticeably faster. Measures smoothness with an FPS counter and discovers measurement code can itself drop frames. Switches server protocols to HTTP/2 multiplexing and uses Brotli static compression (claims ~73% smaller vs uncompressed) and notes CPU and bandwidth trade offs along the way.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:19Modern performance in the year of the dog
- 3:38Are websites 300% faster?
- 5:52What makes up performance?
- 6:05trade-offs
- 7:16limits features
- 7:38developer performance
- 8:18architecture
- 11:10developer freedom
- 13:18Does it make you more productive?
- 13:32page weight
- 13:50your team Choose what makes you productive.
- 14:56network performance
- 19:53measuring performance
- 21:30uncertainty
- 21:55server performance
- 22:27transfer protocol
- 23:34need to use ss!
- 24:10compression
- 26:50DESIGN
related talks
30mWeb runtime performance
32mPractical Performance Tips Building Progressive Web Apps
56mBoosting Web Performance in 2022
46mWeb Performance in 2018
50mWeb Performance APIs You (probably) Didn't Know Existed
03h 16mPUSHing web app performance with HTTP/2
26mWeb Performance in modern JavaScript world
44mSponsored session: Progressive Web Games