To run a web hosting speed test, measure your server response time (Time to First Byte, or TTFB) several times, at different times of day, from different locations, on both a cached and an uncached page. A good TTFB is 0.8 seconds or less (Google, web.dev). Start with our free website speed test and compare the result with the checks below.
Key takeaways
- Hosting speed shows up mainly as server response time (TTFB).
- One test is not enough. Test several times, at different times and from different places.
- Test a cached page and an uncached page, because they show different things.
- A slow TTFB does not always mean bad hosting. Heavy plugins and missing caching can cause it too.
What does a web hosting speed test measure?
A hosting speed test mostly measures how fast your server starts to respond, which is TTFB. It also shows how stable the response is over time, and how it changes with location. It does not measure how heavy your pages are, which is a separate problem.
How do you test your web hosting speed?
1. Test the server response time
Run your page through our PageSpeed Insights walkthrough steps or our free page speed checker and look for the server response time item. Compare with the 0.8 second target. See what a good TTFB is.
2. Test at different times of day
Shared hosting can slow down at busy times. Test in the morning, afternoon and evening for a few days and note the range.
3. Test from different locations
The distance between your visitors and your server affects response time. Use a tool that lets you pick a location, such as WebPageTest. See how to use WebPageTest.
4. Test a cached and an uncached page
A cached page shows how fast your server can deliver ready-made pages. An uncached page shows how fast it can build one. A big difference means your site depends heavily on caching.
5. Test a simple static page
Create a very small plain page on your hosting, with no plugins or database. If it is fast, your host is probably fine and the slowdown comes from your site. If even that is slow, the server is the likely cause.
6. Watch uptime
Speed is not the only measure of hosting. Check that your site stays available. See website performance monitoring tools.
How do you tell hosting problems from site problems?
If your simple test page is fast but your normal pages are slow, the problem is in your site: plugins, theme, database or missing caching. If everything is slow, check your hosting plan, PHP version and server resources. See why your website is slow for the common causes.
When should you change your hosting?
Consider a change if your TTFB is regularly above 0.8 seconds on cached pages after you have fixed caching and plugins, if speed varies a lot during the day or if your site goes down often. Compare plans on resources and support, not just price. Test a new host with a copy of your site before you move.
Frequently asked questions
How do I check my hosting speed for free?
Use our free speed test, Google PageSpeed Insights or WebPageTest and read the server response time.
What is a good server response time?
0.8 seconds or less is good, and over 1.8 seconds is poor (Google, web.dev).
Does hosting affect SEO?
Indirectly, through server response time and Core Web Vitals. See how important page speed is for SEO.
Is shared hosting too slow?
Not always. Quality varies, and results depend on plan, server load and your own site.
How often should I test my hosting?
Test after any change, and run a few tests across different times of day at least once a quarter.
Conclusion
A hosting speed test is a set of repeated checks: server response at different times, from different places, cached and uncached. Start with our free website speed test, and if the host is the problem, follow our guide on how to improve website speed.
