I'd take a look at uMatrix, which is easier and more granular than NoScript (but lacks the more in-depth security features). It allows you to block/allow cookies, css, images, plugins, scripts, frames, and more on local/remote host basis.

For example, when visiting example.com you could allow scripts from example.com but not from gstatic.com, analyticshost.com, or shadylookingdomain.com. Yet at domain.com you could allow gstatic.com scripts and images because it embeds Google Maps.

It's all done in an amazing, quick GUI that provides a visualization of the rules. I wish all firewalls would adopt the UI.

NoScript is a pain to use and configure. And you need to finely tune it. With this profile method, you can have a "all-in" profile, and a "safe" one. This makes things much easier to manager.

1. install it. and close the annoying tab.

2. visit a site, click the noscript icon

3. allow the domains you trust.

no step 4.

how is this hard?

you only have to click the icon again if some site is not working.

> you only have to click the icon again if some site is not working.

And then you start realizing that blocking all scripts is a pain. You want just this script to work, but not this one. So you start filtering and it takes so much time.

Then often, a site is not working exactly right, and you don't know no-script screw you. Sometime you realize it after 10 minutes looking for something no-script removed. Waste of time. Then you for some time you want it one for a site, then off for the same site. And on. And off. And you have 30 tabs, then you have to jungle with the state of it.