Webgl Pagespeed Rescue

Get a heavy three.js scene to 90+ on PageSpeed without changing how it looks.

Your page has a real 3D scene and PageSpeed punishes it: a high Total Blocking Time, a long task blamed on gsap.min.js, or "Other" eating the main thread. Most guides tell you to cut particles or add a Web Worker. Both are usually wrong. PageSpeed measures without a GPU, so the real cost is shader compilation and driver round-trips in the first frame. A script profile never shows it and a warm DevTools cache hides it. This skill is built around that one fact and tells your coding agent exactly what to do, in the right order. Inside: - SKILL.md: the principle, an 8-step sequence, a symptom to cause to move table, and the common mistakes that waste a day. - first-frame.md: the core fix with copy-ready code (compileAsync in the right render target, a 1x1 px warm-up, a fenceSync fence, the OutputPass define trap). - mobile-scaling.md: keeping the text sharp on phones, as a table of magnitudes plus a quality guard. - measuring.md: the measurement protocol (median of three, a 7-point threshold) and when to stop. - pagespeed.py: a PageSpeed Insights runner that saves results, takes the median, prints the long tasks and diffs two runs. Proven on a production build (particle text, EffectComposer, UnrealBloomPass, 14 shader programs): desktop 73 to 97, TBT 700 to 140 ms, first frame 656 ms to 3-6 ms, phone 7,000 to 72,000 particles with the desktop look untouched. Also A/B tested against an agent without the skill, which repeated five classic mistakes the skill removes. Works with Claude, Codex and any agent via MCP Market Hub. Single-seat commercial license, updates included.

主要功能

01Built on a real production rescue: desktop 73 to 97
02Fixes the real cost, shader compilation in the first frame
03A/B tested against an agent working without it
04Works on any three.js or WebGL scene, not one example
05Ships code, references and a PageSpeed measurement script
06No visual change: desktop look untouched, phone kept sharp

使用场景

01High Total Blocking Time from a particle or bloom scene
02A long PageSpeed task blamed on gsap.min.js
03"Other" dominating the main-thread breakdown
04PageSpeed score jumping up and down between runs
05Scene sharp on desktop but blurry on phone
06Directing a coding agent (Claude Code, Codex) to fix WebGL performance