NVMe Hosting
Plenty of hosting plans advertise NVMe storage. If you run a WordPress site, the real question is what that does for your visitors. This article explains what NVMe is, where it helps and where it doesn't, and how to check whether your hosting is the bottleneck.
The short version
NVMe is a way of connecting an SSD to a server that handles far more simultaneous commands than SATA. On a WordPress site it helps most with pages that don't come from the cache, such as a shopping cart, a search query or a logged-in account. A site that is already well cached gets barely faster. Caching, a current PHP version and a server close to your visitors usually do more for load time than the type of disk.
What is NVMe?
NVMe (Non-Volatile Memory Express) is the protocol a server uses to move data to and from an SSD. The first version of the specification came out on March 1, 2011, so it isn't new anymore. An NVMe drive talks to the rest of the server over PCI Express. When a hosting company runs its servers on NVMe storage, that's NVMe hosting. A regular SSD connects over SATA, an interface designed for spinning hard drives.
What is the difference between NVMe, a SATA SSD and a hard drive?
An SSD has no moving parts, so it reaches its data faster than a hard drive. Between two SSDs, the connection makes the difference. SATA at 6 Gb/s tops out around 600 MB/s in theory, and SATA SSDs stay just under that: a Micron 5400 for data centers reads up to 540 MB/s. With NVMe, speed depends on the generation of PCI Express (PCIe):
- PCIe 3.0 with four lanes (x4) delivers about 4 GB/s.
- PCIe 4.0, from 2017, gives 2 GB/s per lane. A Samsung PM9A3 for servers uses four lanes and reads up to 6,800 MB/s.
- PCIe 5.0, from 2019, doubles that to 4 GB/s per lane.
Those are maximums for the connection or for one type of server drive. A website rarely sees them.
NVMe is also built differently. SATA has a single queue of 32 commands, enough for hard drives but too few to get the most out of flash memory, according to the organization behind NVMe. NVMe supports up to 64K queues with 64K commands each (roughly 65,000), and every application or thread can have its own queue. That comes from the NVM Express overview. These are commands that can be open at the same time, not requests per second.
What does NVMe do for a WordPress site?
Visitors notice your server first in the TTFB, the time until the first byte of the page arrives. According to web.dev, 0.8 seconds or less is good. That time adds up from the quality of the hosting, the distance to the visitor, processing time on the server (including database queries), redirects and what is or isn't cached.
An NVMe drive shortens the part where the server waits on storage. How big that part is depends on what comes from memory and cache. A MySQL database with enough RAM reads data from disk once and serves it from memory after that. A page from the page cache goes to the visitor as ready-made HTML, without PHP building it again. Pages that differ per visitor, such as those for logged-in users, don't belong in a page cache, according to the WordPress Hosting Handbook. PHP builds those every time, just like a page that isn't cached yet. The server then queries the database, and any data not yet in memory comes from disk. That's when disk speed counts.
Measurement data from DebugHawk, a monitoring service for WordPress, shows how sites with and without caching compare. In the fourth quarter of 2025 it collected 5.7 million page views from sites using its service. Cached pages had a median TTFB of 106 ms, uncached pages 723 ms. Sites with a persistent object cache had a median PHP execution time of 508 ms, without one 1,542 ms. These are observations from one service's customers: they show a correlation and don't prove a cause.
What else makes your site faster
Which PHP version should you run?
OPcache keeps precompiled PHP code in memory, so PHP doesn't have to re-read every script on each request. The PHP version itself matters less than you might expect: in a Kinsta test with WordPress 6.8 and no plugins, PHP 8.5 handled about 148 requests per second and PHP 7.4 about 139, a difference of roughly 7 percent. You run a newer version mainly for support. According to php.net, PHP 8.2 and 8.3 now get security updates only. For 8.2 that ends on December 31, 2026, just over eleven weeks from now, and for 8.3 on December 31, 2027. If you're still on 8.2, plan the upgrade now. PHP 8.4 gets them until December 31, 2028, and PHP 8.5 (released on November 20, 2025) until December 31, 2029. WordPress.org recommends PHP 8.3 or higher.
How do distance and a CDN help?
If your visitors are far from the server, they feel it in the TTFB. A CDN (Content Delivery Network) puts your content closer to them. The WordPress Hosting Handbook does warn that a CDN without a page cache on the edge servers can raise the TTFB.
What happens after the first byte arrives?
Web.dev suggests that about 40 percent of the time to LCP should go to the TTFB. The rest is loading and rendering the largest element, usually an image or a block of text. INP, which measures how quickly a page responds to a click or tap, depends mostly on what the browser is doing, such as JavaScript on the main thread. A faster disk on the server doesn't fix that.
Does speed matter for Google?
The three Core Web Vitals are LCP (loading, good at 2.5 seconds or faster), INP (responsiveness, 200 milliseconds or faster) and CLS (layout shift, 0.1 or lower), measured at the 75th percentile of page visits. INP replaced First Input Delay (FID) on March 12, 2024, web.dev wrote that day.
Google uses Core Web Vitals in its ranking systems. According to Google Search Central's documentation, no single signal decides everything, and relevant content still comes first, even when the page experience is mediocre. A good score doesn't guarantee a high position.
AdWords has been called Google Ads since July 24, 2018. Your landing page counts toward Quality Score, which Google describes as how relevant and useful the page is to someone who clicks your ad. Load speed isn't part of that description. Elsewhere in the Google Ads help, Google does advise improving landing page speed to get more out of mobile ads. It doesn't say that faster storage lowers your advertising costs.
Is your hosting really the bottleneck? How to measure it
Before you switch hosts, check where the time goes. It takes fifteen minutes.
- Test a few pages in PageSpeed Insights and look at the TTFB. Test at least the homepage, an article and a page that isn't cached, such as the shopping cart or a search result.
- Compare the results. If the TTFB is good on cached pages and high on uncached ones, the problem is in PHP, the database or storage. If it's high everywhere, look at the server or the distance first.
- Open the Core Web Vitals report in Search Console to see real visitors. It uses field data and shows whether the problems affect many pages at once.
- Check that a page cache is active. Without one, WordPress rebuilds every page on every visit, and that explains a slow site more often than the type of disk.
What to look for when choosing hosting
Storage is one feature of WordPress hosting. This table lines up the main ones.
| Feature | What it does | What to ask or check |
|---|---|---|
| Storage (NVMe or SATA SSD) | Sets how fast data comes off the disk when it isn't in memory | Which type of storage is installed and whether you share disk space with other customers |
| Server-level page cache | Serves ready-made HTML without running PHP | Which cache is available, how you clear it and whether WordPress plugins work with it |
| Object cache | Keeps database queries in memory | Whether a persistent object cache is available, for example Redis |
| Server location | Sets the distance to your visitors | Which country the data center is in and whether a CDN is included |
A plan with NVMe and no server-side cache can be slower than an SSD plan with a good cache. Compare all the features.
What can you do today?
Start by measuring, which costs nothing. Then turn on the measures that don't require a move: a page cache, an object cache if your host offers one, a current PHP version and smaller images. If the TTFB is still high on uncached pages after that, NVMe storage or more powerful hosting is a logical next step. Have your theme and plugins audited too, because a slow plugin is slow on any disk. We do that as part of our work on websites.
Our NVMe hosting
NVMe hosting is web hosting on NVMe hardware, in our case combined with LiteSpeed technology. LiteSpeed is a web server with a built-in page cache (LSCache), which you connect to WordPress with a plugin.
You'll find an overview of our WordPress hosting on our NVMe hosting plans page. If you have a question, get in touch: during office hours we reply within 18 minutes on average.
Frequently asked questions
Is NVMe hosting faster than SSD hosting?
The storage itself is: NVMe reads and writes faster and handles more commands at once than a SATA SSD. Your site only gets noticeably faster if pages regularly have to read from disk, for example with logged-in visitors or an online shop. With cached pages the difference is small.
What is TTFB and what is a good value?
TTFB is the time between requesting a page and the first byte coming back. According to web.dev, 0.8 seconds or less is good. It adds up from server quality, distance, processing time, redirects and caching, so the disk is only one part of it.
Which PHP version should my website use?
PHP 8.3 or higher, according to WordPress.org. PHP 8.2 stops getting security updates after December 31, 2026, so plan the upgrade now. PHP 8.4 and 8.5 are supported for longer. Test a new version on a copy of your site first, because older plugins can break.
Does my WordPress site need NVMe?
Usually not as a first step. A site with a page cache, current PHP and light images performs well on an SSD too. NVMe pays off with lots of dynamic pages, such as an online shop with many simultaneous visitors.
