Script Blocker — Block Third-Party Scripts

Script Control blocks JavaScript files loaded from external domains — the widgets, analytics libraries, and tracking beacons that often make up a large share of a page’s load weight. By stopping these scripts before they execute, pages parse faster, the main thread stays less congested, and you reduce exposure to third-party code you never agreed to run.

How It Works

When your browser loads a page, it frequently fetches JavaScript from dozens of domains other than the site you are visiting. Script Control uses Chrome’s declarativeNetRequest API with three static rulesets to intercept script requests that originate from third-party domains.

The rulesets are layered — each higher level activates the rules from the level below plus an additional set targeting a broader category of third-party scripts. The extension evaluates requests at the network layer before they download, so blocked scripts never execute and never consume CPU time parsing or running.

Settings

The default is Trackers. This blocks analytics and tracking without touching anything visible on the page. Move up to Embeds if you want embedded widgets blocked too and don’t mind them breaking.

When to Use This

• Pages feel slow to become interactive even on a fast connection — third-party scripts often block the main thread during parse
• You want to reduce CPU usage on pages with many embedded widgets or analytics tools
• You are on a shared or throttled connection and want to minimize unnecessary downloads
• You use PRO and want the most aggressive script reduction

Pair Script Control with Ad Blocking for layered coverage: ad blocking removes known tracker domains, script control removes the broader third-party script surface.

Privacy

Script Control operates entirely locally using static rules bundled with the extension. No page content, script URLs, or browsing data is transmitted to any server. All rule matching happens inside Chrome on your device.