How are our hosts handling altitude this week in Asia Pacific?
Uptime Test – Week 50 Method
- Compare 8 WordPress Hosts
- Use 8 Live Sites, each with a Different Host but with Identical Content (you can check them out here)
- Use Pingdom Uptime Test
- Location of Test: 10 Asia Pacific Locations
- Frequency of Testing: Every Minute across the Last 7 Days
- Number of Weekly Tests = 1 x60 x24 x7 x8 = 80,640 (xMinutes xHours xDays xSites)
- Uptime testing is confirming that the website is actually accessible to visitors
- An example of why an outage (or downtime) can occur is scheduled maintenance of the server the website is hosted on
Which WordPress Hosts can ace the uptime test this week?
Identical Live Sites
Uptime Test – Week 50 Summary Table
Our hosts have recorded a very poor uptime performance this week, with just 1 host achieving the ultimate goal of 100% Uptime (3 hosts achieved 100% in Week 49):
And our winner this week is obviously GoDaddy, being the only host to achieve 100% uptime as well as recording the fastest time of 908ms. The last time we ran this Asia Pacific test (in Week 47 with EWWW), GoDaddy’s time was slightly faster at 849ms.
Checking in on the overall performance of changing from EWWW to Kraken, the average response time across our 8 hosts in Week 47 was 2,410ms, while this week it has slowed to 2,551ms. Note: If we ignore the extremely poor performance of DreamHost (now the 6th week in a row and will be given one last chance or will be replaced by another host), the average response time is 1,983ms for EWWW and 1,943ms for Kraken.
This is the third and final week of our Kraken Speed Study and its been a fairly close contest between EWWW & Kraken. I will summarize these results to find out who has come out on top.
Next week we will be setting up the final Image Optimization plugin, then we’ll be able to declare the overall best performer!!
And for the 4th Week in a Row
the Winner is…
After 9 months of testing, let’s summarize all the results to see how our 8 hosts are performing overall. It will also allow us to find out which host is currently leading our uptime challenge.