WebGL and three.js performance, done properly. I build and optimize heavy 3D scenes (particles, bloom, post-processing, GSAP) that still score in the PageSpeed 90s. Everything here comes straight from production work, not theory.
Use when a page with a heavy WebGL/three.js scene (particles, bloom, post-processing, GSAP ScrollTrigger) scores badly in PageSpeed Insights or Lighthouse, with a high Total Blocking Time, a long task attributed to gsap/requestAnimationFrame near load, "Other" dominating the main-thread breakdown, scores jumping ±10 between runs, or when the scene looks blurry/wrong on phones compared to desktop. MUST USE before tuning a three.js scene for PSI, before cutting particle counts "for performance", before profiling the scene in DevTools, and on every performance measurement of a page with a canvas/WebGL.