I have a fairly new website hosted on a Canadian shared hosting plan. The plan allows me to run multiple websites, so I recently activated a second one. Since then, both sites have become noticeably slow.
I contacted the hosting company, but it took two days to receive a response, and they said everything was configured correctly. I have removed most of my plugins and optimized the images, and the two sites contain fewer than 200 articles combined. They are mostly informational sites, so I'm unsure what could be causing the slowdown.
I've read that hosting plans may advertise support for several websites without providing separate CPU, memory, disk I/O, or process resources for each one. In that case, active sites would compete for the same account limits, even if the plan technically allows them.
Is that explanation accurate? Where should I start troubleshooting, and how can I determine whether the problem is shared hosting resource limits, oversized pages, plugins, or something else?
5 Answers
There are usually two practical solutions if the account is consistently resource-constrained: place each site on a separate hosting account, or move them to a VPS with enough CPU and memory. A VPS gives you more predictable resources, but it also requires more administration. Before upgrading, it is worth confirming the cause with usage data and checking whether a plugin or scheduled task is consuming resources.
Pay particular attention to image sizes and how much data is downloaded on the initial page load. A page containing many multi-megabyte images can be slow for every visitor, regardless of how small the site’s article count is. Image compression, responsive image sizes, caching, and lazy loading can help if the browser is downloading too much.
The sites could still be generating too much work even with relatively few articles. Use your browser’s developer tools, open the Network tab, and reload a few frequently visited pages. Check the total transfer size, number of requests, slow server response time, and unusually large images or scripts. This can help separate a hosting bottleneck from a page-optimization problem.
A multi-site plan can run several light websites smoothly, so adding a second domain does not automatically prove the host is at fault. Providers often oversell shared infrastructure on the assumption that most sites are idle or low traffic. If both sites became slow at the same time, though, shared account limits or a busy server are reasonable suspects; ask support for actual CPU, memory, I/O, and process-limit information rather than only asking whether the configuration is correct.
That explanation is generally correct. On shared hosting, multiple sites under one account often share the same CPU, RAM, disk I/O, and process limits. The plan may allow several domains, but that does not mean each site gets dedicated computing resources. Check the hosting control panel for resource-usage graphs or throttling notices while the sites are slow. A vague claim that everything is configured correctly does not reveal whether the account is reaching its limits.
That makes sense. I’ll look for the resource graphs and compare them with the times when the sites slow down.
I’ll check the download size of the most frequently accessed pages and see whether any images are much larger than they need to be.