Your site has slowed down and you don't know who's to blame
It's midnight and you've received a message from monitoring: "Error 508". Or maybe a user called to say "the site won't load". The first thought that comes to any manager's mind is: "My hosting is weak, I need to switch services."
Don't be mistaken. In 60% of the cases I've seen in support, the problem isn't the service. It's unoptimized queries, a disabled cache, or a poorly coded plugin. But let's assume you really do need a new service. The question is: which one?
This article is a decision tree. Not a clichéd comparison table. You'll reach an answer with three simple questions.
First question: Do you need root access?
This question determines everything. If the answer is "yes", shared hosting is out of the conversation. Period.
Root access means you can modify the kernel, install specific PHP modules, build the firewall from scratch, or spin up a service like Redis with a custom configuration. Shared hosting doesn't give you this capability because you and 200 other users share a single operating system kernel.
This is where people make mistakes: many think "I just have WordPress, so I don't need root." Until the day a security plugin wants to write to the wp-config.php file with specific permissions and gets a Permission denied error. Or when you want to configure mod_rewrite for a specific path and the host says "this action is not allowed in your plan".
If you need root access, go for a VPS or dedicated server. If not, ask the second question.
The difference between a VPS and a dedicated server lies right here
A VPS is a virtual machine on a shared physical server. You have root access, but resources (CPU and RAM) are shared with a few other people. A dedicated server is a complete physical machine that belongs only to you.
The choice between these two depends on one number: sustained resource consumption. If your site consistently uses an average of 4 cores and 8 GB of RAM, a VPS with 8 GB of RAM will suffice. But if your usage fluctuates — for example, 2 GB one hour and 12 GB the next — you'll run into problems on a VPS because your neighbors are also putting pressure on the same physical resources.
Second question: How much monthly traffic do you have?
Give the exact number, not "a lot" or "a little". Get a report from Google Analytics or your current host's cPanel.
- Under 50,000 visits per month: Quality shared hosting is sufficient. Provided you get it from a reputable provider, not the cheapest option on the market.
- Between 50,000 and 300,000 visits: This is the gray area. If your site is WordPress with 20 plugins, forget shared hosting. If it's a static site or an optimized framework, shared hosting still works.
- Above 300,000 visits: Move to a VPS. This number, with a typical WordPress site meaning roughly 3 to 5 requests per visit, will easily burn through the resources of shared hosting.
A technical note: don't rely on "visits", look at "requests per second" (RPS). A news site with 100,000 visits per day might have 50 RPS, while an e-commerce store with 10,000 visits might hit 200 RPS due to AJAX requests and images.
Third question: How "live" is your site?
By "live", I mean user interaction with the server. You have three states:
- Content site: The user comes, reads the content, and leaves. The main load is on reading from the database and sending HTML. Shared hosting with proper caching handles this well.
- E-commerce store: Shopping cart, payment gateway, product search, inventory updates. Each of these is a separate database request. Here you need a VPS with at least 4 GB of RAM, especially if you're using WooCommerce.
- Application or online service: If your users log in, store data, or interact with each other (like forums, chat, or SaaS tools), get a VPS from day one. Shared hosting wasn't built for this.
A simple metric: if your site converts more than 10% of its visitors into "registered users", that means high interaction and you need more dedicated resources.
This is where they make mistakes: aimless upgrades
The common pattern I see every day: the site is slow, the manager upgrades the hosting to a higher plan without investigation. Two weeks later, it's slow again. Then they get a VPS. Still slow.
Then they submit a ticket: "Your VPS is weak."
I look. CPU usage is below 20%. Half the RAM is empty. The problem is max_execution_time cutting off a specific script, or the lack of opcache causing PHP to recompile every time. Upgrading the service solves none of these.
Before any upgrade, do these three things: enable opcache, turn on page caching, and examine heavy database queries with EXPLAIN. If it's still slow after these, then change the service.
Quick decision table
| Your situation | Recommended service | Reason |
|---|---|---|
| Content site, under 50K visits, no need for root | Shared hosting | Lower cost, easier management |
| E-commerce store, under 100K visits | Strong shared hosting or small VPS | You need stable resources for the database |
| Any site with root access needs | VPS | Full control, reasonable cost |
| Application, sustained usage above 80% of VPS resources | Dedicated server | Neighbor fluctuations on a VPS will harm you |
| Site with seasonal traffic (like a store during holidays) | VPS with temporary upgrade capability | For 3 peak months, a dedicated server is a waste of money |
An honest recommendation about cost
A VPS is more expensive than shared hosting, but not as much as you think. The difference is usually 2 to 3 times, not 10 times. If your site generates revenue, compare this difference to one day of your site being down.
On the other hand, a dedicated server is only justified when your sustained usage exceeds the capacity of a large VPS. Otherwise, you're paying for hardware that's 70% idle.
If you're just starting out and unsure, begin with a quality Linux hosting. Later, when you grow and need root access, migrating to a VPS isn't difficult. Read the migration to ServerNet documentation to do it without downtime.
Frequently asked questions
What's the practical difference between shared hosting and a VPS?
With shared hosting, you share a single operating system with dozens of other users and have no root access. With a VPS, you have an independent virtual machine with full root access, but physical resources are shared with a few others. If your neighbor on the same physical server has high usage, it may affect your performance.
When should I migrate from shared hosting to a VPS?
When you see three signs simultaneously: your hosting's CPU usage is consistently above 80%, 508 or 503 errors have increased, and you need to install software or make a change that the host doesn't allow. If you only have one of these, optimize first.
Is a dedicated server always faster than a VPS?
No. A good VPS on NVMe is practically faster than an old dedicated server with an HDD. Speed depends on the hardware generation and disk type, not just on being dedicated. The advantage of a dedicated server is stability, not necessarily raw speed.
For a beginner WordPress site, what service should I get?
Shared hosting. WordPress with proper caching and a reputable host easily handles up to a few hundred thousand visits per month. Just make sure your host has PHP 8.2 or higher and NVMe. Be sure to ask about these two before purchasing.