Is my web hosting slow? How to test it and what to do next

How to test your hosting speed

A reliable verdict takes a few measurements, not one:

1. 1Run the TTFB checker on your home page several times. One reading can catch a momentary spike.
2. 2Compare the cold and warm results. The warm (repeat) request shows how fast the server is when caching works.
3. 3Test a small static file on the same server, such as /robots.txt. This separates the server and network from your application.
4. 4Test a page that can't be cached, such as search results or a cart, to see the server's raw speed.
5. 5Run the website speed test to see how much of your LCP is spent waiting on the server, and what real visitors experience in field data.
6. 6Repeat at a busy time of day. Shared servers often slow down when neighbors are busy.

Reading the results

For a single lab test, under about 300 ms is good and over about 800 ms is slow; the TTFB checker uses these bands. Google's own guidance for real visitors is more forgiving, treating up to 0.8 seconds at the 75th percentile as good, because field data includes slow mobile networks and distant visitors.

Look at where the time goes. If most of it is DNS, connection, or TLS setup, the cause is distance or configuration, and a CDN or a server region closer to visitors helps. If most of it is server wait, the server is slow to build the page: that's caching, the application, or the hosting plan's resources.

Rule out the fixes that don't need a new host

Before blaming the host, check page caching. If two requests in a row are equally slow, the server rebuilds every page from scratch. Enabling full-page caching (a caching plugin on WordPress, or the host's built-in cache) is usually the single biggest TTFB win, and it's free.

Heavy plugins, slow database queries, and outdated PHP versions also show up as server wait. If caching is on, the software is current, and the server still takes over a second to answer, the plan itself is likely out of resources.

Slow admin area, fast front end?

A fast public site with a sluggish dashboard is a common pattern on WordPress and similar systems. Visitors get cached pages, while the admin area is never cached and runs the full application on every click. That makes the admin area an honest view of the server's raw speed: if saving a post or loading the dashboard routinely takes several seconds, the server is struggling, even though cached pages hide it from visitors. Heavy admin plugins can cause the same symptom, so disable suspects one at a time before concluding it's the hosting.

Signs the hosting itself is the bottleneck

Any one of these on a budget plan is a strong sign that the plan, not the site, is the limit:

• Slow server wait even with caching on, or on a static file.
• Response times that swing widely between runs, which points at an overloaded shared server.
• Frequent 5xx errors or timeouts during traffic peaks.
• A control panel that reports hitting CPU, memory, or process limits; many cPanel hosts show this on a Resource Usage page.
• On a VPS, high CPU steal time (the st value in top), meaning other tenants are using the physical CPU.
• A server far from most of your visitors, with no CDN in front.

Shared, VPS and managed hosting: what changes

On shared hosting, many sites share one server's CPU, memory, and disk, and performance depends on how heavily the host loads each machine. A VPS gives you a guaranteed slice of a machine, but you or the host must configure caching and software well. Managed hosting adds a tuned stack, usually with server-level caching, on top of either model.

None of these is automatically fast or slow. The type of plan tells you which limits apply; measured response times tell you whether you're hitting them.

Questions to ask your host

Before moving, it's worth asking support a few specific questions, with your TTFB measurements attached:

• Which data center is the site on, and can it move closer to most visitors?
• Has the account hit CPU, memory, or process limits, and when?
• Is server-level page caching available, and is it enabled for this site?
• Which PHP or runtime version is the site using, and can it be upgraded?
• Do the server's slow logs show particular requests or queries taking most of the time?

Is the server in the right place?

Server location is part of hosting speed that no amount of tuning changes. Every connection needs several round trips, and each one is longer when the server is on another continent from most visitors. If your audience is mostly in one country and the server sits far away, connection setup alone can add hundreds of milliseconds per new visitor. The latency test shows the round-trip time from its measuring server, and the hosting checker shows which network the site runs on, which together give a first idea of where the server is. Moving to a closer data center, or adding a CDN, is the fix.

Will a CDN fix slow hosting?

Partly. A CDN serves cached pages from locations near visitors without touching your server, which hides slow hosting for cacheable pages. But logged-in users, carts, checkouts, and anything personalized still go to the origin, and many CDNs don't cache HTML at all until you configure them to. A CDN is a good complement to adequate hosting, not a replacement for it.

If you switch hosts, measure the result

Judge a new host on independent, measured results rather than marketing claims, and test on your own terms. Before migrating, record TTFB for a few representative pages; afterward, measure the same pages the same way. The hosting checker confirms the site is really being served from the new server, and the DNS propagation check shows when visitors' resolvers have caught up with the move.