diff --git "a/About-\"This-other-extension-reports-more-stuff-blocked!\".md" "b/About-\"This-other-extension-reports-more-stuff-blocked!\".md" index 8a89491..9f24f97 100644 --- "a/About-\"This-other-extension-reports-more-stuff-blocked!\".md" +++ "b/About-\"This-other-extension-reports-more-stuff-blocked!\".md" @@ -8,7 +8,7 @@ Sometimes, for the same page, one extension can report more stuff blocked than t The less a blocker blocks, the higher the number of network requests. The higher the number of network requests, the more likely some of them will need to be blocked. So sometimes you end up with more network requests blocked as shown by the badge, while internally more network requests were actually allowed for the web page. -Ultimately, for me it's the [benchmarks I run](#) to report blocking power which tells the real story. The badge is really not a good way to assess blocking power of an extension, you could well end up concluding the opposite of what is really happening. +Ultimately, for me it's the [benchmarks I run](uBlock-and-others%3A-Blocking-ads%2C-trackers%2C-malwares) to report blocking power which tells the real story. The badge is really not a good way to assess blocking power of an extension, you could well end up concluding the opposite of what is really happening. If you don't want to run a benchmark, I have this [little online tool](http://raymondhill.net/httpsb/har-parser.html) with which you can find out the requests which were **not** prevented from leaving your browser. To use it, open the dev console for the page for which you want a report, and go to the _Network_ tab. **Edit:** since then I have created [uBO-Scope](https://github.com/gorhill/uBO-Scope), an extension which purpose is to inform you about what was not blocked.