There's a version of this post that opens with a leaderboard — our number next to someone else's, ours in a friendlier colour. We're not going to do that. Benchmarks make for good screenshots and bad promises, because the fast number in the screenshot is almost never the number your visitors get on a Tuesday afternoon.

So instead we pulled a month of real traffic off the platform and worked backwards. Time to first byte. Cache hit rates. Largest contentful paint on actual customer sites, not a stripped-down test page. The honest summary: most of the speed comes from a handful of unglamorous decisions made carefully, then left alone. Here's the long version.

Why speed is the floor, not the ceiling

A slow site doesn't just feel bad. It quietly taxes everything you're trying to do. Google folds Core Web Vitals into how it ranks pages, so a sluggish largest contentful paint costs you visibility before a visitor ever arrives. And once they do arrive, every extra second on load is a share of them gone — bouncing back to the search results, never seeing the thing you wrote or the thing you sell.

That's why we treat speed as the floor. Not a premium tier, not an add-on you unlock on the expensive plan — the baseline every site sits on. A personal blog on Roost runs on the same fast storage and the same tuned cache as a busy store on Flock. The bigger plans add headroom and reach, not a different class of fast.

The two choices doing most of the work

If you stripped the platform back to its studs, two decisions account for most of what you feel as "quick."

NVMe storage, everywhere

Every plan sits on NVMe SSD storage. The short version: NVMe talks to the server over a much wider, much faster lane than the SATA SSDs a lot of budget hosts still run. For a database-driven site like WordPress — where a single page view can mean dozens of small, random reads — that lane width is the difference between a page that snaps and a page that hesitates.

It doesn't show up in a brochure the way "unlimited everything" does. It shows up in the half-second your visitor doesn't spend waiting.

LiteSpeed and a cache that's actually tuned

The web server itself is LiteSpeed, paired with server-level caching that's configured before your site ever goes live. The distinction that matters: a plugin cache lives inside WordPress, so PHP still has to boot up to hand back a cached page. Server-level caching answers from in front of WordPress entirely. PHP never wakes up. The page is just... there.

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.

On a well-cached page, a returning visitor often gets a response in a few dozen milliseconds — because nothing is being built, it's being handed back.

What the numbers actually said

A few patterns held across the month, and they're worth saying plainly because they're more useful than a single hero figure.

  • Cache hit rate is the whole game. The sites with the best real-world load times weren't the ones on the biggest plans. They were the ones whose pages cached cleanly. A page that misses the cache and rebuilds from PHP and the database every time will always lose to a page served from memory — on any host.
  • Time to first byte is mostly waiting, not computing. When TTFB was bad, it was almost never the CPU. It was a slow external call: a third-party font, an analytics beacon, a "related products" widget phoning a far-away API mid-render.
  • The biggest LCP wins were images. Not server tuning. An unsized hero image, shipped at 4000px wide to display at 800, undoes a lot of careful infrastructure in one stroke.

That last one is the recurring theme. The platform gives you a fast floor. The ceiling is mostly back in your hands.

The part that's back in your hands

Here's the honest hand-off. We can — and do — own the boring, heavy parts: fast NVMe storage, a tuned server-level cache, and a global CDN on Perch Pro and up so your assets are served from close to your visitor. That's the floor, and it's a high one — the same floor under a personal blog and a busy store alike.

What we can't do from the server room is un-bloat a page. A few things that move the needle more than any host setting:

  1. Size your images to how they're displayed, and let modern formats do their job. This is the single highest-leverage change on most sites.
  2. Be a tough doorman about third-party scripts. Every embedded widget, chat bubble, and tracker is a request to somewhere you don't control, on the critical path to your page appearing.
  3. Lean on the cache instead of fighting it. A page that can be cached whole will always beat a page that insists on being rebuilt for every visitor.

None of that is exotic. It's the same boring discipline as the infrastructure underneath it — done carefully, then left alone.

Settle in

We'd rather earn the word "fast" on your real traffic than win it on a test page. Every plan rides the same fast floor, every plan is backed by a 30-day money-back guarantee, and you can watch your own numbers from the dashboard once you're settled in.

If you want the walkthrough version, launch your first site takes about a minute, or see the plans to find the right perch.