Private local benchmark

Ad blocker test lab.

Test the blocker you already trust with one calm scan. It checks ad scripts, tracker pixels, analytics services, cosmetic hiding rules, and host-level blocking signals.

1 Pick a scan

Quick, Standard, or Deep.

2 Let it probe

Everything runs in your browser.

3 Fix open rows

Use categories to tune your blocker.

What this checks

Choosing an ad blocker and need a clean place to compare it? Run the same scan against SimplyAdBlocker, AdBlock, AdBlock Plus, AdGuard, Ghostery, uBlock Origin, AdBlocker Ultimate, or another blocker you use.

Advertising scripts Tracker pixels Analytics services Cosmetic filters
Score under 90/100?

Open the rows that slipped through, check the category, then try SimplyAdBlocker for a quieter setup with no accounts and no telemetry.

Improve your score with SimplyAdBlocker
01

Compare one blocker at a time. Multiple blockers can overlap and make the score less reliable.

02

Refresh cleanly. If old results stay visible, do a hard refresh with cache cleared before running again.

View results

A Deep scan starts 5 seconds after first load. Results stay in your browser.

Results

Live scan details.

Blocked means your blocker caught it Open means the request or bait got through Warning means the signal timed out or was unclear
01

Cosmetic filters

Static and dynamic ad-shaped boxes show whether your blocker hides empty ad spaces.

02

Scripts and pixels

Local baits and third-party probes check ad scripts, analytics, social pixels, and error monitors.

03

Host signals

DNS-style reachability checks help spot common ad and tracking hosts that still answer.

Cosmetic bait zone

Harmless traps used by the scan.

If these boxes disappear, cosmetic filtering is doing its job.

Tracker pixel
Dynamic ad

Plain answers

How to read the score.

Why can a test say “open” even when my blocker works?

Some domains allow simple image or fetch probes while still blocking real ad behavior. Treat the score as a practical snapshot, then inspect the detailed rows.

Does this page upload my results?

No. The checks run locally and results are rendered in your browser. This site does not include third-party analytics.

Can this prove DNS blocking?

No browser page can universally inspect your DNS resolver. We test whether known ad and tracking endpoints fail from the page, which is a useful but imperfect signal.

Why do DNS apps and browser extensions sometimes score differently?

They block at different layers. DNS tools can stop whole hosts, while extensions can hide page elements and block script paths. Running several blockers together can also create false positives.