Quick guide: popup user interface
Pages 112
- Home
- 2014 07 22: µBlock and others: Blocking ads, trackers, malwares
- About "This other extension reports more stuff blocked!"
- About that CSS selector with "www.faceporn.net" in it...
- About the required permissions
- About this "your software" mindset
- Advanced settings
- Advanced user features
- Badware risks
- Behind the scene network requests
- Block more, way more
- Blocking mode
- Blocking mode: easy mode
- Blocking mode: hard mode
- Blocking mode: medium mode
- Blocking mode: nightmare mode
- Blocking mode: very easy mode
- Can you trust uBlock?
- Change log
- Cloud storage
- Compare: Memory footprint: what happens inside µBlock after installation
- Contributed memory usage: benchmarks over time
- Cosmetic filtering in µBlock: version 0.4.0.0 update
- Counterarguments
- Dashboard
- Dashboard: 3rd party filters
- Dashboard: Settings
- Dashboard: Whitelist
- Deploying uBlock Origin
- Disable hyperlink auditing beacon
- Does uBlock block ads or just hide them?
- Does µBlock block ads or just hide them?
- Does µBlock blocks ads or just hide them?
- Doesn't uBlock Origin add overhead to page load?
- DOM inspector
- Dynamic filtering
- Dynamic filtering examples
- Dynamic filtering (obsolete, need revision)
- Dynamic filtering: Benefits of blocking 3rd party iframe tags
- Dynamic filtering: Benefits of blocking 3rd party script and iframe tags
- Dynamic filtering: default deny
- Dynamic filtering: default deny: useful rulesets
- Dynamic filtering: disabling cosmetic filtering for the current site
- Dynamic filtering: Examples of usefulness of blocking 3rd party iframe tags
- Dynamic filtering: precedence
- Dynamic filtering: quick guide
- Dynamic filtering: rule syntax
- Dynamic filtering: to easily reduce privacy exposure
- Dynamic filtering: turn off uBlock everywhere
- Dynamic filtering: turn off uBlock everywhere except
- Dynamic filtering: turn off µBlock everywhere
- Dynamic filtering: Usefulness of blocking 1st party script tags
- Dynamic filtering: Usefulness of blocking inline script tags
- Dynamic URL filtering
- Element picker
- Experimental features
- Experimental filters
- FAQ
- Filter list licenses
- Filter lists from around the web
- Filter lists: gorhill
- Filter syntax extensions
- Firefox version: benchmarking memory footprint
- Firefox version: benchmarking memory footprint (2015 03 07)
- How to ...
- How to whitelist a web site
- Inline script tag filtering
- Launch and filter lists load performance
- Maintainership transfer of uBlock: post mortem
- Manually editing per site switches
- Memory footprint: what happens inside uBlock after installation
- Memory footprint: what happens inside µBlock after installation
- My answers to web store reviews where appropriate
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: µBlock consumes over 80MB
- Myth: µBlock is just slightly less resource intensive than Adblock Plus
- Notes on media coverage of uBlock Origin
- Notes on memory benchmarks, selfies
- Overview of uBlock's network filtering engine
- Overview of uBlock's network filtering engine: details
- Own memory usage: benchmarks over time
- Per site switches
- Prevent WebRTC from leaking local IP address
- Privacy policy
- Privacy stuff
- Procedural cosmetic filters
- Quick guide: popup user interface
- Reference benchmark
- Regular expression based filters
- Software known to have uninstalled uBlock Origin
- Static filter syntax
- Strict blocking
- Technical inaccuracies from around the web
- The logger
- The network request logger
- Tips and tricks waterfall
- Tools
- Tricks and tips
- Troubleshooting
- Tutorial: how to unbreak a site using the dynamic filtering pane
- uBlock and others: Blocking ads, trackers, malwares
- uBlock vs. ABP: efficiency compared
- Various videos showing side by side comparison of the load speed of complex sites
- What uBlock can and can not (currently) do
- What µBlock can and can not (currently) do
- Who care about efficiency, I have 8 GB and|or a quad core CPU
- Who cares about efficiency, I have 8 GB and|or a quad core CPU
- Why don't you accept donations?
- µBlock and others: Blocking ads, trackers, malwares
- µBlock version 0.8.5: many changes
- µBlock vs. ABP: efficiency compared
- Show 97 more pages…
- The title bar
- The large power button
- The number of requests blocked
- The number of domains connected
- The site-based switches
This is uBlock's popup UI when you click on uBlock's icon in the toolbar:

The title bar

Click the title bar of the popup to go to uBlock's dashboard.
The large power button

Click the large power button to turn off uBlock for the current site (a.k.a. whitelist the current site). This will be remembered the next time you visit the site.
Alternatively, you can also Ctrl-click to turn off uBlock only for the current page (command ⌘-click on Mac).
For more advanced whitelisting control, see "How to whitelist a web site".
The number of requests blocked

This shows the number of network requests uBlock blocked on the current page. Also, less useful (but people like this kind of thing), the number of network requests uBlock blocked since you installed it. The percentage figure tells you how many requests were blocked out of all the requests made.
Click the eye-dropper icon to enter element picker mode, which allows you to create a filter by interactively picking an element on a page, thus permanently removing it from the page.
Click the list icon to open the network request logger in a separate tab. This allows you to inspect real-time network traffic within the browser.
The number of domains connected

The number of distinct domains with which a network connection was established, out of all connections (established + blocked). The domains are derived using the official Public Suffix List.
In general, it must be assumed that each distinct domain is managed by a distinct administrative authority. In practice, it is not uncommon to have a multiple distinct domains which are under the same administrative authority (example 1: google.com, ajax.googleapis.com and gstatic.com, example 2: wikipedia.org and wikimedia.org).
That said, this statistic may be seen this way: the more distinct domains your browser connects to, the greater the privacy exposure.
In a best-case scenario, the number of distinct domains to which a web page connects should be only one: that of the remote server from which the web page was fetched.
The higher the number, the higher you are exposing yourself privacy-wise.
There is a good correlation between the domains connected count and: unneeded page bloat, high privacy exposure, increased likelihood of being the target of data mining.
Example: the web page on http://www.ibtimes.com/ (which can be read fine in all cases, by the way):
| uBlock's mode | turned off | default settings | default-deny |
|---|---|---|---|
| domains connected | ![]() |
![]() |
![]() |
| privacy exposure | very high | medium | very low |
| bloat | ridiculously high | medium | very low |
And I had click-to-play enabled in all cases, so it could have been worse (except for default-deny)...
The site-based switches

The per-site switches allow you to control some settings on a per-site basis. See detailed documentation about per-site switches.



