#437 CSS effects on swamp.club (any page) cause high CPU

Hi! I'm interesting in swamp and trying to read the documentation. Unfortunately, I'm finding that any page on swamp.club is causing my laptop's CPU fans to cut on. When I investigate my performance monitoring tools, it's very clear that many of my CPUs become very active whenever a swamp.club tab is active. I had Codex analyze the situation with Playwright and it confirmed my hunch that there were issues with the CSS effects. Below is the summary and data that Codex was able to provide.

Bug Report: High CPU Usage On swamp.club Homepage Summary Opening https://swamp.club/ causes sustained high Chromium CPU usage. The evidence points primarily to continuous CSS animations, especially the fixed full-screen .noise-overlay, not specifically to the chromatic aberration title effect. Evidence Collected Test environment: Chromium headless via Playwright, viewport 1440x900. Page structure:

• 0 canvas elements
• 0 video elements
• 0 images
• 7 active CSS-animated elements on the homepage
• No console errors observed Active animations included:
• .noise-overlay → noise
• main title → glitch, rgb-split
• duplicate title layer → glitch-skew
• subtitle → text-corrupt
• counter → counter-glow-pulse
• label → flicker
• command text → typing, blink-caret CPU measurements over 12-15 second windows: Condition Avg CPU, one-core equivalent Baseline ~312-315% Disable chromatic/glitch title only ~315-319% Disable text shadows only ~313% Disable noise overlay only ~58% Disable non-title animations only ~42% Disable all CSS animations ~4-5% Diagnosis The chromatic aberration effect is real and CSS-based: layered text, magenta/cyan text-shadow, rgb-split, glitch, and glitch-skew keyframes. However, disabling only that title effect did not reduce CPU. Disabling .noise-overlay dropped CPU from ~312% to 58%, and disabling all CSS animations dropped it to 5%. Most likely hotspot: .noise-overlay, a fixed full-screen element using an inline SVG feTurbulence noise texture and animation: .5s steps(10,end) infinite noise. Suggested Fix Start by disabling or replacing .noise-overlay. If visual noise is required, prefer a static pre-rendered texture or a much less frequent update. Also consider honoring prefers-reduced-motion for all continuous decorative animations.