Browserweb’s Mobile First Speed League


We are WordPress designers and developers who wanted a web hosting platform optimized for fast mobile-first designed websites.

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

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

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

May 21, 2019

1.   |    7.1sBrowserweb
2.   |   12.2sMedia Temple
3.   |   13.5sA2 Hosting
4.   |  14.2sLiquidweb
5.   |   14.3siPage
6.   |  14.6sInMotion
7.   |  17.7sBlueHost
8.      |   18.2sSiteground
9.      |  19.6sDreamhost
10.   |    20.5sWPEngine
11.   |   20.6sGoDaddy
12.   |   22.0sPantheon
13.   |   33.5sFlywheel
14.   |   failed testPressable



MAY 2019

Failed test. GTMetrix could not crawl due to consistent timeout error.




MAY 2019

33.5s. The FlyWheel is still very broken in 2019.





MAY 2019

Drops from 10th to 12th in the league. 22.0s with a page grade F.



MAY 2019

20.6s and  still one of the slowest. Slow Daddy dot com.


WP Engine


MAY 2019

20.5s with a page grade F. And still an expensive digital experience to forget.




MAY 2019

19.6s dropping from #2 in 2018 to #9 in 2019. Clearly the new website design is not fast enough. Keep on Dreaming...




MAY 2019

18.2s they've at least addressed the major issues but the speed is still not acceptable for a mobile website in 2019.


Browserweb's Technology Stack



MAY 2019

17.7s still feeling the blues, even with a recent website upgrade.


InMotion Hosting



MAY 2019

14.6s with no motion evident.





MAY 2019

14.3s - coming in at number 5 in 2019




MAY 2019

14.2s. Up to number 4 in 2019.

A2 Hosting



MAY 2019

13.5s with a page grade of D.

Media Temple



MAY 2019

12.2s and up to #2 in 2019, but with an E Grade from GTMetrix.



MAY 2019

7.1s in 2019, shaving more time off our 2018 speeds and still not one of the competition is even near Browserweb...

We use what we sell, WordPress CMS.

We're the highest page grade and fastest mobile speed of all the competitor web hosts.

Supersonic Mobile Website Hosting from Browserweb - do more in less time and keep your visitors happy. Only at


September 2018 (Archive)

1.   |    5.9sBrowserweb
2.   |   10.4sDreamhost
3.   |   11.8sInMotion
4.   |   12.1sBlueHost
5.   |   13.8sA2 Hosting
6.   |  15.0siPage
7.   |   15.5sLiquidWeb
8.      |   16.2sSiteground
9.      |   19.2sGoDaddy
10.   |    21.6sWPEngine
11.   |   21.9sPantheon
12.   |   22.3sMediaTemple
13.   |   24.5sFlyWheel
14.   |   30.4sPressable

What You Should Look for When Testing


  • 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.