19 Ways to Guarantee Website Uptime on Black Friday

Black Friday

Make sure you don’t inadvertently close up shop on Black Friday

The predicted £1bn sales figure for Black Friday has made website availability and performance a board level concern for online retailers, with preparations for this year’s event starting as soon as last year’s ended for some. At Intechnica we have been working alongside several leading UK retailers to help them be fully prepared for whatever Black Friday brings.

Without revealing all of our methods, we’ve compiled a quick checklist of things retailers should have done to plan and prepare for Black Friday, along with some last minute checks and actions they might still be able to consider. How many have you thought about and do you feel fully prepared?

Planning – In the lead up to Black Friday

  1. Assign an owner and team dedicated fully to the specific task of preparing the website for Black Friday.
  2. Agree on the budget – performance doesn’t come for free. How much is uptime and speedy response times worth to the business on Black Friday? (We can help you figure this out!)
  3. Find out how much traffic is expected and its nature. Work closely with the marketing department to find these out based on planned activity along with overall trends. This information should include baseline traffic levels, the size of peaks, how fast they are expected to hit, where the traffic is likely to come from and how users are expected to behave on the site.
  4. Measure how much traffic the site can handle and where the bottlenecks are through thorough performance testing and analysis.
  5. Validate that your test results make sense and are realistic!
  6. Identify existing means to scale up the website’s capacity, e.g. capacity planning, cloud hosting, failover capacity, disaster recovery etc.
  7. Optimise performance in quick development sprints, focusing on low hanging fruit and test the results regularly.
  8. Move hits away from the domain using CDNs etc.
  9. Reduce the size of traffic hits, e.g. optimise image sizes, minify JavaScript etc.
  10. Cache content as close to the browser as possible, e.g. on a webserver rather than in the database.

Preparation – Last minute checks

  1. Ask “what could possibly go wrong?”
  2. Ask what the impact of such failures would be.
  3. Ask how you would know if such a failure was about to occur or in progress.
  4. Ask what could be done to mitigate this!

On the day

  1. Make a list of non-essential functionality that could be quickly switched off to boost performance if the site is struggling, e.g. predictive site search, live chat, etc.
  2. Empower team members to be able to deal with problems quickly without needing to wade through red tape.
  3. Make sure monitoring is in place and running (real user monitoring, business metrics, social media etc.).
  4. Know who you can contact in a pinch within the business and with third parties – have a list of numbers and emails at the ready.
  5. Have an insurance policy in place in case all else fails.

What if all else does fail?

Many top retailers suffered very public failures last Black Friday, with sites crashing under much higher demand than anticipated. Fortunately we have developed TrafficDefender, an insurance policy for if websites do reach bursting point come Black Friday.

TrafficDefender removes the risk of complete website outages if capacity can’t keep up with demand, and gives a better experience to any overflow of visitors than a generic error message by placing excess visitors into an orderly queue.

Even if you have followed our checklist from top to bottom, do you have an insurance policy for if all else fails?


How much damage does Third Party Content really do to ecommerce sites? [REPORT]

thirdpartyreportIntechnica recently did some in-depth research into how the performance of ecommerce (specifically fashion retail) websites is being affected by the over-proliferation of third party content, the results of which have been published in our brand new report, “The Impact of Third Party Content on Retail Web Performance”.

For the uninitiated, third party content refers to basically anything on your website served externally – usually adverts, tracking tags, analytics codes, social buttons and so forth. Check here and here for some good background on the dangers of third party content.

If you are already initiated, though, you will already know that this content places an overhead on a website’s performance to varying degrees. In a best case scenario you’re looking at some extra page weight in the form of objects, which are being served from added hosts via extra connections to your users, the result being a few extra milliseconds on your page load time. On the other end of the spectrum, a misbehaving piece of third party content can slow pages to a crawl or even knock your site offline. Remember when everyone blamed Facebook for taking sites like the Huffington Post, Soundcloud and CNN down? Yep. Third party content at its most disruptive.

So what did we want to find out?

We wanted to really see how much of an impact third party content was having on real websites. We went about this by doing some external performance monitoring of the normal websites in parallel with filtering out the third party content (which we identified based on experience – if you want to see an open source, ever-growing list of third party content, I recommend It’s also important to note that we measured a “land and search” transactional journey, not just home page response, to get a more realistic measurement. From this information, we were able to distinguish which kinds of content are most prevalent and even what element of this content was most to blame for any performance overhead. It also gave us some interesting insights into whether sites that use third party content more conservatively also happen to follow other web performance best practices.

Some fast facts

There is more detailed data in the report itself, which is available to download in full here. However, let’s look at some key findings. Keep in mind that some of these might seem predictable but it’s nice to have some concrete data, isn’t it?

  1. In general, sites that use more third party content are heavier, use more hosts and connections, and are slower than those that use less third party content.
  2. When third party content is completely filtered out, websites with a lot to begin with see a greater immediate speed boost than those with less to begin with. In fact, many retailers swapped places in the rankings once third party content was taken out of the equation.
  3. Falling in line with the famous “golden rule of web performance”, it’s the extra hosts, connections and objects brought on by third party content that result in slower response times – more so, in fact, than page weight.

Some pretty graphs and tables

I recently saw someone on Twitter express the rule “nt;dr” (no table; didn’t read), so let’s get some data in this post, shall we?


The chart above shows the average number of each type of third party content present on each of our target websites. As you can see, there is far more variation in adverts than in any other form of third party content, although it’s somewhat surprising to see the average of 1.8 analytic tags on these websites. Serving adverts etc. from multiple hosts impacts performance, as we see in the table below…


Our second table tells us a little more about why sites with more third party content tend to be slower. The median, maximum and minimum response, hosts ,connections, objects and size represent only what is added to the sites by third party content, not the overall metrics. We can see that third party content alone is adding up to 18.7 seconds to the response time (a median of 9.4 seconds). What’s also interesting is that there is a stronger correlation between average response time and number of objects, connections and hosts added than there is between response time and added page weight (0 is no correlation ,1 is absolute correlation).


The last chart I’ll show you here is very telling in terms of real impact of third party content. Red and blue are the full, normally served websites of Retailer A and Retailer B respectively. We can see that red is much slower than blue during this time period. Yellow and green are the same websites (A and B respectively) except with all third party content removed. Not only did Retailer A gain a greater speed boost than Retailer B by filtering this content out, but it actually went from being the slower website to being the faster of the two. What’s even more interesting is that Retailer A reported disappointing revenues of this period, while Retailer B posted a strong revenue report.

Read the full report

This is just a sample of some of the data we collected and analysed, so make the jump to our website to read the full report for yourself.