Your WordPress host is probably why your WordPress site is slow. Every week someone tells us their site is slow and asks which speed plugin to install. Nine times out of ten, the plugin isn’t the problem — the stack underneath the site is. Here’s what’s usually going on, how to prove it with numbers, and what actually fixes it.
One framing before we start, because it explains almost everything below: hosting has a triangle — fast, good, cheap: pick two. Cheap hosting is slow by design, not by accident. When a server is sold to as many customers as possible at the lowest possible price, performance is what got sacrificed to hit the price. We skip the cheap corner — we sell the fast-and-good corner — and this article will show you exactly how to tell which corner you’re currently standing in.
First, learn to read TTFB — the honest metric
Time to first byte (TTFB) is how long the browser waits before the server sends anything at all. It’s the purest measure of your hosting, because it strips out your theme, your images, your fonts — everything you’d be tempted to blame. Rough guide on a cached page:
- Under 200ms — properly tuned hosting. Nothing to fix here.
- 200–600ms — workable, with room to improve.
- Over 600ms — the hosting is the bottleneck. No caching plugin on earth will rescue this; the wait happens before WordPress even finishes thinking.
Measure it in your browser’s developer tools (Network tab, first request) or any TTFB checker. If the number is ugly, everything below explains why — and most of the causes are hosting-side.
The usual suspects, in order of likelihood
1. The shared hosting squeeze
Your site shares a server — CPU, memory, disk I/O — with hundreds of others, and the host throttles each account to make that work. The limits have names you’ll see in hosting control panels: entry processes, PHP workers, execution allotments. Hit the cap and requests queue. Add a “noisy neighbour” site having a busy moment on the same box, and your TTFB triples — through no fault of anything you installed. “Unlimited” bandwidth and storage don’t help; the scarce resource was never storage, it’s compute.
2. No server-level caching
WordPress generates every page in PHP — database queries, plugin logic, theme template — for every single visitor. Server-level page caching (LiteSpeed’s cache, nginx fastcgi_cache) stores the finished HTML and serves it without running PHP at all, which is why a good host can serve a cached page in tens of milliseconds. A caching plugin running on plain Apache without server support still wakes PHP for every request — you get the plugin’s settings screen but not its promise.
3. Missing object cache and opcache
Two different things people confuse. Opcache stops PHP recompiling your code on every request — free performance many budget hosts leave switched off. An object cache (Redis or Memcached) stores repeated database query results in memory. It matters most when the page cache can’t be used: logged-in users, WooCommerce carts and checkouts, membership sites. An online store with no object cache is paying for the same product query again and again, every request.
4. Front-end weight
Once the server’s fast, the page itself can still be heavy (and if you’re wondering whether server or page is your problem, our speed audit walkthrough shows exactly how we tell): uncompressed images served as full-size JPEGs (modern formats like AVIF and WebP are often a quarter of the size), five font families where one would do, render-blocking CSS and JavaScript stacked in the head, and third-party scripts — chat widgets, trackers, embeds — each adding their own round trips. One caution from the trenches: don’t lazy-load your hero image. It’s the first thing visitors see; lazy-loading it delays your Largest Contentful Paint for no bandwidth benefit. (And if you do build with a page builder, use one that’s actively maintained — Elementor is the mainstream option, and Crocoblock extends it for dynamic sites. They’re convenient; they’re also not what we’d choose when every millisecond counts.)
5. No CDN, and slow DNS
If your server sits in one city and your customers don’t, physics is against you — every visitor far from the data centre pays latency on every request. A CDN caches your assets at the edge near your visitors. And DNS is the very first lookup before anything else happens; anycast DNS (ours is called PainlessDNS®) answers from the nearest node instead of one fixed location. Both are cheap wins that cheap hosting tends to skip.
The fix, in order of impact
- Move to properly tuned managed WordPress hosting — LiteSpeed or nginx with server-level page caching, Redis object cache, modern PHP, a CDN and anycast DNS. (Ours is DomainCastle®; whichever you choose, ask the questions below.)
- Turn on the caches your host provides — page cache and object cache. This is configuration, not surgery.
- Cut page weight — modern image formats at proper sizes, drop unused plugins, defer non-critical scripts.
- One font family. Maybe two. We said what we said.
Do them in that order. Most sites feel twice as fast after step one alone, because step one is usually the actual problem.
Five questions to ask any WordPress host before you pay them
- What’s your TTFB on a cached page, and will you show me a live test?
- Is page caching server-level (LiteSpeed/nginx) or plugin-only?
- Is Redis or Memcached available for object caching?
- How many PHP workers / entry processes do I actually get?
- Where are backups stored, how long is retention, and how do I restore one myself?
The same corners explain your security posture too — cheap hosting is where most compromised sites start. Quick, confident, specific answers: you’re in the fast-and-good corner. Vague ones about “optimised servers” and “99.9% uptime”: you’ve found the cheap corner, and now you know what that buys.
Want the numbers for your own site before you decide anything? We run a free speed audit — pick “Book a free speed audit” on the contact page. Real measurements, plain English, no obligation.
Affiliate Disclosure: This article contains affiliate links. If you click a link and make a purchase, we may earn a commission at no additional cost to you. We only recommend products and services we genuinely believe in. This disclosure is made in accordance with the Australian Consumer Law (ACL) and the AANA Code of Ethics. Thank you for your support.
