How are our hosts travelling with uptime this week from Asia Pacific?
Uptime Test – Week 41 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?
WordPress Hosts
Identical Live Sites
Weekly Tests
WordPress Host #1: SiteGround
WordPress Host #2: A2 Hosting
A sample of the Uptime Status (Over 6 pages in total):
WordPress Host #3: GoDaddy
WordPress Host #4: DreamHost
WordPress Host #5: InMotion Hosting
A sample of the Uptime Status (Over 3 pages in total):
WordPress Host #6: HostGator
WordPress Host #7: Bluehost
WordPress Host #8: Web Hosting Hub
A sample of the Uptime Status (Over 2 pages in total):
Uptime Test – Week 41 Summary Table
Our hosts have recorded an average uptime performance this week, with 4 hosts achieving the ultimate goal of 100% Uptime (3 hosts achieved 100% in Week 40):
- GoDaddy
- Bluehost
- SiteGround
- HostGator
Unfortunately, A2 Hosting’s extremely poor uptime results have continued. This week they were once again over 2 hours of downtime from 79 separate outages. This now makes it over 24 hours of downtime in the last 7 weeks of testing. Due to no solutions coming through from A2 Hosting support, I have decided to stop including A2 Hosting as one of our 8 hosts, with a replacement to be announced next week.
The poor performance of Web Hosting Hub & InMotion Hosting are both related to scheduled maintenance, with emails sent in advance.
And our winner this week is GoDaddy, recording the fastest time of 842ms. The last time we ran this Asia Pacific test (in Week 35 with CloudFlare and WP Super Cache), GoDaddy’s time was slightly quicker at 730ms.
Checking in on the overall performance of changing from CloudFlare & WP Super Cache, the average response time across our 8 hosts in Week 35 was 1,736ms, while this week with all optimizations removed it is understandably slower at 2,012ms.
This is the third and final week of our No Optimizations Speed Study. I will package up the results and see how much of a difference we see between 2016 & 2017?
Next week, the Uptime Test will be run from North America. With the removal of A2 Hosting and no maintenance announced so far, hopefully we will see a drastic improvement in uptime?
For the 7th Week in a Row,
the Winner is…
Uptime Rankings
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.
Hi, I'm Clint!
