Using Firefox Enhanced Tracking Protection Strict Mode to Reduce Tracker Load

The problem: trackers slow pages and leak data

When you visit a typical news or shopping site, dozens of third‑party requests load scripts, cookies, and fingerprinting tools that you never see. These requests can add latency, consume bandwidth, and expose your browsing habits to companies you didn’t intend to share data with.

Thesis: Firefox’s Enhanced Tracking Protection (ETP) Strict mode blocks known trackers early in the request lifecycle, giving a measurable privacy boost with only a modest performance cost.

How ETP Strict works

ETP Strict relies on Disconnect’s tracker list. When Firefox starts a network request in a content process, it checks the destination domain against that list before the request is sent. If the domain is classified as a social‑media tracker, cross‑site cookie provider, or fingerprinting script, the request is cancelled locally. Because the filter runs in the content process, the blocked request never reaches the network stack, reducing data leakage and avoiding unnecessary round‑trips.

Enabling and configuring ETP Strict

1. Open about:preferences#privacy or click the shield icon in the address bar and select “Privacy & Security”.
2. Under “Enhanced Tracking Protection”, choose the Strict radio button.
3. Firefox will show a shield badge on the toolbar indicating the mode is active.
4. For sites that break, click the shield icon on that page, toggle the switch off for that site, or add an exception via “Manage Exceptions”.

Worked example: observing blocked requests on a tracker‑heavy page

1. Navigate to a known tracking‑rich site (e.g., a homepage with many social‑share buttons).

Open Developer Tools (F12) and go to the Network tab.

Enable the “Block request” filter (funnel icon → “Show blocked requests”).

Reload the page. You will see entries for domains such as facebook.com/tr, twitter.com/i/jot, or doubleclick.net marked as (canceled) or with a shield icon indicating they were blocked by ETP.

Return to the toolbar shield icon and select “Protections”. The dashboard will display a running count of blocked trackers, cookies, and fingerprinters for the current session.

This flow demonstrates that the blocking occurs before any response is received, so no data is exchanged with those domains.

Trade‑offs and limitations

• Site breakage: Some widgets (login buttons, comment systems, analytics‑dependent features) rely on the same domains that ETP blocks. When functionality fails, you must create a per‑site exception.
• List latency: The tracker list is updated periodically (approximately every 48 hours). Newly emerging trackers may not be blocked until the next refresh, so protection is not instantaneous for zero‑day threats.
• Performance variance: While internal telemetry shows an average <5 % increase in page load time, pages that rely heavily on blocked resources can experience higher latency or missing content until you add an exception.

Actionable closing

Enable ETP Strict globally for baseline protection, then use the shield icon on any problematic site to temporarily disable blocking or add a lasting exception. Periodically review the privacy dashboard to see how many trackers are being stopped and adjust exceptions as needed. This approach gives you concrete control over tracker exposure without requiring third‑party extensions.