Ad and tracker blocking applied before the request leaves
Short answer
About 141,000 EasyList and EasyPrivacy rules are applied before a request is sent, rather than hiding elements after they have loaded.
The problem it exists for
A news front page can spend nine seconds loading adverts and one second loading the article, and a blocker that hides elements afterwards has already fetched them.
How it works
- Requests are matched against the filter lists and dropped before they go out.
- Lists refresh every three days, which is one of only two network calls Nightjar makes on its own.
- On Yahoo's front page this measured 9,633 ms down to 1,093 ms.
What it does not do
- Those load-time figures predate the current filtering engine and have not been rerun.
- Controls moved 2.0% and 4.8%, which is roughly the noise floor — so a 6.6% result is not a result.
- Filter lists have false positives, and occasionally a site needs blocking turned off to work.
- Playback wins: when an advert shares a host with the video, the advert is let through rather than risk the video not playing.
Other ways people ask this
- browser built-in ad and tracker blocking
- browser with built in ad blocker windows