NoScript is configured by default to only allow scripts and "active content" to run from domains you allow. You can temporarily allow certain domains, or perman

NoScript is configured by default to only allow scripts and "active content" to run from domains you allow. You can temporarily allow certain domains, or permanently allow them. So yes, it does address the CDN issue. If someone includes a script from apis.google.com, that script won't run until I permit content from that domain to run (and I only ever do that temporarily, and only if the site needs it). Likewise for any other domain: CDN, analytics, whatever. I don't know much about Ghostery - NoScript addresses most of my privacy concerns around web browsing.