Home / server / Questions / 221678
In Process
Zach Smith
Asked: 2011-01-13 09:52:49 +0800 CST

Reducing Loading of Advertisers Scripts

  • 772

I have a website (http://dev2.liquor.com) that loads very quickly when I remove the advertisers and tracking scripts our partners give us. Of course we need to reduce page load time from 6 seconds to 1 second, and I see that it is 100% all of our external js files for partner tracking, ads, etc.

I have been banging my head against the wall trying to find alternate ways to load/compress/serve the multitude of js the user needs to download. I can easily compress/minify mine, but someone else's that is not on our server is becoming hard to do so.

The best I can do is get a C on YSlow, and each suggestion they give me pertains to my stupid tracking js scripts!

I think the main problem is the tracking (http://pastebin.com/faMDGrrs) which I can see in the status bar is causing the site to load very long. Thoughts on how to deal with that?

Is it even possible to manage third party scripts in my website?

Any help would be greatly appreciated.

web-server page-speed

2 Answers

  1. Here's some client-side JS I threw together (based upon the Google Analytics asynchronous tracking snippet) which would allow you to load external Javascripts asynchronously:

    <script type="text/javascript">
  (function() {
    var scripts = new Array(
        'external.domain.com/script1.js',
        'external.domain.com/script2.js',
        '../script1.js',
        './script2.js',
        '/script3.js'
    );
    if ( scripts.length )
    {
        for ( var i = 0; i < scripts.length; i++ )
        {
            var asynchronous = document.createElement('script');
            asynchronous.type = 'text/javascript';
            asynchronous.async = true;
            if (
                scripts[i].substring(0, 1) != '/' &&
                scripts[i].substring(0, 1) != '.'
            ) {
                // assume external domain (enforce protocol)
                asynchronous.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + scripts[i];
            } else {
                // assume relative URI
                asynchronous.src = scripts[i];
            }
            var s = document.getElementsByTagName('script')[0];
            s.parentNode.insertBefore(asynchronous, s);
        }
    }
  })();
</script>
    • 1

  2. Putting third party scripts into an iframe could be an alternative.

    Common sense is that an iframe has a high cost (in terms of load), but if it's cost is less then the cost of loading third party elements, you could give it a try.

    You probably you did most of things that are discribed here, but it's a good resource anyway.

    • 0