NVMe vs SSD vs HDD Hosting: Which One Actually Makes Your Site Faster?

1. HDD, SSD, NVMe — The Basics

HDD (Hard Disk Drive)

Spinning magnetic platters, mechanical read/write heads. 80–160 IOPS. Seek time 5–15 ms. Cheap per gigabyte but slow for random reads. Used in archival storage and some legacy cheap hosting.

SATA SSD

Flash memory over the SATA bus (max 550 MB/s sequential). 80,000–100,000 IOPS random read. Most "SSD hosting" from 2015–2022 means SATA SSD.

NVMe SSD

Flash memory over the NVMe protocol directly on the PCIe bus. 3,500–7,000 MB/s sequential. 500,000–1,000,000 IOPS random read. 6–10× faster than SATA for the small, random reads that database engines make. Standard on modern data-center SSDs.

Read the NVMe Wikipedia entry for the deep technical history.

2. The Numbers (Real Benchmarks)

Benchmarks run with fio, 4 KB random read, queue depth 32, single thread:

For WordPress, the single most relevant number is random 4K read IOPS. That's the pattern MySQL makes when serving queries. NVMe delivers 10–50× more IOPS than SATA SSD, which is why the same database query returns in 2 ms on NVMe vs 20 ms on SATA SSD.

3. Why NVMe Matters for WordPress Specifically

A single WordPress page request typically executes 50–200 database queries. Each query is a tiny random read — lookup a post by ID, lookup the author, lookup the user meta, lookup the options table, lookup the post meta, and so on. The query itself might take 0.5 ms of CPU time, but the disk read waiting for the row dominates.

• On HDD: 150 queries × 5–15 ms seek = 750–2,250 ms just waiting on disk.
• On SATA SSD: 150 × 0.1 ms = 15 ms.
• On NVMe: 150 × 0.02 ms = 3 ms.

This is why the TTFB on the same WordPress site can be 1,200 ms on HDD-backed shared hosting, 300 ms on SATA SSD, and 100 ms on NVMe. The PHP code is identical. The database schema is identical. The storage is different.

Once you enable object caching (Redis or Memcached), most queries hit RAM and the disk matters less. But disk still matters for writes — every new order, comment, or form submission is a disk write, and those can't be cached away.

4. How to Verify What Storage Your Host Uses

Method 1 — SSH and lsblk

lsblk -o NAME,ROTA,MODEL

Look at the ROTA column. 0 = SSD or NVMe, 1 = HDD. The MODEL column usually tells you the exact drive — if it starts with NVMe or the name includes a drive model like "Samsung PM9A3" (a data-center NVMe), you're on NVMe. If it says "Samsung 860 EVO" you're on SATA consumer SSD. If you see something like "WDC WD20EFRX" you're on spinning HDD.

Method 2 — Run a fio benchmark

fio --name=test --filename=/tmp/test --size=1G --rw=randread --bs=4k --runtime=30 --numjobs=4

IOPS numbers in the hundreds of thousands = NVMe. Tens of thousands = SATA SSD. Hundreds or low thousands = HDD or a severely throttled virtualized volume.

Method 3 — Read the hosting plan page carefully

"SSD storage" = could be SATA or NVMe. Ambiguous. "NVMe SSD storage" or "NVMe storage" = definitely NVMe. "Enterprise SSD" = usually SATA data-center SSD. "Ultra-fast storage" = marketing with no technical claim. "HDD" or silence on storage type = spinning disk. All LaunchPad Host plans use NVMe (PCIe 4.0 on Growth and Scale).

5. When the Storage Type Actually Matters

Storage matters most when:

• You run WordPress, WooCommerce, or any database-heavy CMS
• You have little or no object caching (the raw query time dominates)
• You're on shared hosting where CPU is already constrained
• You have high write volume (WooCommerce stores, forums, logging)

Storage matters less when:

• Your site is static HTML served from a CDN
• You have aggressive full-page caching hitting 95%+ cache ratio
• You're on a well-tuned VPS with dedicated IOPS

But even in the "matters less" cases, NVMe is essentially free at modern hosting price points — there's no reason to accept slower storage in 2026.