The real causes, roughly in order
Before touching hosting at all, these are the culprits that show up most often, starting with the ones that tend to have the biggest impact:
- Unoptimised images. A single product photo exported straight from a phone camera can be 4 to 8MB. A page with a dozen of those is loading tens of megabytes before anything else even starts rendering.
- Too many plugins, or the wrong ones. Every active plugin adds code that has to run on every page load. Heavy page builders in particular tend to load significant CSS and JavaScript regardless of whether a page actually uses those features.
- No server-level caching. Without it, WordPress rebuilds the same page from scratch, querying the database, on every single visit, instead of serving a pre-built version.
- Database bloat. Years of unlimited post revisions, expired transients, and spam comments sitting in the database slow down every query, even simple ones.
- Outdated PHP version. Each major PHP version has brought meaningful performance improvements. A site still running an old PHP version is leaving real speed on the table for free.
- Oversold shared hosting. If a server is hosting far more sites than its CPU and RAM can comfortably support at once, every site on it slows down together during peak load, regardless of how well-optimised any individual site is.
Notice how far down the list "which host you're with" actually sits. It matters, but it's rarely the single biggest factor, and no amount of hosting can compensate for a homepage loading eight unoptimised hero images.
What NVMe actually changes
Every WordPress page load involves reading a large number of small files: PHP core files, plugin files, theme files, and often thousands of tiny database queries. This is a read pattern that specifically benefits from fast storage, because it's not one big file being read once, it's thousands of small reads happening rapidly. NVMe drives handle exactly this pattern significantly faster than older SATA SSDs, which is why the difference is more noticeable on WordPress specifically than on, say, serving a single large video file.
This happens before any caching layer even gets involved. It's the baseline speed of every request touching the disk, which on a busy WordPress site happens constantly.
What LiteSpeed actually changes
Most WordPress caching plugins work by intercepting the request inside WordPress itself: PHP still has to start up, WordPress still has to load, and then the plugin checks whether a cached version exists. LiteSpeed's built-in LSCache works at the web server level instead, serving a cached page before PHP is even invoked for that request. For a cached page, that's the difference between doing almost no work and doing a meaningful chunk of work just to arrive at the same cached result.
| Layer | Standard setup | NVMe + LiteSpeed |
|---|---|---|
| Storage | SATA SSD | NVMe SSD |
| Page caching | Plugin-level, PHP still runs | Server-level, PHP often skipped entirely |
| Server resource use per cached request | Higher | Lower |
What only you can fix
Hosting solves the infrastructure layer. It cannot solve:
- Images exported at full camera resolution instead of compressed and appropriately sized
- A page builder loading unnecessary CSS and JavaScript on every page
- Fifteen active plugins where three would do the same job
- A theme built without any attention to performance
A genuinely fast site needs both a capable server underneath it and reasonably disciplined choices on top of it. Neither one alone gets you all the way there.
- Run your homepage through a free speed test tool and note the largest individual files it's loading
- Compress and resize any image over 200KB before uploading it
- Deactivate any plugin you can't immediately explain the purpose of
- Confirm you're running a current PHP version in your hosting control panel
- Make sure exactly one caching plugin or server-level cache is active, not several stacked together
Get the infrastructure layer right
Every WebSpaceBar hosting plan runs on pure NVMe storage with LiteSpeed Enterprise caching and 1-click WordPress installs, standard.
Frequently asked questions
Does NVMe storage actually make WordPress faster?
Yes, measurably. WordPress reads a large number of small PHP and asset files on every page load, and NVMe drives handle that kind of read pattern far faster than older SATA SSDs, which reduces server response time before a single caching layer even gets involved.
Is LiteSpeed faster than Apache for WordPress?
For WordPress specifically, yes, mainly because of LSCache, a server-level caching layer built into LiteSpeed that serves cached pages before PHP even needs to run. That's a meaningful step up from most plugin-based caching, which still has to execute inside WordPress to check the cache.
Will better hosting fix a slow WordPress site on its own?
Better hosting fixes server-side bottlenecks like disk speed, CPU throttling, and caching, but it can't fix unoptimised images, bloated page builders, or excessive plugins. A fast host with an unoptimised site will still be slow, just less slow than it would be on weaker hardware.
How many caching plugins should a WordPress site run?
One. Running multiple caching plugins at once frequently causes conflicts that make a site slower or behave unpredictably, not faster. Pick a single caching solution suited to your hosting environment and remove the others.