Reduce KHIX homepage memory usage
The 2026 site can reach ~1.2 GB RAM in Chrome. This appears primarily related to large decoded/composited image assets rather than a JS heap leak.
Main suspects:
faq-lennyblink-lennyblink.webp is 2667×3318, animated, priority, and unoptimized- Hero has 9 full-screen
unoptimized layers with permanent will-change: transform, plus animated pond/waterfall WebPs
- Tracks loads eight 2048×2048 character images as
unoptimized
- FAQ creates a new
AudioContext on every cave-note interaction without reusing/closing it
Potential fixes:
- Replace large animated WebPs with video
- Remove unnecessary
priority / unoptimized and serve responsive sizes
- Reduce permanent
will-change usage
- Reuse one
AudioContext
- Profile memory before/after in Chrome DevTools
Reduce KHIX homepage memory usage
The 2026 site can reach ~1.2 GB RAM in Chrome. This appears primarily related to large decoded/composited image assets rather than a JS heap leak.
Main suspects:
faq-lennyblink-lennyblink.webpis 2667×3318, animated,priority, andunoptimizedunoptimizedlayers with permanentwill-change: transform, plus animated pond/waterfall WebPsunoptimizedAudioContexton every cave-note interaction without reusing/closing itPotential fixes:
priority/unoptimizedand serve responsive sizeswill-changeusageAudioContext