Most of what you feel as "fast" on a website isn't a single clever trick. It's a couple of unglamorous decisions, made early and then left alone. For us, two of those decisions sit underneath every plan we sell: the web server we run, and the storage we run it on.
This is the longer explanation of both — what they are, why they matter for WordPress specifically, and why they're the floor on a personal blog and a busy store alike, rather than a perk you unlock by spending more.
The web server, and where caching lives
When someone visits your site, a program on the server has to receive the request, figure out what to send back, and hand it over. That program is the web server. We run LiteSpeed. The reason matters less than what it lets us do, which is cache pages at the server level — in front of WordPress, not inside it.
That distinction is the whole point, so it's worth slowing down on.
A plugin cache lives inside WordPress. When a request arrives, PHP still has to wake up, load WordPress, and let the plugin decide "ah, I have this one saved" before handing back the saved copy. It's faster than rebuilding the page from scratch, but PHP still booted up to do it. There's still a little engine turning over before anything happens.
Server-level caching answers from in front of WordPress entirely. The web server itself holds the finished page in memory and hands it straight back. PHP never wakes up. The database is never touched. For a returning visitor on a cached page, the response is essentially "here's the page I already had" — often back in a few dozen milliseconds.
The fastest database query is the one you never run. The fastest line of PHP is the one that never executes. Good caching is mostly the art of doing less, sooner.
Here's the part that tends to get glossed over: we tune that cache before your site goes live, not after you go hunting for a plugin and a YouTube tutorial. The configuration that usually takes an afternoon of trial and error is already done. You inherit it.
So, LiteSpeed vs. nginx?
People ask this a lot, usually because they've read a benchmark. The honest answer is that both are excellent, modern web servers, and either one beat the older setups years ago. What we care about isn't a leaderboard — it's that LiteSpeed's caching integrates cleanly with WordPress and answers cached requests without dragging PHP into it. That integration is the feature. The name on the box is just the name on the box.
NVMe storage, and why databases care
The second decision is storage. Every CloudPerch plan sits on NVMe SSD storage. No plan, anywhere in the lineup, runs on the slower stuff.
A quick analogy. An older SATA SSD talks to the server through a narrow lane — fine for big, sequential reads, like streaming one large file start to finish. NVMe talks to the server over a much wider, much faster lane, and it's especially good at lots of small, scattered reads happening at once.
That last bit is the whole reason it matters for WordPress. A site like yours isn't one big file. It's a database-driven application, and a single page view can mean dozens of tiny, random reads — this post, those settings, that menu, these widgets, the user who's logged in. On narrow storage, each of those little reads waits its turn. On NVMe, they don't.
You can think of it as the difference between a page that snaps and a page that hesitates. The hesitation is rarely one big pause. It's a hundred tiny ones, stacked up, and storage is where a lot of them come from.
It won't show up in a brochure the way "unlimited everything" does. It shows up in the half-second your visitor doesn't spend waiting — and in the admin area, which is the one part of WordPress that can't be fully cached and leans on the database constantly.
Why both are on every plan
Plenty of hosts treat speed as a tier. The cheap plan gets the slow floor; "performance" is a line item further up the menu. We went the other way on purpose.
Every plan — from Roost at $14/mo all the way up to Aerie — rides the same NVMe storage and the same tuned LiteSpeed cache. The bigger plans add headroom and reach, not a different class of fast:
- Roost and up: NVMe storage, LiteSpeed, server-level caching, free SSL, daily backups. The fast floor.
- Perch Pro and up: a global CDN, so your images and assets are served from a location near your visitor instead of one spot on the map.
- Flock and up: more transfer and stronger security — advanced DDoS protection and a WAF — for busy stores and membership sites pulling real numbers.
A personal portfolio gets the same baseline speed as a store doing real numbers. What you pay more for is room to grow into, not permission to be quick.
| Plan | The speed floor | What's added |
|---|---|---|
| Roost | NVMe + LiteSpeed + tuned cache | — |
| Perch Pro | same floor | Global CDN, WAF, SFTP |
| Flock | same floor | Advanced DDoS + WAF, SSH |
| Aerie | same floor | Unlimited sites, more headroom |
The honest hand-off
We can own the heavy, boring parts: fast storage, a tuned cache, and — once you're on Perch Pro — a CDN that serves your assets from close to your visitor. That floor is high, and it's the same one for everyone.
What we can't do from the server room is un-bloat a page. An unsized hero image shipped at 4000px to display at 800, or a stack of third-party scripts each phoning a far-away server mid-load, will undo a lot of careful infrastructure in one stroke. We wrote more about that trade-off in speed isn't a feature — the short version is that the platform gives you the floor, and the ceiling is mostly back in your hands.
That's the deal we're comfortable making: do the unglamorous work once, do it carefully, then leave it alone so it keeps paying off quietly on every page load you never have to think about.
If you'd like to see the floor for yourself, launch your first site takes about a minute, or compare the plans to find the right perch for what you're building.