NVMe against SATA SSD: what it actually changes for your site
Every host now says NVMe. It is a real advantage and it is routinely described in a way that promises more than it delivers, so here is where the difference shows up and where it does not.
What is actually different
A SATA SSD speaks a protocol designed for spinning disks. It has one command queue, 32 commands deep, and it is capped at around 600 MB/s by the interface itself. An NVMe drive is attached to PCIe and speaks a protocol designed for flash: thousands of queues, thousands of commands each.
The headline number people quote is sequential throughput - several gigabytes a second against 600 megabytes. That number is close to irrelevant for a web server, because web servers almost never read a large file sequentially.
The number that matters is latency under concurrency. A busy site produces many small, random reads at once: a page load might touch a hundred database pages and two hundred small files. A SATA SSD serialises those behind one shallow queue. NVMe does not. That is the real win, and it grows with load rather than showing up on an idle benchmark.
Where you will notice it
- Database-heavy pages. WooCommerce category pages with filters, dashboards, reporting screens - anything doing many small reads per request.
- Busy hours. On an idle server the two are close. At fifty concurrent requests the SATA queue is the bottleneck and the NVMe one is not.
- Backups and restores, which do move large files and finish appreciably sooner.
- Shared hosting in general, because you are sharing the disk with every other account on the machine. Deeper queues mean less waiting behind a neighbour.
Where you will not
- A page served from cache. If the answer is already in memory the disk is not consulted at all. Caching beats any drive upgrade.
- A slow query. A missing index makes the database read a million rows instead of ten. Doing that faster is not the fix.
- Anything bound by distance. If your server is on another continent, disk latency is a rounding error next to network latency.
The honest summary
NVMe is a real improvement and it costs us little to provide, which is why it is standard across our shared, WordPress and VPS plans rather than an upsell. But if a site is slow, the order to look in is: caching, then queries, then server location, then storage. Storage is rarely the largest number on the page, and a host that leads with NVMe rather than with any of the other three is telling you what it would prefer you compared.
