01
One project, deployed everywhere
One reference repository goes to every host in the comparison, at the same commit, with the same lockfile and the same content. No host will get a hand-tuned build.
Method
The rules were fixed before the first run.
Publishing the method after the numbers lets you quietly pick the method that produced the numbers you wanted. So this page went up first, and it is the standard every figure on this site has to clear.
02
Cold and warm stay separate
First byte after a cache purge and first byte on a warm edge are different products. Both will be published as two numbers, never averaged into one.
03
No run, no number
A figure may only be published together with the command that produced it, the date it was run, and the raw output. Anything I cannot show the log for stays off the page.
04
Prices are read off the checkout page
Plan pricing will be read from the provider's own pricing page and printed with the date it was read. Introductory rates and renewal rates count as two separate numbers.
What will not appear here
Three things you will never find here.
A review of something I have not run
A host that has not been deployed to sits in the queue with the status queued and nothing else attached to it. No paragraph of impressions assembled out of other people’s reviews.
A single blended score
Rolling latency, price, and support into one number out of ten hides the trade-off you came here to make. Each dimension gets reported on its own so you can weigh them for the project in front of you.
A ranking that moves with the commission
Several of the hosts in the queue run referral programs, and the rates differ widely between them. None has been joined yet. When one is, the ordering in every comparison will still come from the published run, whichever way that cuts against what pays best.