WordPress Hosting Page Cache Speed: How We Cut Load Time From 558ms to 16ms
Page caching on a WordPress host is not a plugin feature — it is an infrastructure decision, and the difference between doing it wrong and doing it right is the difference between 558ms and 16ms on the first byte.
This article explains exactly how CM Cloud Managed WordPress implements server-side caching, what the numbers look like in practice, and why it matters especially for businesses in Cameroon, Nigeria, Ghana, Kenya, and across West Africa where last-mile latency already adds overhead.
Why Most WordPress Hosts Fail at Caching
Most shared hosts tell you to install a caching plugin — W3 Total Cache, WP Super Cache, LiteSpeed Cache. That puts the responsibility on you and adds a layer of complexity that breaks on plugin updates.
The deeper problem: PHP still boots on every uncached request on those hosts. If your cache is cold, stale, or bypassed by a logged-in user, you pay the full PHP + MySQL round-trip cost every time.
On a busy site in Lagos or Douala, where the connection already has 30–80ms of additional latency vs. a European data centre, a slow host compounds that penalty.
How CM Cloud Managed WordPress Caches Pages
CM Cloud Managed WordPress implements caching at the server layer — nginx + FastCGI cache — before PHP is invoked. Here is the request path for a cached page:
- Request arrives at nginx
- nginx checks the FastCGI cache store
- Cache HIT → response sent directly from memory/disk — no PHP, no MySQL
- Cache MISS → PHP + WordPress + MySQL execute, response cached, then returned
The result is a Time to First Byte (TTFB) of approximately 16ms on a cache hit, measured from within the same region. Compare that to 558ms on a typical shared host running PHP-FPM with no server-side cache.
What Gets Cached
- All public pages and posts (non-logged-in visitors)
- Taxonomy archives and category pages
- Static asset headers (Cache-Control, ETag)
What Bypasses the Cache (Correctly)
- Logged-in WordPress users (admin, editors) — they see live content
- WooCommerce cart, checkout, and account pages — never cached to prevent order data leakage
- Pages with active session cookies
This is standard, correct behaviour. Any host that caches WooCommerce cart pages is introducing bugs, not speed.
The 558ms → 16ms Benchmark
Here is what the numbers look like on a real WordPress install with a published post, tested from a West African network point:
| Scenario | TTFB | PHP Invocations |
|---|---|---|
| Shared host, no server cache | 558ms | 1 per request |
| CM Cloud, cache MISS (first load) | 210ms | 1 (then cached) |
| CM Cloud, cache HIT | 16ms | 0 |
The 558ms figure is from a shared hosting environment running PHP 8.1 with a page-caching plugin but no FastCGI or full-page server cache. The plugin cached HTML to disk, but PHP still had to read that file and return it — no nginx-level bypass.
16ms is the nginx-direct response time once the page is in the FastCGI cache. That number is infrastructure, not luck.
NVMe Storage Makes the Cache Faster Too
Every CM Cloud Managed WordPress plan runs on NVMe SSD storage. This matters for caching because FastCGI cache misses write to disk before serving — on a spinning disk or SATA SSD host, that write is a bottleneck. On NVMe, the write latency is sub-millisecond.
Hostinger’s entry tier uses SSD storage (not NVMe) at the $2.99/mo promotional price. That promotional rate also requires a 48-month lock-in and renews at $10.99/mo — the speed trade-off and the renewal jump are both worth factoring into your total cost.
CM Cloud Managed WordPress Plans
All plans include server-side FastCGI page caching, NVMe storage, free SSL, and AI credits.
| Plan | USD/mo | XAF/mo | EUR/mo | Storage |
|---|---|---|---|---|
| Starter | $6.99 | XAF 4,500 | €6.50 | NVMe |
| Business | $12.99 | XAF 8,000 | €12.00 | NVMe |
| Pro | $19.99 | XAF 12,500 | €18.50 | NVMe |
Pricing is month-to-month with no 48-month lock-in required. See full plan details at cmcloudhosting.com/pricing.
Managed WordPress vs. Competitors: Cache + Speed Comparison
| Provider | Starter Price (USD) | XAF | EUR | Server-Side Cache | Storage | Renewal Trap |
|---|---|---|---|---|---|---|
| CM Cloud | $6.99/mo | XAF 4,500 | €6.50 | ✅ FastCGI (nginx) | NVMe | No |
| Hostinger | $2.99/mo* | ~XAF 1,900* | ~€2.80* | Partial (plugin-layer) | SSD (not NVMe) | Renews at $10.99/mo |
| Kinsta | $35.00/mo | ~XAF 21,700 | ~€32.50 | ✅ Full-page (nginx) | NVMe | No |
| WP Engine | $25.00/mo | ~XAF 15,500 | ~€23.00 | ✅ EverCache | NVMe | No |
*Hostinger $2.99 requires 48-month prepayment. Renewal at $10.99/mo. Competitor prices are public list prices as of 2026 and may vary by region or promotion.
CM Cloud sits between budget hosts (Hostinger) and premium WordPress-only hosts (Kinsta, WP Engine) — with the same server-side caching architecture as the premium tier, at a price accessible to African businesses.
AI Credits Included
Every CM Cloud plan includes AI credits at no extra charge. Additional credits top up from $1.00 / XAF 500 / €0.93 for 25 credits.
| Top-Up | USD | XAF | EUR |
|---|---|---|---|
| 25 credits | $1.00 | XAF 500 | €0.93 |
Does a Caching Plugin Still Help?
Yes — but for different reasons. Once server-side caching handles the TTFB, a plugin like LiteSpeed Cache or WP Rocket still adds value for:
- Browser caching headers — telling the visitor’s browser to store CSS, JS, images locally
- Image lazy loading — deferring off-screen images
- CSS/JS minification — reducing asset payload size
- CDN integration — offloading static assets to an edge network
Think of server-side caching as solving the server response problem, and a caching plugin as solving the browser-download problem. You want both. CM Cloud solves the server side by default; a plugin handles the rest.
Practical Impact for West African Businesses
For a business in Douala, Accra, Lagos, or Nairobi:
- A 16ms TTFB from the server means the total page load time is dominated by network latency and asset download — factors you can control with a CDN and image optimisation
- A 558ms TTFB means the server itself is the bottleneck before the network even starts — no amount of CDN configuration fixes a slow server
- Google Core Web Vitals penalise slow TTFB in rankings. A fast server is an SEO investment, not just a UX improvement
If your current WordPress host does not explicitly state server-side FastCGI or full-page nginx caching, assume it is not there.
Migration Is Free and Takes Under 10 Minutes
Already have a WordPress site on Hostinger, GoDaddy, or another host? CM Cloud includes a migration tool. The process — export, import, DNS switch — typically completes without downtime in under 10 minutes.
For a full walkthrough, see the migration guide already on the blog.
Get Started
Server-side page caching should be a default, not a premium feature. CM Cloud Managed WordPress includes it on every plan — Starter at $6.99/mo (XAF 4,500 / €6.50), no lock-in required.
View plans, compare features, and sign up at cmcloudhosting.com/pricing.