Why Slow?
summary
Talk explains why web apps feel slow and gives concrete fixes: use a modern starter like Ember CLI, serve static assets via an edge CDN, and maintain visible continuous performance monitoring. Shows that about 20% effort can yield large gains (one case improved Lighthouse from ~60 to ~90) and stresses addressing runtime issues like memory leaks and profiling for long-running industrial apps on cheap Android tablets; also discusses tools, AMP tradeoffs, and when load vs runtime metrics change.
AI-written summary · about
chapters (17)
- 0:00Introduction to the guests
- 2:45How I started working on performance (Ivan Akulov)
- 4:20Ember CLI (Andrey)
- 6:08Do modern bundlers really ignore performance?
- 7:50Why developers ignore performance tips in their projects?
- 11:37Different categories of frontend performance
- 14:52Performance metrics at the development stage
- 22:05Convenient way to monitor performance
- 26:49Has website loading speed improved?
- 36:20SPA - for all tasks
- 39:57Different approaches to performance in backend and frontend
- 48:17The first tool for measuring performance - Why Slow
- 51:34How performance tips for optimization have changed
- 57:48Why use bundlers with HTTP/2?
- 1:00:14Correct approaches to script bundling
- 1:03:23Q&A
- 1:04:09What tools exist for measuring runtime performance besides DevTools?
related talks
29mClient Says Your Awesome Web App Works Slowly. Now What?
21mWhy are web applications slow, and what to do about it
01h 12mMake It Seem Like Everything Loads Fast
42mBuilding quick apps in 2018
42mLazy, but Fast: How Taking It Slow Can Speed Up Your App!
22mPerformance Empathy
01h 03mSpeed up your Web Application
36mNobody cares about web performance. It's hard, expensive and unneeded