Newsner handles millions of requests from one day to another. By having a social media-dependent content setup one post can generate millions of hits. This required a special and robust setup with an edge caching service.


Massive loading times decreased visibility on Facebook

The problem Newsner was facing was that increased loading time would mean a smaller impact on Facebook as Facebook’s engine took into account of loading time, 50x errors etc. If the engine noticed that something was not right, meaning slow response time or likewise) it meant that the article would struggle to get the full spread through the whole network it potentially could have.

With their current setup with having one server in Sweden, a post that got to be spread in the United States would most likely result in the above problem.

We were brought in to fix this, the first problem we saw was that their platform was Wordpress whom which is not known for fast response times, speed and good at handling hundreds of requests per second.

This was unless there was a cache in place. And we are not talking about the full-featured cache plugins for Wordpress. Those didn’t do the job as the requests still hit the origin server.

We needed a shield that was in front of the origin and which resulted in Edge-Cache.


By using Amazon Cloudfront we could achieve the above where more than 99% of the traffic is between End User and Edge Cache node. Amazon have edge cache nodes all over the world which makes them a good candidate when it comes to scale on a global level.

Our final solution worked as show below.


During a period of 2 years we served more than 1 000 000 000 visits with above setup.