Interactive checklist
WebGL scene health check
Score a Three.js scene before publishing. The checklist focuses on the failure modes that make WebGL pages feel unfinished: invisible models, broken camera framing, heavy assets, weak loading states, and mobile performance surprises.
How to read the score
A high score does not mean the scene is visually finished. It means the technical surface is less likely to break under real page conditions. Use the result as a publishing gate before you add more polish.
Scores below 55 usually mean the scene still has structural risk. Scores between 55 and 79 are workable but need mobile and loading checks. Scores at 80 or above are ready for design review, copy review, and real-device testing.
8 min read · mobile
Three.js mobile performance checklist
Mobile WebGL quality comes from budgets: fewer pixels, fewer surprises, and graceful fallbacks.
7 min read · debugging
Three.js scene debugging checklist when nothing appears
A blank canvas is easier to fix when you test renderer, camera, geometry, material, lights, and animation in order.
8 min read · performance
A practical Three.js performance budget for small sites
Performance gets easier when each scene has a budget before it has polish.