Does NVMe make shared hosting faster?
About a third of the shared hosting plans in the catalog list NVMe drives: that's around 2,400 plans from more than 500 hosts. Prices start under half a dollar a month, and the median is roughly $7 — even slightly below the median for the market as a whole. NVMe is no longer a premium option, and you don't need to pay extra for it. But it's important to understand how much it actually speeds up a site on a shared server.
NVMe, SATA SSD and HDD: what's the difference
- HDD — a mechanical drive with millisecond access times and a hundred or two random operations per second. It's long been obsolete for hosting database-driven sites and survives mostly on archive and very cheap plans.
- SATA SSD — a solid-state drive on an older interface. Sequential reads top out at around 550 MB/s, with tens of thousands of random operations per second. That's enough for most websites.
- NVMe connects directly to the PCIe bus. Sequential reads reach several gigabytes per second and random operations hundreds of thousands, but most importantly, latency is lower and it handles parallel requests better.
On a shared server that last point matters more than record gigabytes per second: one drive serves hundreds of sites at once, and NVMe copes with that load better without building up a request queue.
What really makes a site fast
How quickly a page is served on shared hosting depends on several factors, and the disk isn't always the main one.
- PHP processes and CPU limits. Every request to a dynamic page takes up a PHP process. If the plan allows, say, 10 concurrent processes and a fraction of a core, requests start queuing during traffic spikes, and NVMe won't help.
- Caching. A page cache (a WordPress plugin, the CMS's built-in cache, LiteSpeed Cache on LiteSpeed servers) serves ready-made HTML without running PHP or querying the database. The gain is many times over — far more than swapping the disk.
- OPcache and PHP version. A current PHP 8.x with OPcache enabled is noticeably faster than older 7.x releases.
- The database. This is where NVMe really shows: large tables, slow unindexed queries, search and catalog filters all benefit from fast random reads.
- Server overcrowding. If the host packs too many accounts onto one machine, no disk will save you from slowness.
Bottom line: NVMe noticeably speeds up online stores, forums, sites with large databases, and CMS admin panels where there's a lot of reading and writing. For a landing page or a well-cached blog, the difference from a SATA SSD will be barely noticeable.
How to check that the disk really is NVMe
Shared hosting gives you no access to the hardware, so you can only verify the host's claim indirectly.
- See whether the drive model or server configuration is listed in the host's plan description or knowledge base. Reputable hosts don't hide such details.
- If the plan includes SSH, run a simple write and read test with dd, or fio if it's installed. Hundreds of megabytes per second or more on sequential writes is a good sign; single or double digits is a reason to ask support. Keep in mind that the host may cap disk speed per account (an I/O limit), and the test will show exactly that limit.
- Look for the I/O limit in the plan description or the control panel (on CloudLinux it's shown in the resource usage section). A 1–2 MB/s limit cancels out any advantage of NVMe.
- Check the server response time (TTFB) for a test page that queries the database, comparing two or three plans during a trial. Hosts with a free trial are collected in our hosting with a free trial selection.
How to measure the effect of moving
If you're moving an existing site from an old plan to NVMe, measure the speed before and after rather than relying on gut feeling. Compare server response time (TTFB) on the same pages: the home page, a catalog or search page, and the admin panel. Take several measurements at different times of day, and always with the page cache disabled — otherwise you'll be measuring the cache, not the disk. If the TTFB of an uncached page dropped from, say, 800 to 400 ms, the move was worth it. If it barely changed, the bottleneck is PHP, CPU or database queries, and it's time to optimize the site itself.
What else to look for in NVMe plans
The median disk size in this selection is 25 GB, slightly more than across the catalog as a whole. About half of plans offer unmetered traffic. The cheapest NVMe plans give you only 0.5–1 GB, so if you're choosing on price, check the disk size carefully. If your site is already hitting CPU and process limits on shared hosting, moving to an NVMe plan won't fix it: in that case consider a VPS for WordPress or another VPS with dedicated resources. To compare other parameters, go back to the main web hosting table.