optimize-threejs-games

Frame drops in Three.js games are fixed by first profiling a repeatable scene to identify whether the bottleneck is CPU or GPU. Then apply low-risk fixes like reusing geometry and materials, pooling effects, culling offscreen work, and avoiding per-frame allocations, verifying the original scene afterward.

Reduce draw calls in Three.js by reusing shared geometry and materials, culling inactive or offscreen objects, and capping particle counts. Measure draw calls in a deterministic test scene before and after each change to confirm improvement.

A game is likely CPU-bound when simulation, allocations, pathfinding, or per-frame scans grow with actor count. It is likely GPU-bound when resolution, overdraw, shadows, transparent particles, post-processing, or texture bandwidth dominate frame time.

Yes, the workflow explicitly covers mobile performance by recording device and viewport in benchmarks, applying adaptive quality settings, and verifying mobile controls after optimization. Decorative effects should degrade before combat readability or controls.

Stuttering during combat often comes from per-frame memory allocation, unpooled particle effects, or unthrottled UI updates that spike with actor count. Pool transient effects, avoid allocations in the render loop, and update only changed transforms.