Your website feels sluggish, customers complain and your PageSpeed score is red. But what is to blame? It could be heavy images, a bloated theme, too many plugins, or the server itself. Before you spend money on a redesign, it helps to know how to tell if your hosting is slowing down your website. This guide shows you simple tests anyone can run, the numbers to look for, and what to do about the results.
Why hosting matters for speed
Every time someone visits your site, their browser asks your server for the page. The server has to process the request, run any code such as WordPress and PHP, query the database and send back the result. Only then can the browser start downloading images, styles and scripts. If the server is slow, overloaded or poorly configured, everything waits. No amount of image compression fixes a server that takes three seconds to respond.
Sign 1: High Time to First Byte (TTFB)
Time to First Byte measures how long it takes for the first piece of data to arrive from your server after a request. It is the clearest indicator of server performance.
How to test:
- Go to a free tool such as Google PageSpeed Insights, GTmetrix or WebPageTest.
- Enter your website address and run the test.
- Look for "Server response time", "Initial server response" or "TTFB".
What the numbers suggest: as a rough guide, a TTFB under about 600 milliseconds is reasonable, and under 200 milliseconds is excellent. If you regularly see well over one second, your hosting is a strong suspect, especially if the page itself is not very heavy.
Test several times, at different times of day, and test a simple page like your Contact page as well as your home page.
Sign 2: Speed varies wildly at different times
If your site is fast early in the morning but crawls during business hours, the server may be overloaded. On cheap shared hosting, hundreds of websites can share the same resources. When neighbours get busy, your site suffers. Run tests at 7am, midday and evening across a few days and compare.
Sign 3: Even a blank page is slow
This is a powerful test for WordPress sites. Create a new, empty page with just a heading and publish it. Test that page. If even a nearly empty page has a slow server response, the issue is not your images or content, it is the server or the core configuration.
Sign 4: The admin area is painfully slow
If the WordPress dashboard takes ages to load, saving posts times out or uploading images fails, the server may lack CPU, memory or fast storage. The admin area is not cached, so it exposes raw server performance.
Sign 5: Frequent errors and downtime
Watch for messages such as:
- "503 Service Unavailable" or "508 Resource Limit Reached", often meaning your account hit its resource limits.
- "Error establishing a database connection", which can indicate an overloaded database server.
- "504 Gateway Timeout", where the server took too long to respond.
Sign up for a free uptime monitoring service that checks your site every few minutes and emails you when it goes down. A few weeks of data gives you hard evidence.
Sign 6: Resource usage warnings in cPanel
If your host uses cPanel with CloudLinux, look for a "Resource Usage" section. It shows whether your account has hit limits on CPU, memory, entry processes or I/O. Frequent limit hits mean your plan is too small for your traffic or your site is inefficient. Ask your host to explain the graphs if they are unclear.
Sign 7: Outdated server software
Check which PHP version your site runs in cPanel under "Select PHP Version" or MultiPHP Manager, or ask your host. Older PHP versions are slower and no longer receive security updates. Also ask whether the server uses modern storage such as SSD or NVMe and a fast web server such as LiteSpeed or Nginx.
How to rule out other causes
Before blaming your host, check the usual suspects:
- Images: are they huge files straight from a camera?
- Plugins: are you running dozens, including sliders, page builders and multiple tracking tools?
- Theme: is it a heavy multipurpose theme loading lots of unused features?
- Caching: is a caching plugin or server cache active?
- External scripts: chat widgets, ads and social feeds load from other servers and can slow pages.
Look at the waterfall chart in GTmetrix or WebPageTest. If the first request is fast but the page takes long to finish because of many large files, the problem is mostly on the website side. If the first request itself is slow, look at hosting.
A simple diagnostic checklist
- Run PageSpeed Insights and GTmetrix on home and contact pages, three times each.
- Note TTFB in each result.
- Test a blank page.
- Check cPanel Resource Usage for limit hits.
- Check your PHP version.
- Temporarily disable non essential plugins on a staging copy and retest.
- Set up uptime monitoring for two weeks.
If TTFB is consistently high and limits are frequently hit, your hosting is very likely part of the problem.
What to do if your hosting is the problem
- Talk to your host first. Share your test results. A good host will investigate, optimise settings or suggest the right plan.
- Enable server level caching if available, such as LiteSpeed Cache on LiteSpeed servers.
- Upgrade your plan if you have outgrown it, or move to a VPS for dedicated resources.
- Move to a better host if support is unhelpful or the infrastructure is outdated. Plan the migration carefully with backups and DNS changes during quiet hours.
At Baasa Cloud, our hosting runs on LiteSpeed servers with caching and daily backups, and our team can review your speed test results with you and help migrate your site if you decide to switch.
Frequently asked questions
Is shared hosting always slow?
No. Well managed shared hosting with sensible limits and modern hardware can be very fast for small and medium sites. Problems arise when servers are overcrowded or poorly maintained.
Does server location affect speed for Ugandan visitors?
Distance adds some delay, but server quality, caching and a CDN usually matter more. A well configured server abroad can outperform a poor one nearby.
Can a CDN fix slow hosting?
A CDN speeds up delivery of static files such as images and scripts, and some can cache whole pages. It helps, but it cannot fully hide a slow server for dynamic pages and the admin area.
How often should I test my website speed?
Monthly is a good routine, and always after major changes such as a new theme, plugins or a hosting move.
Conclusion
To tell whether hosting is slowing down your website, focus on server response time, test blank pages and the admin area, check resource usage and rule out heavy images and plugins. Gather evidence, then talk to your host. If the problem persists, it may be time to upgrade or move to a faster, better supported hosting service.