WordPress Site Slow on Shared Hosting: Upgrade the Host or Fix the Site?
Your WordPress site is slow on shared hosting, with 503 or 508 errors at busy times. Support says to upgrade the plan. You suspect an upsell, and you may be right.
I’ll show you a 10-minute check to make sense of the host’s warnings and decide where to spend: a speed fix, a bigger plan, or a move.
Is shared hosting why your WordPress site is slow?
Shared hosting often isn’t the whole story. In about ten minutes, check the server response, page cache, host’s usage page and wp-admin. No single check proves the cause, but together they help you decide whether to fix the site or pay for more resources.
- Run PageSpeed Insights on your slowest page. If your site has enough visitors, the real-visitor section shows Time to First Byte: Google calls 0.8 seconds or less good and over 1.8 seconds poor. In the lab section, the “Document request latency” insight flags a server that took more than 600 milliseconds to answer.
- Open Tools → Site Health in WordPress. It tells you whether a page cache is detected and whether the server response is slow.
- Look at the host’s emails and usage page. Warnings about resource limits, CPU throttling or 503 and 508 errors matter more than a slow score. On cPanel hosts, the page is called Resource Usage.
- Compare wp-admin with the front end. If the dashboard is slow too, the server or the database is working hard. If only the pages are slow and they carry big images and a page builder, look at the site first.
| What you see | Points to |
|---|---|
| Server answers fast, pages still slow | The site: theme, builder, images, scripts |
| Limit warnings that line up with backups, bots or one plugin | The site, running into the plan’s limits |
| Slow server answer with cache on and a cleaned-up site | The host or the plan |
| Mixed signals | Ask the host which resource hit its limit, what caused it and when |
What the host’s warnings mean
Shared plans cap what one account can use. Hit a cap, and your visitors see errors while the server is fine for everyone else.
| Warning | In plain words |
|---|---|
| 503 Service Unavailable | Often means resources ran out, but it can also be maintenance; ask the host to confirm |
| 508 Resource Limit Is Reached | On cPanel hosts with CloudLinux: too many processes running at once for your account |
| CPU limit or throttling | Your account used its share of processor time |
| Entry processes | How many requests PHP can handle for you at the same moment |
| Memory limit | Your account’s processes together used more memory than the plan allows |
Before you accept an upgrade, ask support in writing which resource hit the limit, which URL or process caused it, and when. A backup at noon, bots on the login page or one plugin needs attention even on a bigger plan. Ask about the PHP version and OPcache too: an old PHP version or a small OPcache can slow wp-admin on its own.
If the server answers fast and the site is still slow, a new host won’t fix it.
The site needs a speed fix first. See what a WordPress speed fix usually costs.
If the site is the problem: what to fix first
The host can’t fix every site problem. I’d look at these causes:
- A heavy theme or page builder A builder that loads its code on every page can cost more than many light plugins. Which plugins you run matters more than how many.
- One plugin that eats the limits A security plugin’s firewall, a related-posts plugin or a stats plugin can run on every request. A free tool like Query Monitor shows which plugin slows a page.
- Cache off, or two caches fighting A cache plugin that sends “don’t cache” headers can switch off the host’s own cache. Run one page cache, the one your host recommends, unless its guide says to pair it with a plugin.
- Bots on the login page or xmlrpc.php Brute-force traffic can keep the CPU busy all day. Your host’s logs show it.
- Backups and scheduled tasks at busy hours A daily backup plugin running at noon can trigger the same resource warning every day. Move it to the night.
- Big images Photos straight from a phone can weigh several megabytes each. Compress them and serve them at display size.
Old PHP is worth fixing too, but carefully. Make a backup, test the newer version on a staging copy first, and on a store test every update there.
A basic speed fix by a Fiverr Pro starts from about $100, plus Fiverr’s service fee; deeper Core Web Vitals work costs more. Judge the result by lab tests of the same pages before and after, plus wp-admin and, on a store, the cart and checkout. One score isn’t enough.
When to upgrade from shared hosting, and how
Upgrade when the site still hits its limits after the fixes, and the host’s logs show which resource runs out. That often happens on a store, where cart, checkout and account pages can’t be cached, so every visit there puts the server to work.
Compare a bigger plan on the same host, a new host and a one-time speed fix:
| Option | What it costs | When it fits |
|---|---|---|
| Stay as you are | Your renewal price × 36 (Hostinger Premium: $10.99 × 36 = $396) | The check found nothing on the host’s side |
| Speed fix | From about $100 once, plus Fiverr’s fee | The check pointed at the site |
| Bigger plan, same host | The upgrade quote in your account, then its renewal | The host is fine, the plan is too small |
| New host | See the picks below | The host’s limits or support are the problem |
The bigger plan has to fix the limit you hit. Hostinger lists Premium at 1 CPU core and 2 GB of memory, Unlimited at 2 cores and 3 GB, and Cloud Startup at 4 cores and 4 GB. SiteGround caps CPU time per hour, day and month: StartUp gets 1,000 CPU seconds an hour, GrowBig 2,000 and GoGeek 4,000. For too many simultaneous requests, ask what the bigger plan changes for that limit, not only CPU.
Ask for the upgrade price in writing. New-customer deals can differ from your account’s upgrade quote for the remaining term and its renewal price.
Where to move: picks by situation
These four fit different situations when the ten-minute check points at the host or an upgrade costs about as much as a move. Each is a step up from basic shared hosting, but a site problem can follow you.
| If you need… | Move to | Intro (term) | Renews at | 3-year cost |
|---|---|---|---|---|
| More resources on a small budget | Hostinger Cloud Startup | $7.99/mo (48 mo) | $25.99/mo | $384 |
| Your own server size, billed monthly | Cloudways (DigitalOcean 2 GB) | $28/mo (monthly) | no first-year discount | $1,008 at today’s price |
| One busy site, unmetered visitors | Rocket.net Starter | $25/mo (yearly) | same price, pledged in writing | $900 |
| One business site with expert support | Kinsta Single 35k | $350/yr (yearly), first month free | no first-year discount | $1,050 at today’s price |
Prices from each host’s pricing page at the time of writing, before tax. Hosts change prices often, so check the total on the checkout page before you pay. The Hostinger cost is the upfront payment for 4 years. The Cloudways cost is the server only; offsite backup storage is billed per GB on top.
Hostinger Cloud Startup gives you 4 CPU cores and 4 GB of memory with daily backups, at the lowest 3-year cost of these four picks. The catch: you pay four years up front, and it renews at $25.99 a month, about three times the intro price.
Cloudways offers a cloud server you pick and resize later, with staging. It bills monthly for hours used, with a free trial and no money-back period. Email is a paid add-on.
Rocket.net Starter fits one busy site: unmetered visitors, 50 GB of bandwidth, 10 GB of storage and daily backups. Rocket.net promises no price hikes on renewal. It doesn’t host email.
Kinsta Single 35k covers one site up to 35,000 visits a month, with 14-day backups and unlimited free migrations. It’s $35 a month if you pay monthly, and billing starts after a free first month. Kinsta doesn’t host email, and visits over the plan are billed as overages.
For more managed picks under $30 a month, see the best cheap managed WordPress hosting. For a store, see the best WooCommerce hosting for a small store.
Before you move: the checklist
The full steps are in how to move WordPress to a new host. These are the safeguards:
- Make your own backup and keep it off the old server. Then do a test restore, not just a check that the archive opens.
- Copy your DNS records from the provider your nameservers point to: A, www, MX, SPF, DKIM and any others.
- Give every mailbox and forwarder a new home if your mail sits on the old host, and point MX to the new mail service while the old host still runs. Add the new mail service to SPF and keep the other senders already in it.
- Test the copy on the new host through its preview link before you switch the domain. On a store, pause orders during the final copy and switch.
- Check the old plan’s renewal date, so it doesn’t auto-renew for another term while you move.
Three ways to move the site
- The new host moves it for free. Hostinger covers the website only, not email, DNS records or cron jobs; Hostinger-to-Hostinger moves don’t qualify. Kinsta lists unlimited free migrations; Cloudways and Rocket.net offer free migration, so ask what it covers.
- Move it yourself with a plugin. Use the migration plugin the new host’s guide names, since plugin archives aren’t interchangeable. It fits a simple site without a store and with mail already sorted.
- Have it done by a Fiverr Pro. For a store with live orders, mail on the old host, a custom setup, or no time.
I recommend Fiverr Pro for a move like this. Fiverr vets Pro freelancers by hand for their experience, portfolio and service record. A WordPress migration there starts from about $100, plus Fiverr’s service fee. Start with a small first order, or for a big move ask for a custom offer split into milestones; each milestone has an eight-day review window.
Keep your own backup and give a separate SFTP user and database access on the new host instead of your main login. Keep the hosting and domain accounts in your name. Find a vetted migration expert on Fiverr. For prices by job size, see what a WordPress migration costs.
After the switch: measure again
Point the domain to the new host: the A records for the root and www, with no old AAAA record left pointing to the old server. If you change nameservers, add the saved records to the new zone first. Then check:
- Confirm SSL is active. Some hosts issue the certificate only after the domain points to them.
- Send a test email from each mailbox, submit each form and, on a store, place a test order.
- Run PageSpeed Insights on the same pages as before and compare the server response in the lab test. The real-visitor data covers 28 days, so it catches up later.
Keep the old host until its traffic drops to zero; I give it a week or two. Then move mail and DNS off the old plan before you cancel it, and turn off its auto-renew.
Summary
A WordPress site slow on shared hosting isn’t always a host problem. Use the ten-minute check and ask which resource hit its limit. Fix the site when the server answers fast; upgrade or move when limits persist after fixes. Measure the same pages before and after.
FAQ
Will upgrading my hosting plan make my site faster?
Only if the plan's limits are the cause. A bigger plan gives backups, bots or a heavy plugin more room without fixing the cause. Ask the host which resource ran out and why.
What does "508 resource limit is reached" mean?
On cPanel hosts with CloudLinux, it means your account had too many processes running at once. Traffic spikes, bots or a slow plugin keeping requests open are common causes. Ask the host which URL or process hit the limit.
Do I need a VPS for WordPress?
Usually not as a first step. A raw VPS means you manage the server yourself. If shared hosting is too small, managed cloud hosting such as Cloudways or Hostinger Cloud gives you more resources without running the server.
Will a CDN fix a slow host?
Partly. A CDN serves images and cached pages from servers near the visitor. Pages that can't be cached, like the cart, checkout and wp-admin, still wait for your server.
Will moving hosts hurt my SEO?
It usually doesn't if the addresses stay the same and the new site works, but there's no guarantee. Keep the same URLs, test the copy before you switch, and watch crawling and traffic in Search Console in the weeks after.