Reviewed by the SEOPointz team · Last reviewed June 2026. We’ve benchmarked Time to First Byte across shared, VPS, and cloud plans, so these figures reflect testing rather than marketing copy. SEOPointz may earn a commission from some links; it never changes what we recommend.
Most advice about a slow website points at images, plugins, and bloated themes — all fair. But there’s a layer underneath all of that which no amount of front-end optimisation can fix: how fast your server responds in the first place. If your host takes 600 milliseconds to begin sending a page, every visitor pays that tax before a single image loads. This is the part of speed that’s baked into your hosting choice, and it’s the part people discover too late.
Why milliseconds turn into lost money
Speed isn’t a vanity metric. Industry data consistently shows a roughly 7% drop in conversions for every additional second of load time, and bounce rates climb steeply once a page crosses the three-second mark — rising sharply as load time stretches toward five seconds. For a store doing real volume, a half-second improvement can translate into six figures of recovered revenue a year. The visitor doesn’t consciously time your page; they just feel the lag and leave. Slow hosting quietly erodes the traffic you already paid to acquire.
Google is watching the clock too
Page speed feeds directly into Core Web Vitals, the performance signals Google uses as part of ranking. The headline metric, Largest Contentful Paint, is heavily influenced by how quickly your server starts responding. As of 2026 only about a third of websites pass all three Core Web Vitals, and Google’s recommended thresholds have tightened rather than loosened. Notably, fully hosted platforms tend to post higher pass rates than self-hosted WordPress sites — not because WordPress is slow, but because default shared hosting often is. Server speed is therefore both a conversion issue and an SEO issue at the same time.
Time to First Byte: the number that exposes your host
Time to First Byte (TTFB) measures how long the server takes to send the first byte of a response. It strips away your design and isolates raw hosting performance, which is why we lead with it when testing providers. A high TTFB usually traces back to the server stack rather than your code: an overcrowded shared server, slow storage, an outdated PHP version, or no server-level caching. If your TTFB is poor, optimising images won’t save you — the delay happens before the browser even starts drawing.
What actually makes hosting fast
A handful of factors do most of the work, and they’re worth checking before you buy:
- Storage: NVMe SSDs read and write several times faster than older SATA SSDs, cutting database query time and TTFB on dynamic sites.
- Server software & caching: LiteSpeed with server-level caching can reduce TTFB by the vast majority for cacheable pages — often the single biggest win on a WordPress site.
- Server location: latency rises with distance — roughly 10ms per 1,000km for dynamic requests — so a server near your audience matters.
- CDN: a content delivery network serves static files (images, CSS, scripts) from locations close to each visitor, but it can’t speed up dynamic, logged-in, or checkout pages — those still hit your origin server.
- Resources: crowded shared plans throttle under load; VPS, cloud, or quality managed hosting give you headroom.
| Speed factor | Slow setup | Fast setup |
|---|---|---|
| Storage | SATA SSD / HDD | NVMe SSD |
| Caching | None / plugin only | Server-level (e.g. LiteSpeed) |
| Server distance | Far from audience | Near audience + CDN |
| Plan type | Crowded shared | VPS / cloud / managed |
| PHP version | Outdated | Current, tuned |
How to test what you’re paying for
Before committing — or before blaming your theme — measure. Run your site through a tool that reports TTFB and Core Web Vitals from a location near your real audience, then test again from elsewhere to see how much distance hurts. If TTFB is consistently high even on a near-empty page, the bottleneck is your host, and no front-end tweak will fix it. That’s the moment to consider upgrading your plan or switching providers, rather than spending another weekend compressing images.
Frequently asked questions
What’s a good Time to First Byte?
As a working target, under 200ms is excellent and under 500ms is acceptable for most sites. Consistently above that on a lightly loaded page points to a hosting limitation rather than your content.
Will a CDN fix slow hosting on its own?
Only partly. A CDN accelerates static assets globally, but dynamic content — carts, logins, search — still comes from your origin server, so a slow host stays slow for those pages.
Is shared hosting always too slow?
No. Quality shared hosting with NVMe storage and server-level caching is fast enough for many sites. The problem is overcrowded budget plans where you compete for resources with hundreds of neighbours.
To go deeper, see how speed ties into rankings in our guide to web hosting and SEO, and don’t overlook the trade-off between performance and protection covered in web hosting security.
