Skip to content
Start a project
← Back to blog Performance · · 7 min read

Should a Small Business Switch Web Hosting When the Website Feels Slow?

Move host when the server itself is slow to respond, unreliable or badly overcrowded. If the server answers quickly but pages still load slowly, the problem is the site: oversized images, a bloated theme or page builder, too many plugins, or third-party scripts such as chat widgets and tracking. A new host will not fix any of those. Moving costs money and can break email and enquiry forms along the way.

The check below is free and takes a few minutes.

How to tell if it is your host or your website

A page load has two parts. First, the server receives the request and starts sending the page back. The time this takes is called time to first byte (TTFB), and it is the part your host has most control over. Second, the browser downloads and runs everything the page needs: images, fonts, theme code, plugin scripts, embedded maps and chat widgets. That part depends mostly on how the site is built, and it is often where most of the load time goes.

Google's free PageSpeed Insights tool reports on both parts.

  1. Open PageSpeed Insights and test your homepage, then your most important service page. Mobile results are shown first. Read those.
  2. If a section of real-user data appears, find Time to First Byte. Google treats roughly 0.8 seconds or less as good and over 1.8 seconds as poor. Many small sites do not get enough visitors for this section to appear. If yours does not, move on to the next step.
  3. Further down, in the diagnostics, look for a warning about server response. Depending on the version, it is labelled "Reduce initial server response time" or "Document request latency". If it appears, the server is slow to answer.
  4. Now look for warnings about the page itself: images that need resizing or compressing, "Avoid enormous network payloads" (which shows total page weight), unused JavaScript and third-party code. These describe the site, not the host.
  5. Run the test again at a different time of day, ideally a busy one such as a weekday morning. A single result can mislead, because shared servers slow down when neighbouring sites are busy.

Reading the results:

  • Server response flagged, page fairly light: the host is the likely bottleneck, and moving can help.
  • Server response fine, page heavy or full of scripts: the site is the cause. Fix the site and keep the host for now.
  • Both flagged: reduce the page weight first. It is often the cheaper job, and a move alone would leave much of the delay in place. Then reassess the hosting.

Treat TTFB as a rough signal rather than a verdict. On WordPress, a heavy plugin can make server response look poor even on decent hosting, because the server is busy building the page before it sends anything. If server response is slow on every page and at every time of day, even on simple pages, hosting is the more likely culprit. If it is slow only on certain pages, look at what those pages are doing.

Two sites that feel equally slow

Both of these are hypothetical examples, but they follow common patterns.

Example A: moving host helps. A plasterer has a five-page brochure site on a cheap shared plan. The pages are light, with a handful of compressed photos, no page builder and few plugins. PageSpeed Insights flags server response whenever it is run on a weekday morning, and less often late at night. The page itself has little to optimise. The delay is the server waiting for its turn on an overcrowded machine, which is exactly what a better host addresses.

Example B: moving host changes little. A builder has a similar-sized site, also on shared hosting, that feels just as slow. Here, PageSpeed Insights shows server response is fine. The homepage, however, carries several large uncompressed photos straight off a phone. It is built with a page builder that loads its own code on every page, and it runs a chat widget, a reviews widget and two tracking scripts. Most of the load time is the browser downloading and running all of that. On a premium host, a 6MB homepage is still a 6MB homepage.

The distinguishing symptom is server response. In A it is slow and the page is light. In B it is quick and the page is heavy. For B, the useful work is resizing and compressing images, removing scripts that are not earning their place and cutting unnecessary plugins. If the theme or page builder accounts for most of the weight, a rebuild may be the honest answer, and hosting changes as part of that rather than as a separate fix. Solid Digital's Astro builds, for instance, start from £699 and serve static pages from Cloudflare, with the hosting listed as free.

Good reasons to move even if speed is fine

A clean speed test is not a reason to stay with a poor host. These problems justify a move on their own:

  • Frequent outages. While the site is down, anyone searching for you gets an error instead of your phone number. If you or your customers notice the site down more than occasionally, that alone is enough to move.
  • No reliable backups. Some cheap plans include no backups, or store them on the same server as the site. If that server fails or the site is hacked, there may be nothing to restore. Check what is backed up, how often and where it is stored.
  • Unhelpful support. When something breaks, response time matters. A host that takes days to reply turns a short outage into a lost week of enquiries.
  • Outdated PHP. WordPress runs on PHP. A host stuck on old versions leaves the site on software that no longer receives security fixes, and newer plugins may refuse to run on it.
  • Renewal price jumps. Introductory prices can rise sharply at renewal. Paying a premium for a poor plan is a fair reason to look elsewhere, as long as the saving outweighs the effort and risk of moving.

What to sort out before you move

Most of the damage in a host move happens to email and enquiries rather than to the website itself. Work through these steps before changing anything:

  1. Confirm who controls the accounts. You need logins for the domain registrar, the current hosting and any separate DNS provider, held in the business's name. If a previous developer set them up under their own account, fix that first. This plain guide to who should own your website domain and hosting accounts explains what to check.
  2. Take a full backup you can actually restore. Include both the site files and the database, and store the backup away from the old server. Do not cancel the old plan until the new site is confirmed working.
  3. Find out where your email lives. If email is hosted with the same company, moving the website can cut it off. Decide where email will go, and record the existing MX, SPF and DKIM records before touching DNS. Treat email as a separate move with its own plan.
  4. Set up SSL on the new host first. The site should load over https without browser warnings from the moment DNS switches.
  5. Lower the DNS TTL a day or so ahead. A short TTL lets the change spread quickly, and lets you switch back quickly if something goes wrong.
  6. Test straight after the DNS change. Load your key pages, submit every contact form and confirm the messages arrive, then send and receive a test email. Check again over the next couple of days, because some visitors will still reach the old server until DNS fully updates.

The decision rule is simple. If the test points at the server, or the host is unreliable, move using the checklist. If it points at the page, spend the money on the site instead. If you would rather not handle the diagnosis or the move yourself, ongoing website management covers both: finding what is actually slowing the site down and moving host without losing email or enquiries.