How Ad Networks Can Satisfy Top Client Concerns with HTTPS
October 31, 2014 | David Henzel
If you read our previous blog post on how to move your website to HTTPS you will know that Ad Networks are actually a problem when you are trying to move to full HTTPS support. For an unknown reason lots of Ad Networks still do not support the delivery of their banner ads via HTTPS. Although with the pressure from Google and the HTTPS boost in SEO ranks forced some of them to start moving and finally release support for secure connections.
Some companies might still be hesitant because they believe that its a headache to move to HTTPS or that it costs too much. And its true with some CDNs that charge extra for every SSL related step and can take weeks to process your tickets. But not at MaxCDN, SSL installation is completely automated and we do not charge for HTTPS traffic. Switching over is easy and fast with MaxCDN.
The problem that a lot of Ad Networks do is to strictly focus on revenue and the business side and ignore that they are a third-party content provider that heavily affects thousands of websites that use them to show ads.
What most ad networks do is to provide their users a js code to add to their website which then will load the actual banner. The good news is that this is the easiest thing to optimize and increase the loading performance, but the bad news is that not all companies do that. Its a serious bottleneck for websites that are really focusing on their web speed and performance.
Integrating the CDN’s API allows you to automate everything, from purging files after changing something to pulling reporting data and using it in your own control panel. By doing so you can also save a lot of money that were previously invested into infrastructure to support the millions of hits that the servers were processing.
Now lets see what happens when an Ad network does not support HTTPS. If a website owner makes his website HTTPS accessible and switches all URLs in his website to a schemeless variant (//example.com/ad.js) then all ads on his website will simply stop working. Thats because the browser will now use the https protocol to load all ads and since the ad provider does not support it and will result in timeouts.
Now if the website owner continues to use the HTTP urls provided by the Ad network then it will result in browser warnings for all users that visit his website because his website is now not 100% secure as its loading non-encrypted content. At this point the website owner is losing money and will most probably switch to an Ad Network that fully supports HTTPS to match his website. This results in a lost client for the company and a turndown for lots of other potential clients.
Its really a no-brainer, every single company needs to support HTTPS. And if they are using a CDN as mentioned above then on top of that its very easy. To enable HTTPS on MaxCDN all you need to do is to press one button. We even provide a free SNI SSL solution to promote security to smaller websites. The only negative thing about it is that its not 100% supported in older browsers and devices. Our Dedicated IP SSL provides 100% compatibility for all users and its what we suggest all Ad Networks and other big companies to use.