Editor's note: If you work for a web hosting company and are interested in working with Review Signal on projects like this, make sure you're subscribed to our Web Hosting Company Newsletter.

SIGNUPS END DECEMBER 23, 2021(<--SIGNUP HERE)

I’m starting to prepare for WPHPB 2022 and that means I need to do the following:

Collect feedback from last year’s tests – improvements/changes/problems?
Get signups from companies

Feedback?

Please share any feedback from last years test you might have. These benchmarks continue to evolve as the industry does. Your feedback, suggestions, criticisms and ideas help keep these benchmarks meaningful.

I launched WPHostingBenchmarks.com last year as a stand alone site for these benchmarks. Any feedback about the tests and the presentation are always appreciated.

Load Storm is shutting down and I will be moving all load testing to k6. There will still be two tests focusing on cached performance and uncached performance. The cached performance will stay the same (this already used k6). The uncached performance will be written entirely in k6 to closely replicate what the Load Storm test did. Logging in and browsing as a logged in user for the WordPress benchmark. For the WooCommerce it will replicate popular user behaviors such as checkout flow, browsing products, viewing account/orders. I'm open to feedback on this and listening to suggestions. Since this will be entirely new and can't be compared backwards to Load Storm, it's an opportunity to revamp or tweak the tests in ways that might make more sense. So any suggestions/ideas are appreciated.

Send email feedback to kevin at reviewsignal.com.

Participation Details:

Please read the WordPress Methodology and WooCommerce Methodology for each test you're interested in participating.

You can read about the whole process at the links above.

2022 Testing will follow a similar process (unless there is some critical feedback necessitating a major change which will be communicated before testing begins).

Changes:

Load Storm is deprecated and will be replaced by k6. The tests will be approximate replications in terms of endpoints being tested.

WPPerformanceTester will need an update in some of the functions and possibly database wrappers.

Possible Changes:

Removing Internet.nl and Mozilla Observatory scores. Are they worth having?

Participation Fees / Price Tiers

Hosting Plan Monthly Price ($)	Participation Fee
<25	$100.00
25-50	$100.00
51-100	$150.00
101-200	$200.00
201-500	$250.00
Enterprise	$500.00
WooCommerce	$250.00

Re-testing fee: 50% of the participation fee per test after 2nd test. eg. 1 extra test for the 51-100/month price tier will cost $75 ($150 * 50%) per test.

These fees cover the costs associated with running these tests. The prices scale up because larger plans require more resources. Re-testing fees are to re-do a load test because something went wrong (namely security issues interfering with getting an accurate measurement). Two tests are included for all participants. There is no limitation to the number of re-tests as long as there is a legitimate reason (poor performance isn’t a legitimate reason). However, the tests need to be finished within the testing time period to allow ample time for analysis and publication.

If you’re concerned about security measures blocking tests, I am willing to work with you to schedule the tests to make the best effort possible to bypass security issues. You are responsible for making sure the tests run cleanly, I can help to some extent, but ultimately I cannot guarantee a clean test through your security measures - only you can.

Requirements and Understanding:

Accounts will be provided for free for the duration of testing (approximately 4 months from setup)
It is the responsibility of the hosting company to turn off and disable accounts after testing is finished. If there is any doubt, once results are published, testing can be considered over under all circumstances.
Company will assign representative(s) who are responsible and available to answer questions and deal with issues that arise during testing.
Tests are run on DEFAULT configurations (except Enterprise tier which allows unlimited customization). This means changes and improvements that aren’t on by default or a simple click away in an obvious place (eg. wp-admin or customer panel homepage or welcome email) aren’t allowed. If a user needs to click ‘enable caching’ and you tell them this, this is acceptable. If they have to go download a caching plugin and install it themselves, this is not acceptable. If you have a specific question about your service please ask beforehand.
Once tests are run, results will be published. There is no opting out because of poor or incomplete results.