performance-auditor

Frame-rate drops stem from excessive particle counts, memory leaks, or bundle bloat. Use built-in performance monitoring and browser DevTools to measure FPS, memory growth, and rendering time. Diagnose bottlenecks by profiling particle systems, trail effects, and asset sizes against your device's 30–60 FPS adaptive target.

Yes. Implement adaptive quality that dynamically adjusts particle counts, trail lengths, and effect intensity based on detected device capabilities and real-time FPS. Deploy particle pooling and spatial partitioning to reduce physics calculations. Low-end devices run 200–400 particles at 30 FPS minimum while desktop maintains 800–1000 at 60 FPS.

Profiling and budgeting are critical. Target full bundles under 250 KB gzipped, minimal under 120 KB, and audio under 200 KB. Profile asset compression, remove unused effects, and measure trade-offs between visual fidelity and file size. Use performance monitoring to confirm 30–60 FPS delivery across desktop, mobile, and low-end platforms.

Monitor runtime memory usage over time with DevTools and built-in debug tools. Ensure memory stays under 100 MB at runtime and initial load under 50 MB. Use particle pooling to reuse objects, properly release event listeners, and validate that memory does not grow unbounded during extended playback.

No. Desktop targets 60 FPS with 800–1000 particles; mobile adapts between 30–60 FPS with 400–600 particles; low-end devices maintain 30 FPS minimum with 200–400 particles. Use adaptive quality settings and real-time performance monitoring to detect device capabilities and adjust effects, bundle size, and particle counts accordingly.