Performance, uptime & infrastructure
How this is scored
What runs the sites and how reliably: CPU, RAM and storage per tariff stated, SSD or NVMe storage, current PHP versions and how long old ones are kept, HTTP/2 or HTTP/3, server-side caching (OPcache, Redis, a page cache), a CDN, databases and their limits, resources that are guaranteed rather than shared without a stated limit, an uptime SLA with a service credit, a public status page with incident history, and redundancy of the platform. Where the data centre is located is scored under sovereignty.
0 — Not a hosting product; websites or web apps cannot be run on it.
3 — Storage and a number of sites per tariff are stated and the product is described as fast; resources, PHP versions, caching and uptime are basic or not described.
5 — Resources per tariff stated (CPU or a performance class, RAM, SSD or NVMe storage), several current PHP versions selectable, HTTP/2, server-side caching or a cache plugin documented, free SSL, a stated uptime target, and a public status page.
8 — Dedicated or guaranteed resources stated per tariff, HTTP/3 and a CDN included, Redis or an object cache, PHP versions kept current with an end-of-life policy published, an uptime SLA with a service credit, a status page with incident history, and a redundant platform (replicated storage, failover) described.
10 — Infrastructure documented to the level an operator could audit: hardware generations and storage architecture named, performance measured and published with method, an SLA with credits and exclusions at 99.95 % or above, every incident on the status page with a post-mortem, and scaling without downtime documented.
The Shop Operator
I can read the tariff specs before buying: the plans state NVMe storage from 100 to 500 GB, RAM from 6 to 20 GB, one vCPU and the number of databases, plus HTTP/2, free SSL, a 99.99 % uptime figure described as guaranteed, geo-redundant replicated storage, Tier IV data centres and a public status page that lists incidents. What I could not find for my Black Friday planning is any word of a page cache, Redis or an object cache, HTTP/3 or a CDN on the web hosting tariffs, or an uptime SLA that pays a service credit when the shop is down. PHP stays patchable through a paid extended support programme, which softens that gap a little. 1 2 4 5 8