The Anideo Dev Blog

com.anideo.dev

The Anideo Dev Blog

We are building Denso.

How moving to Amazon Cloudfront increased our App Store conversion rate by 250%

30 Dec 2011 - Singapore

So as you may know, we’ve been working on Denso for a while now, and our primary source of marketing (after the initial wave of PR via Eduardo) has been our website. We post interesting videos once in a while to Hacker News, Reddit, Twitter and Facebook, thus generating inbound traffic.

The Hacker News story about Jon Stewart’s takedown of scammy iOS games generated a record number of visits to getdenso.com, but unfortunately, that number didn’t correlate well with the App Store downloads for that period. What we noticed was that our site appeared slow (even though New Relic indicated that our website stood up quite well against the onslaught) - and the reason was that our static assets (Javascript and CSS) were taking too long to load and would occasionally even 504.

This, was obviously, unacceptable.

We researched a bunch of ways on how we can improve the speed of the site, and naturally Amazon Cloudfront ranked very high among our options. But we needed a way for it not to interfere with our existing deployment strategy (which is git push heroku master). We chanced upon this excellent resource which basically gives a detailed tutorial on setting up a custom origin server on CloudFront. With Heroku, its not as straightforward as the Open Government tutorial makes it out to be - there will be another blog post coming up on the tweaks that we implemented.

Before and After

We switched over to our shiny new CDN solution on the 16th of December.

Before the 16th, our App-Store-downloads-to-web-visits ratio was hovering around 6-8%

After the CDN deployment, our App-Store-downloads-to-web-visits ratio is now a healthier 21-28%.

Moral Of the Story

Obviously the moral of the story is not for everyone to move over to a CDN. A lot of other iOS app downloads are probably not driven by their web cousins, so it won’t always make sense for you to optimize web performance.

Our biggest takeway is - run experiments, follow up on performance, try to find out root causes for weaknesses, and ruthlessly tackle them.

blog comments powered by Disqus