We're hiring!

Magento Hosting Performance Study

Before reading further, please set your preferred response time

Set your preferred response time and we will add your personal preference to the charts throughout this study.

How fast should a website respond?

Results Overview

We have measured the time you have to wait before the browser starts rendering the webpage. This is the time everyone has to wait before any other optimisations come in play.  It does not matter how the front-end is optimised – smaller images, aggregating css and javascript, reducing domain name lookups – this waiting time applies to everyone.

The user experience is what matters for conversion, and we use the following reference values when we measure and evaluate the Time to First Byte:

  • Average Response time less than 0.8 seconds generally gives good performance
  • Average Response time over 0.8 seconds gives stores a somewhat sluggish feeling
  • Average Response time over 1.2 seconds feels sluggish, and risks that people start double-clicking
  • Average Response time over 1.5 seconds suggests annoyed and struggling visitors
  • Anything over 2 seconds guarantees a poor user experience

How to read and analyse this diagram

  • The red response time bars show the response time most visitors will experience
  • Only the first four sites have acceptable and consistent average response times below 0.8 seconds
  • The blue response time bars may occur for visitors during heavy traffic events, hitting the full page cache
  • Response times less than a second for Full Page Cache Tests indicate effective use of Full Page Caching for Scaling (FPC Test response times less than 0.5 seconds should not be compared because network latency is the main source of variation)
  • Large absolute differences between the initial run and the confirmation runs suggest that performance randomly varies (Hellyhansen.com, Eplehuset.no, Hoyer.no)

Some extra info on the three Servebolt-hosted sites: YMEUniverse.com, Coverbrands.no and KariTraa.com

  • None of these use REDIS or any other alternative caching backends
  • Coverbrands.no delivers the second best response times, and does not use full page caching. It is proven to scale to more than 2000 simultaneous users without a cluster setup
  • KariTraa.com runs on PHP 5.6. Upgrading the site to PHP 7 would slice of another 35-50% of the average response time

Enklereliv.no is the only non-Servebolt site that delivers super performance in this test. The numbers, and our from-the-outside inspection of the setup suggests that their full page cache is primed at all times.

Chance of Poor Performance

The following graph includes all sites were more than 3.5% of pages on average respond in more than 2 seconds. Site visitors usually visit more than 1 page, but this graph displays the chance per click of hitting a page 2 second+ page.