Hosting · Explainer
When Should You Move Off Shared Hosting?
Short answer
Move off shared hosting when your site keeps hitting CPU, memory or visit limits, when pages stay slow after caching and image fixes, or when a store, membership site or busy blog needs more steady speed. One bad day is not enough on its own. A pattern over 2 to 4 weeks, with the same limit reached again and again, is the real sign.
Key takeaways
- Shared hosting means many sites share one server, so your neighbours can affect your speed.
- Repeated CPU or memory limit warnings over 2 to 4 weeks are a stronger sign than one slow day.
- WordPress.org recommends PHP 8.3 or newer as of November 2026, with MariaDB 10.11 or MySQL 8.4.
- WooCommerce 10.8 and later asks for a WordPress memory limit of 256 MB or more.
- A good Core Web Vitals result needs LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
- Back up the full site and files before any move, and check the new host after the move.
What is shared hosting?
Shared hosting is a plan where many websites share one server and its CPU, memory and disk.
That sharing keeps prices low and setup simple. It also means one busy neighbour can slow your site at peak times.
A shared plan suits a small blog, a brochure site or a new store with light traffic. It suits them until the site needs more steady speed or more control than the plan allows.
When should you move off shared hosting?
Move when the same limit keeps stopping your site over 2 to 4 weeks, not after one bad day.
Look for a pattern. Repeated limit warnings, slow admin pages, failed updates and downtime during normal traffic all point the same way.
If caching, smaller images and fewer plugins do not fix the problem, the plan itself may be the ceiling. How many visitors shared hosting can handle helps you set a realistic traffic expectation before you judge the plan.
How do CPU and RAM limits show you have outgrown shared hosting?
CPU and RAM limits show it when your host reports them often, or throttles your site during normal use.
CPU seconds measure how much processor time your site uses. RAM is the short-term memory each PHP process can use. When either runs out, pages load slowly or return errors.
SiteGround publishes clear limits in its fair-use page, as of November 2026. Its StartUp plan allows 1,000 CPU seconds per hour, 10,000 per day and 300,000 per month.
GrowBig allows 2,000 per hour, 20,000 per day and 600,000 per month. GoGeek allows 4,000 per hour, 40,000 per day and 800,000 per month, and SiteGround allocates up to 768 MB of RAM per process. See the SiteGround fair-use limits for the full table.
| SiteGround plan | CPU seconds per hour | CPU seconds per day | CPU seconds per month |
|---|---|---|---|
| StartUp | 1,000 | 10,000 | 300,000 |
| GrowBig | 2,000 | 20,000 | 600,000 |
| GoGeek | 4,000 | 40,000 | 800,000 |
Other hosts use different names for the same idea. Some call them CPU minutes, entry processes or PHP workers. How to read a hosting plan's CPU and RAM limits explains those terms in plain language.
Check your host panel for a resource graph before you decide. A flat line near the top each day is a sign. A single spike after a post goes viral is not.
How do slow pages and Core Web Vitals point to a move?
Slow pages point to a move when they stay slow after caching, image work and plugin cleanup.
Core Web Vitals are three Google measures of real visits: loading, response and visual stability.
Google's web.dev guide sets good targets of LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less, judged at the 75th percentile of page loads split across mobile and desktop. See web.dev on Web Vitals for those targets.
Google Search Central gives the same targets in its own words. Its page says Core Web Vitals measure real-world user experience for loading, interactivity and visual stability, with LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. See Google Search Central on Core Web Vitals for the full page.
Use Search Console to see field data from real visits. Lab scores from one test run can look fine while real visitors on phones still wait.
What to fix before you blame the host
- Turn on page caching and check it serves cached pages to logged-out visitors.
- Shrink images and serve them at the size the page shows.
- Remove plugins you do not use and replace heavy ones with lighter options.
- Check for a plugin or theme that runs slow database queries on every page.
If those fixes leave the same pages slow, the server may be the limit. A CDN can help with static files, but it cannot fix slow PHP on the origin server.
Cloudflare explains that its Automatic Platform Optimization service can cache HTML at the edge, while Cloudflare normally caches only static content. Logged-in or administrator users bypass that cache so private content is not served to other visitors. See Cloudflare on Automatic Platform Optimization for how it works.
When does traffic growth force a move?
Traffic growth forces a move when normal days, not just spikes, push your site over its visit or CPU ceiling.
A launch, a sale or a viral post can overload any plan for a few hours. That is a spike. Steady growth is different: daily visits rise, the resource graph stays high, and slowdowns happen at the same time each day.
Watch three numbers for 2 to 4 weeks. Daily visits, peak visits per hour and CPU use tell you more than a monthly total.
If the plan caps visits, ask what happens at the cap. Some hosts throttle the site, some charge extra, and some show errors. The answer matters more than the headline visit number.
A bigger shared plan can buy time. It can also be the wrong buy if the next tier still shares the same crowded server type. How to choose WordPress hosting walks through the plan types to compare.
When does a store or membership site outgrow shared hosting?
A store or membership site outgrows shared hosting when checkout, login or member pages stay slow because they cannot be cached.
Cached pages skip PHP and the database. Checkout, cart, account and member-only pages cannot use that shortcut. Every visit to those pages runs PHP, reads the database and uses memory.
WooCommerce sets a clear floor for stores.
Its server recommendations for WooCommerce 10.8 and later, updated 25 May 2026, ask for WordPress 6.9 or greater and PHP 8.3 or greater tested up to PHP 8.4.
They also ask for MySQL 8.0 or greater or MariaDB 10.6 or greater, HTTPS support and a WordPress memory limit of 256 MB or greater. See WooCommerce server recommendations for the full list.
A store also needs room for orders, search and reports at the same time. A membership site needs the same room for logins, lesson pages and member search. If those pages slow down while blog posts stay fast, the uncached pages are the clue.
How do PHP and database versions factor in?
PHP and database versions factor in when your host cannot offer a supported version, or will not let you switch to one.
WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, plus HTTPS support, as of November 2026.
WordPress still runs on PHP 7.4 and MySQL 5.5.5, but WordPress.org warns those versions have reached end of life and may expose your site to security issues. See WordPress.org requirements for the current list.
PHP itself gives each branch 2 years of active support, then 2 years of security fixes only.
The php.net table shows security support ending 31 December 2026 for PHP 8.2, 31 December 2027 for PHP 8.3, 31 December 2028 for PHP 8.4 and 31 December 2029 for PHP 8.5. See php.net supported versions for the dates.
An old PHP version is not proof that the host is bad. It is a warning when the host offers no newer version, or when switching breaks the site because the plan lacks a staging copy to test on.
How do security, backups and support limits factor in?
Security, backup and support limits factor in when the plan leaves gaps you cannot close yourself.
Shared hosting should include automatic updates for the server, isolation between accounts and a way to restore a backup. Ask how often backups run, how long they are kept and whether you can download a copy.
WordPress includes a built-in Site Health screen at Tools > Site Health.
WordPress.org says it checks the overall health of your site and reports critical issues, recommended improvements and technical detail, with Status and Info tabs. Site Health was added in WordPress 5.2. See WordPress.org on Site Health for what it checks.
Open Site Health and read the Info tab before you move. It lists your WordPress, PHP and database versions, memory limit and server details in one place. Copy that page into your notes so you can compare the old and new hosts.
Support matters too. If every limit question ends with an upsell and no clear number, that is a sign. A good host can state the CPU, memory and visit limits in plain numbers.
What should you check before you move?
Check the backup, the new plan limits, staging and the move steps before you pay for a new host.
Start with a full backup you have downloaded, not only a backup stored on the same server. A move without a tested backup is a risk you do not need.
Then compare the new plan on the same terms as the old one. Ask for CPU, RAM, PHP workers, visit limits and storage in writing. Is managed WordPress hosting worth it explains what managed plans add and what they do not.
Ask whether the new host offers a staging site. A staging site is a private copy of your site where you test changes before they go live. Test the PHP switch and the plugin updates there first.
Plan the move for a quiet time and keep the old site live until the new one passes checks. Check the home page, one post, search, login, checkout and a form after the move. How to change hosts without losing SEO covers the checks that protect search traffic during a move.
What are common myths about leaving shared hosting?
The most common myth is that a bigger plan always fixes slow pages.
A bigger shared plan gives you more of the same shared resource. It helps when you were close to the old limit. It does not help when a plugin, a theme or an uncached page is the cause.
Another myth is that a CDN removes the need for a better host. A CDN speeds up static files such as images, CSS and JavaScript. It does not run your PHP or your database queries.
A third myth is that moving hosts is the same as fixing security. A new host can add server patches and isolation. It cannot fix an old plugin, a weak password or a site that has no backup.
What mistakes should you avoid?
Avoid moving without a backup, a staging test or a check of the new plan limits.
- Moving after one traffic spike without checking 2 to 4 weeks of resource data.
- Picking a new host on price alone without asking for CPU, RAM and visit limits.
- Skipping the backup, or leaving the only backup on the old server.
- Moving during a sale, launch or busy season without a staging test first.
- Forgetting to check checkout, login, search and forms on the new host.
- Leaving the old site and its DNS settings in place with no plan to close or cancel it.
Frequently asked questions
Can I stay on shared hosting if my site is small?
Yes, if your site is small and steady. A small blog or brochure site with light traffic and few uncached pages often runs fine on shared hosting. Stay while pages load well, Site Health shows no critical issues and you rarely hit a resource limit.
How long should I watch resource use before deciding?
Watch it for 2 to 4 weeks. That window shows whether the problem is a one-off spike or a daily pattern. Note the date, time and limit reached each time, then compare the pattern with the plan limits your host states.
Will a CDN let me stay on shared hosting longer?
A CDN can help, mainly for static files such as images, CSS and JavaScript. It does not run PHP or database queries, so it cannot fix slow checkout, login or member pages. If those pages are the problem, a CDN alone is not enough.
Do I need a VPS or managed hosting after shared hosting?
Not always. A higher shared plan, a cloud plan or managed WordPress hosting can each be the next step. The right choice depends on your traffic, your store or membership needs and how much server work you want to do yourself.
What should I back up before moving hosts?
Back up the full site: files, themes, plugins, uploads and the database. Download a copy to your own computer or separate storage, not only to the old server. Keep that copy until the new site has passed all your checks.
Will moving hosts hurt my search rankings?
A careful move should not hurt rankings on its own. Keep the same URLs, check redirects, confirm the site loads fast on the new host and watch Search Console for crawl errors. A rushed move with broken pages or long downtime is what causes harm.
Sources
- Requirements WordPress.org
- PHP: Supported Versions php.net
- WooCommerce Server Recommendations WooCommerce
- Web Vitals web.dev
- Understanding Core Web Vitals and Google search results Google Search Central
- What is a Fair Use of SiteGround Web Hosting Services? SiteGround
- Site Health: keep your website healthy WordPress.org
- Automatic Platform Optimization: About Cloudflare
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
