The question of whether it is time to move from shared hosting to a VPS usually arises from a symptom rather than from theory: the store started slowing down at peak hours, or the host sent an email about exceeding a limit. Let us work out when moving genuinely solves the problem and when it just relocates it to a more expensive plan.
What actually limits shared hosting
The limit is not "disk space", as many assume, but three things that are usually invisible in the plan description:
- The number of concurrent processes. A store handles requests in parallel; once the limit is reached, visitors queue. That is exactly where "it only slows down in the evening" comes from.
- CPU time. It is shared with your neighbours on the server. A heavy neighbour makes your store slower with no change on your side at all.
- Access to configuration. PHP version, database parameters, server-level caching — on shared hosting these are either unavailable or decided for you.
When shared hosting is still perfectly adequate
A store with a few hundred products and dozens of concurrent visitors runs fine on shared hosting. If pages are served quickly and outages are not caused by resources, moving will change nothing — it will only add server administration to your responsibilities.
A frequent scenario: the owner moves to a VPS, gets the same four-second load time and concludes that "the VPS did not help". In reality a heavy module or missing database indexes were the cause, and neither disappeared on the new server.
Signs that you have run out of headroom
- The site is noticeably slower at predictable times — evenings, weekends, promotion days.
- The host regularly reports exceeded limits or suspends the site for minutes at a time.
- Price imports or feed generation fail to complete because of execution time limits.
- You need a PHP version or an extension the plan does not offer.
- The catalogue has grown to tens of thousands of items and the admin is now slower than the storefront.
One sign is a reason to investigate. Three or more and the move is already justified.
What a VPS costs if you count honestly
The server itself is usually no more expensive than a decent shared plan. The difference is that on shared hosting administration is included in the price, and on a VPS it is not. System updates, certificates, backups, monitoring, incident response — that is either your time or a separate service.
So an honest comparison looks like this: server cost plus maintenance cost against the price of the plan. If the store generates revenue, the difference pays for itself the first time a peak day is saved; if it is an early-stage project, there is no hurry.
What to do before the move, not after
The worst option is to transfer the store together with its problems and only then start investigating. Before moving it is worth knowing what is actually slow: the server or the store itself. The diagnostic order is described in the article on why a server is slow, and OpenCart's own typical bottlenecks in the guide to store optimization.
The technical side of the transfer — without downtime and with a correct DNS switch — is covered in the article on moving a site to a new server. What to set up on the new server straight away: a control panel, Nginx and PHP-FPM tuned for load, and backups following the 3-2-1 rule.
If you would rather not administer a server yourself, that part is covered by managed store care: updates, monitoring and incident response on our side.
