Size still matters for Advertisers
August 2nd, 2010 by Tim WintleOver the past few years, the size of websites has increased dramatically – driven partly by advertiser demand for shinier creatives, partly by a new generation of web designers who have never focused on file size, and partly by increased broadband penetration.
File size is very important.There used to be a rule of thumb that if your website didn’t load within three seconds then the user would probably leave your website – and I believe that rule still holds. For publishers, that means you are losing out on ad revenue (and visitors) by serving large file sizes.
Even if a viewer does stay on the website, a slow page can irritate the user – which can impact negatively on the brand who’s adverts are being shown.
Not only that, but many people pay for data by the Mb / Gb (especially mobile users) – sending your users larger data than they need costs them real money, and puts them off websites and advertisers.
File size is being overlooked though. If you’re from an ad agency or a publisher, you are probably willing (and able) to pay for high-speed internet access. Website viewers, the people being advertised to, aren’t always in the same situation though.
As an example, I just opened up the website of a popular web publisher, and noticed the page (including ads) was over 8mb in size.
Here’s how long that website would take to load on a user’s computer, depending on what internet connection the user is on:
- 8 seconds (10Mbps broadband – you’re probably on this)
- 45 seconds (2Mbps broadband – most of your users are probably on approximately this speed)
- 3 minutes 7 seconds (500Kbps broadband – quite a few of your users are probably on this)
- 40 minutes (56Kbps modem – you’d be surprised how many are still on this)
Of course, people don’t just browse from their homes and offices – users browse from mobile phones and from mobile broadband.
Although mobile broadband can have very fast speeds (8Mbps), this speed goes down very fast if you’re on the move. Travelling on the train this weekend, I recorded my average broadband speed at about 120Kbps. For the page above, it takes about 20 minutes to load the page.
Here in the UK, up to 50% of users have mobile broadband – which means that 50% of viewers to this site may be have to wait 20 minutes for a page before your ads load.
The situation gets worse in other countries. For example, in Australia the average speed is far lower. If you’re serving ads world-wide, you should be aware that they’re probably taking far longer to load in Australia than they are to users in the USA or UK.
So that’s the bad news about the industry in general, but here’s what we at the Viral Ad Network are doing about the issue:
How the Viral Ad Network reduces Ad size:
For all ads, we are able to do the following
- We serve the majority of data through compressed protocols (See RFC 2616 – section 3.5)
- All of our standard javascripts are made as compact as possible, using the most advanced javascript analysis tools available.
- We only load our standard code when it’s required.
- We split our ad serving into two parts – the part that’s the same for every ad, and the part that varies depending on which ad is being served. We tell browsers and proxies cache the former as much as possible (including across different websites), and only load the latter each time an ad is displayed.
- Most Ethernet implementations have a MTU of approximately 1492 bytes. We endeavour to fit our initial ad code into a single TCP packet (we currently serve roughly 870 bytes of initial javascript).
In addition, for ad creatives which we have control over, we do the following:
- For data feeds loaded from servers, we provide server-side rewriting that compacts the data as much as possible (and compresses it).
- For images, we re-compress the images to reduce file size (Note re-compression is also a necessary precaution for security)
- For video players we produce ourselves, we sometimes in-line any images into the swf. This reduces the number of requests that have to be made for the data.
- We try to post-load data from the server whenever possible. This means the code required by the ad often doesn’t load until after the website and ads have loaded, and the user starts interacting with an ad.


