Also just for some info on what I meant before in terms of this not really effecting page load: https://gtmetrix.com/faq.html#faq-fully-loaded-vs-onload
They support both tests and clearly state that not everything they show in their reports is loaded during “page load”, this includes stuff up to 30 seconds past the time the page actually finishes loading. This is pretty much the same way Pingdom handles their scans.
What that means is that anything after onload is not always a true effector for your page load. They had to change it to include those extra things for stuff like JS based sliders that load after the page finishes. Which is not the case here. Ours is not loading any content so though it gets reported it is technically not part of nor increasing the page load, its just getting scanned in their comprehensive reports.
That said that doesn’t prevent it from hitting your server. So if your doing 10k users a day and tracking their popup opens you would have 10k hits to your site beyond what missed your cache. The new option to disable will work in those cases. If your simply concerned about the page load reports, then its arbitrary and just something to annoy us all, myself included. This also applies to things like social buttons that don’t load until after the page stops loading to prevent them from slowing down your users ability to start interacting with your site.
That said we have sites with millions of monthly views and complex load balanced setups using the plugin and built in analytics without issue. So I haven’t actually seen any reports where these hits actually are causing server issues. Hope this new options takes care of that for anybody that may experience that in the future though.
I am closing this since the new version is minutes away.
Please take a moment to click that it Works and to rate and review the plugin or support.