We Challenged Our Page Speed Against 13 Top Web Hosts

We are WordPress designers and developers who wanted a web hosting platform optimized for page speed.

We tried many of the other hosts in the early days and decided on creating our own supersonic hosting server based on our knowledge and experience.

Certainly, our results would appear to vindicate that we know how to optimize for page speed.  Read the reviews below.

If you're looking for a fast loading WordPress or Woocommerce driven website you should consider Browserweb . If you have any questions, feel free to ask.



May 2019

1.   |    1.2sBrowserweb
2.   |    1.8sSiteground
3.   |   3.5sInMotion
4.   |  3.8siPage
5.   |  4.4sPressable
6.   |  4.7sBlueHost
7.   |  5.1sPantheon
8.      |     6.6sLiquidweb
9.      |    8.8sDreamHost
10.   |    9.1sFlywheel
11.   |   11.2sGoDaddy
12.   |   12.8sA2 Hosting
13.   |   15.4sMediaTemple
14.   |  19.8sWPEngine

Desktop Speed Review Report (May. 2019)

WP Engine


MAY 2019

Download Report
Media Temple


MAY 2019

5.7s with Grade D. Where's Buddha?

Download Report
A2 Hosting


MAY 2019

3.4s with a page grade B. Still a wanna be but making improvements. Can't seem to get past the #3SECONDS barrier.



MAY 2019

6.0s with a page grade E. New design, still a depressing speed means it's still a no-go in our book.

Download Report


MAY 2019

16.5s with a page grade F. The FlyWheel is still very broken.

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

Download Report


MAY 2019

1.2s with a page grade A. The same position every month, #1.

Download Report

Summary of Speed Results for December 2018

Top 8 Hosts Page Speed Review Report (Archives)



We're #1, so we tested more Hosts (archives)

What You Should Look for When Testing Page Speed

The test location closest to your target audience provides the most accurate representation of your page load.

Don’t compare these tools equally and wonder why your scores differ from tool to tool.

Onload time may misrepresent the true load time of your page.

Real browsers provide a better indication of your website’s performance.

It’s important to understand how each tool works before relying on them for any sort of data or results.


Which Page Speed Testing tool should you rely upon or use?

It depends. We feel that the use cases for each tool can be broken down into the following categories:

Quick Checks

GTmetrix, Pingdom Tools, and PageSpeed Insights


Consistency/Historical Tracking

GTmetrix and WebPagetest


In-depth Analysis

GTmetrix and WebPagetest


SEO Check

PageSpeed Insights, GTmetrix, and Pingdom Tools


Mobile Devices

WebPagetest, GTmetrix, and PageSpeed Insights


Location Dependent

WebPagetest, GTmetrix, and Pingdom Tools


Advanced Options

WebPagetest and GTmetrix


Pingdom defaults to Onload Time only

This is why you may see Pingdom results loading faster than GTmetrix and/or WebPagetest.



Fully Loaded Time vs Onload Time

Fully Loaded Time

The point after the Onload event fires and there has been no network activity for 2 seconds. This ensures more consistency with tests.

Possible issues with using this event: This event fires only when a page completely stops loading content, including ads and below the fold elements. Your site might have loaded fast above the fold and be usable, however since the analysis is now waiting for the entire site to stop loading data, your reported Page Load Time might be longer.


Onload Time

When the processing of the page is complete and all the resources on the page (images, CSS, etc.) have finished downloading. The browser will trigger window.onload when this occurs.

Issues with using this event: Some elements of the page load may not make it in before this event fires – like JavaScript based image carousels – causing inconsistent page load times and inaccurate screenshots. It may also report faster page load times than actual.


Onload time may misrepresent the true load time

Due to network variances or the way the page was designed to load (eg. asynchronous loading), resources loaded after the browser triggered window.Onload may not make it into reports.

The result is a report that indicates the page loaded faster than it actually did. This means that the while the tool received a “page finished loading” trigger at onload, the actual user is still experiencing resources being downloaded.

Our preferred testing platform, GTmetrix now uses fully loaded time, which waits for 2 seconds of network inactivity before stopping the test.


The Other Platforms

GTmetrix and WebPagetest allow you to switch between Fully Loaded and Onload Time.

Pingdom defaults to Onload Time only.

This is why you may see Pingdom results loading faster than GTmetrix and/or WebPagetest.

Scores and Recommendations

Recommendations will differ between tools

Each of these tools assess websites against their own set of recommendations.

Most of them stem from Google’s original open source PageSpeed library, and have likely been customized or modified.

GTmetrix in particular has modified PageSpeed and YSlow rules to assess websites based on what they feel are the most important metrics.


Don’t compare these tools equally and wonder why your scores differ from tool to tool

While they’re all likely based on the original, open-sourced Google PageSpeed library, some key differences should be pointed out.

After Google made general scoring algorithm/recommendation changes years ago, they have not updated the open-sourced library since.

The PageSpeed Insights online tool as a whole seems to contain a new set of rules (which isn’t open-source).

Don’t compare these tools equally and wonder why your scores differ from tool to tool; they all use different recommendation sets.

This is why you’ll see differing rules from each service, and why GTMextrix deemed it necessary to update their own PageSpeed rule set.