← All posts
PERFORMANCE

How NVMe storage cuts your TTFB in half

MC
Maya Chen
Performance Engineer · Jun 18, 2026 · 8 min read

Time to First Byte — TTFB — is the quiet tax on every page you ship. It's the gap between a visitor's request and the first byte of your response, and it sits underneath every other performance metric you care about. Optimize your images all you like; if your server is slow to respond, the whole experience feels sluggish.

There are many levers for TTFB, but the one teams reach for last is also one of the most impactful: the storage layer. The disk your database and application files live on dictates how fast your server can read and write — and on shared hosting, that's often a spinning disk or an oversubscribed SATA SSD.

Why disk speed still matters

Modern frameworks read dozens of files per request and run database queries that touch disk constantly. Every cache miss, every uncached query, every session lookup becomes a round trip to storage. NVMe drives connect over PCIe rather than the aging SATA bus, and the difference in random read latency is dramatic — microseconds instead of milliseconds.

"In our WordPress benchmarks, simply moving from SATA SSD to NVMe dropped median TTFB from 410ms to 190ms — with no application changes at all."

The benchmark setup

We ran identical WordPress and Node.js workloads on two otherwise-matched servers — same vCPU, same RAM, same region — changing only the storage tier. Each test issued 10,000 requests at a steady concurrency of 50, and we recorded TTFB at the 50th and 95th percentiles.

WorkloadSATA SSDNVMe
WordPress p50410ms190ms
WordPress p95980ms420ms
Node API p50120ms58ms

What this means for you

Storage is not a setting most people think to check, which is exactly why it's such an easy win. Before you spend a sprint refactoring queries, confirm what your host actually runs underneath you. At Corehostly, every plan — from the smallest shared tier to dedicated metal — ships on NVMe by default, with no premium add-on. That's a deliberate choice: the fast path should be the default path.

If you're on a host that still charges extra for NVMe, or won't tell you what you're running, that's a signal worth acting on. Faster storage is the rare optimization that helps every request, every visitor, every day — without touching a line of your code.

MC
Maya Chen
Performance engineer at Corehostly. Spends her days shaving milliseconds off the platform and writing about what she finds.

Keep reading

{{ r.cat }}

{{ r.title }}

Want NVMe on every plan?

It's the default at Corehostly — no upcharge, every region.

See plans →