Smart Page Cleanup: Cookie Banners & Popups (2026)

SuperchargePerformance separates cookie banner handling from cosmetic cleanup. Auto-Reject Cookie Banners is its own toggle and ships on by default. Smart Page Cleanup is a separate, opt-in toggle for CSS-based ad hiding and popup blocking.

Auto-Reject Cookie Banners

Cookie consent banners fire before you can interact with a page. SuperchargePerformance uses the AutoConsent library to detect them and dismiss them by selecting the reject/decline path — not accept. The banner disappears. No click required, and no configuration needed — the feature is on from the moment you install.

AutoConsent supports hundreds of consent management platforms. Banners that use non-standard implementations may not be detected. In those cases the banner remains and you can click manually as usual.

Smart Page Cleanup

Smart Page Cleanup is off by default — CSS injection can occasionally leave empty layout gaps where an ad slot used to sit, so the toggle is opt-in. It adds two behaviors when enabled:

Cosmetic Ad Hiding

Some ad slots survive network-level blocking. The ad network’s domain gets blocked, but the container div stays on the page — an empty box where an ad would have loaded. Cosmetic rules target those containers with CSS and collapse them.

These are CSS injections, not DOM removals. The page structure stays intact; the empty containers are hidden. Page functionality is unaffected.

Popup Blocking

Unsolicited popups come from window.open() calls triggered by page scripts rather than user actions. Smart Page Cleanup intercepts those calls and drops the popup before the browser opens a new window.

Popups that follow a direct user click — OAuth flows, download dialogs, payment processor windows — are allowed through. The distinction is whether the window.open() traces back to a genuine user gesture within a 2-second window.

When to Adjust These

Auto-Reject Cookie Banners and Smart Page Cleanup are controlled independently. If a site’s cookie preferences need to persist (say, a subscription site you’ve already logged into), add that domain to the whitelist instead of disabling the feature globally.