Comments on: How I sped up page load times by 10x http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/ OpenX Community News Tue, 24 Nov 2009 12:36:32 +0000 http://wordpress.org/?v=2.6.2 By: Kyle http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-53028 Kyle Wed, 08 Oct 2008 18:17:07 +0000 http://blog.openx.org/?p=419#comment-53028 SPC may decrease the amount of HTTP requests per page, but what can be done on the logging front? Even if you've got a single page call for all banners on a page, you're still getting an HTTP request to lg.php for each banner if you have impression logging turned on.. SPC may decrease the amount of HTTP requests per page, but what can be done on the logging front? Even if you’ve got a single page call for all banners on a page, you’re still getting an HTTP request to lg.php for each banner if you have impression logging turned on..

]]> By: Chris Nutting http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-51789 Chris Nutting Mon, 29 Sep 2008 11:50:06 +0000 http://blog.openx.org/?p=419#comment-51789 @Goran - SPC makes one HTTP request in the which provides the HTML for each ad on the page whereas using iframes makes one HTTP request per ad (or in your case, 2). The code which inserts the ad into the page (OA_show(id);) does not make an HTTP request, it simply gets the HTML already returned by the SPC request and outputs it. So with 20 positions on the page, SPC makes 1 HTTP request, receives the HTML for 20 ads, and outputs them as required, with iframes, each of those 20 positions makes an HTTP request and shows the selected ad. For each ad actually shown on the page, there will be a (non-blocking, meaning that loading the rest of the page content doesn't hang while waiting for this response) beacon which counts the impression, and depending on the creative type, there may be an additional (non-blocking) call to retrieve the creative (e.g. the .gif or .swf media file). So in the scenario with 20 ads on the page, and serving only HTML/External ads: SPC: 1 (multi-ad) request + 20 beacon requests = 21 HTTP requests iframes: 20 ad requests + 20 beacon requests = 40 HTTP requests. The reason that iframes "feel" faster is that they are non-blocking. However the load on your adserver will be higher and you will lose the ability to use some of the ad-contextual features like companion positioning or "Don't show this ad again on the same page" @Goran - SPC makes one HTTP request in the which provides the HTML for each ad on the page whereas using iframes makes one HTTP request per ad (or in your case, 2).

The code which inserts the ad into the page (OA_show(id);) does not make an HTTP request, it simply gets the HTML already returned by the SPC request and outputs it.

So with 20 positions on the page, SPC makes 1 HTTP request, receives the HTML for 20 ads, and outputs them as required, with iframes, each of those 20 positions makes an HTTP request and shows the selected ad.

For each ad actually shown on the page, there will be a (non-blocking, meaning that loading the rest of the page content doesn’t hang while waiting for this response) beacon which counts the impression, and depending on the creative type, there may be an additional (non-blocking) call to retrieve the creative (e.g. the .gif or .swf media file).

So in the scenario with 20 ads on the page, and serving only HTML/External ads:
SPC: 1 (multi-ad) request + 20 beacon requests = 21 HTTP requests
iframes: 20 ad requests + 20 beacon requests = 40 HTTP requests.

The reason that iframes “feel” faster is that they are non-blocking. However the load on your adserver will be higher and you will lose the ability to use some of the ad-contextual features like companion positioning or “Don’t show this ad again on the same page”

]]> By: Goran Jurić http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-51787 Goran Jurić Mon, 29 Sep 2008 11:38:27 +0000 http://blog.openx.org/?p=419#comment-51787 Hm, It looks like my testing environment wasn't so clean as I thought it was :) I have repeated my tests, and iframe invocation does indeed need more http requests to deliver the banner. I have tested with 3 banners (2 GIFs, and 1 Flash banner): Iframe -> 12 requests Single page -> 10 requests Hm, It looks like my testing environment wasn’t so clean as I thought it was :)

I have repeated my tests, and iframe invocation does indeed need more http requests to deliver the banner.

I have tested with 3 banners (2 GIFs, and 1 Flash banner):

Iframe -> 12 requests
Single page -> 10 requests

]]> By: Goran Jurić http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-51784 Goran Jurić Mon, 29 Sep 2008 10:25:00 +0000 http://blog.openx.org/?p=419#comment-51784 If we don't take the load of the server that serves the banners (I don't really care about the load on that server, it's a separate machine that doesn't serve that many banners) I found the Single page call more demanding for the end user than the iframe invocation code for each banner. I have iframe invocation code stored in the separate html file on the server, and after the page loads fully (with images and everything), a fetch this html file using jQuery and insert it into the banner container on the site. Using this method and taking into account that I have one extra http request because I load the html file with the iframe invocation code separately there are still more http requests needed to deliver the banners using Single page call than it is to deliver the banners using this html -> iframe -> banner method. The method I am using is described in detail on my website - http://gogs.info/2008/09/optimizing-frontend-performance-with-some-javascript-magic/ . So I really don't understand how can you decrease page load times tenfold if you are actually making one or two request per banner MORE than you do with the iframe invocation code? If I missed something I would appreciate if you could elaborate on this delivery method in detail. If we don’t take the load of the server that serves the banners (I don’t really care about the load on that server, it’s a separate machine that doesn’t serve that many banners) I found the Single page call more demanding for the end user than the iframe invocation code for each banner.

I have iframe invocation code stored in the separate html file on the server, and after the page loads fully (with images and everything), a fetch this html file using jQuery and insert it into the banner container on the site.

Using this method and taking into account that I have one extra http request because I load the html file with the iframe invocation code separately there are still more http requests needed to deliver the banners using Single page call than it is to deliver the banners using this html -> iframe -> banner method.

The method I am using is described in detail on my website - http://gogs.info/2008/09/optimizing-frontend-performance-with-some-javascript-magic/ .

So I really don’t understand how can you decrease page load times tenfold if you are actually making one or two request per banner MORE than you do with the iframe invocation code?

If I missed something I would appreciate if you could elaborate on this delivery method in detail.

]]> By: Todd Morgan http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-51280 Todd Morgan Thu, 25 Sep 2008 18:34:27 +0000 http://blog.openx.org/?p=419#comment-51280 Yes Please! Yes Please!

]]> By: Rithish http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-51057 Rithish Wed, 24 Sep 2008 11:57:37 +0000 http://blog.openx.org/?p=419#comment-51057 Yes. I would definitely be interested in seeing a tutorial for using the single page call. :o) Yes. I would definitely be interested in seeing a tutorial for using the single page call. :o)

]]> By: OpenX tips by Erik Geurts http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-51031 OpenX tips by Erik Geurts Wed, 24 Sep 2008 06:44:28 +0000 http://blog.openx.org/?p=419#comment-51031 <strong>Single page call makes your site load faster...</strong> Using the newest version of OpenX, I was able to speed up a client’s website by a factor of 10. This tip describes how we used the singe page call feature of OpenX 2.6 to do this. Introducing OpenX single page call My client hired me to upgrade ... Single page call makes your site load faster…

Using the newest version of OpenX, I was able to speed up a client’s website by a factor of 10. This tip describes how we used the singe page call feature of OpenX 2.6 to do this.

Introducing OpenX single page call
My client hired me to upgrade …

]]> By: Oliver George http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-50968 Oliver George Tue, 23 Sep 2008 21:10:09 +0000 http://blog.openx.org/?p=419#comment-50968 Tell us if you you would like to see a tutorial on using this technique to show a grid of ads efficiently using single page call. Perhaps Erik will be encouraged by the interest and write one ;-) cheers, Oliver Tell us if you you would like to see a tutorial on using this technique to show a grid of ads efficiently using single page call.

Perhaps Erik will be encouraged by the interest and write one ;-)

cheers, Oliver

]]> By: Leo http://blog.openx.org/09/sped-up-page-load-times-with-a-faster-ad-tag/#comment-50967 Leo Tue, 23 Sep 2008 20:44:55 +0000 http://blog.openx.org/?p=419#comment-50967 very good news :) very good news :)

]]>