Outbrain is an advertisment (simular content) script, Disqus is a commenting system (known for having holes in it’s security). optimizely is a site analytics tool to measure server load on client side (live preview of inbound traffic as well). qauntserve is a statics module (often used with the default jetpack analytics module). and adobetm is connected to the Adobe Marketing Cloud (statics with a digital tag)
New info, Oliver, coming up, good you assist with this research…
I could not resist to run the alerted extension SPOF-O-Matic results against the online Tracker Tracker,
see these results attached, widgets, trackers, ads. Do not open links given there in a browser - all info just just for research purposes. The only resource that did not was ssets.adobedtm.com, but alerted for another reason.
See this: https://www.mywot.com/en/scorecard/assets.adobedtm.com?utm_source=addon&utm_content=popup
Where the WOT page is also a Possible Frontend SPOF from:
Look at the scripts, stylesheets, and font files in your web page from a worst case scenario perspective. Ask yourself:
Is your web site’s availability dependent on these resources?
Is it possible that if one of these resources timed out, users would be blocked from seeing your site?
Are any of these single point of failure resources from a third party?
Would you rather embed resources in a way that avoids making them a frontend SPOF?
Make sure you’re aware of your frontend SPOFs, track their availability and latency closely, and embed them in your page in a non-blocking way whenever possible.
Combine these resources: SPOF-O-Matic extension for Google Chrome, online Tracker Tracker (do not forget to update): https://tools.digitalmethods.net/beta/trackerTracker/ and http://www.cookiechecker.nl/ or similar.
Found at first sight that Google Ad tracking code and JQuery code could be the cause of most front-end SPOFs, example
(72%) - <script type=“text/javascript” src="htxps://apis.google.com/js/plusone.js
