# Embed Request: Option to NOT Load Google Analytics or Other Unnecessary Scripts in the Embedded iFrame JS **URL:** \ **Category:** Feature\ **Created:** [November 8, 2017, 1:27pm UTC](https://meta.discourse.org/t/embed-request-option-to-not-load-google-analytics-or-other-unnecessary-scripts-in-the-embedded-iframe-js/73687 "2017-11-08T13:27:04Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![Berto](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/berto/32/77084_2.png) [@Berto](https://meta.discourse.org/u/Berto)\ **Post date:** [November 8, 2017, 1:27pm UTC](https://meta.discourse.org/t/embed-request-option-to-not-load-google-analytics-or-other-unnecessary-scripts-in-the-embedded-iframe-js/73687/1 "2017-11-08T13:27:04Z")
Continuing the discussion from [Embedding Discourse Comments via Javascript](https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963/236), I noticed that when embedding my Discourse Forum (which has been configured with Google Analytics via the Admin fields) into my Blog as blog comments, it was loading Google Analytics JS files twice – once from the blog’s calls, once from the Embed’s calls. This then added more resources to be downloaded on the calling site, and could double your statistics across your entire business. There should be an option to _not_ load Analytics and potentially any other unnecessary scripts to save bandwidth/requests on the site embedding Discourse. Embed should be more bare bones IMHO. The current workaround is to stop using the official Google Analytics options and just put the call into your forum’s head. Then it’s not called in the embed. --- _[View the full topic](https://meta.discourse.org/t/embed-request-option-to-not-load-google-analytics-or-other-unnecessary-scripts-in-the-embedded-iframe-js/73687)._