JavaScript Performance in the Browser's World
summary
Browser devtools and webpagetest.org expose the real bottlenecks: forced layouts show as yellow triangles but here the real culprit is an algorithm, not microbenchmarks — the profiler reveals 89,000 Math.max calls caused by the masonry plugin recalculating the entire layout on each infinite-scroll append, producing long CPU bursts and GC pauses. Fixes that work: use CSS transitions, batch DOM work with requestAnimationFrame, and profile before optimizing.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:22Changing Your Mindset
- 2:17Loop Optimization
- 3:05Peephole Optimization
- 5:30Browser Tools
- 7:35Force Layout
- 9:59Chrome Force Layout
- 12:15Chrome Infinite Scroll
- 18:04Summary
