When to leave shared for a VPS

You leave shared for a VPS when you need root access, a custom daemon, guaranteed CPU cores, or you have measured CloudLinux LVE limits during real customer traffic. The shared vs VPS choice should rest on numbers from your own site, not on a blog post or a sales pitch. Fix open doors like xmlrpc first, cache the public pages, and only then decide whether the plan itself is the bottleneck.

Shared hosting at LogicWeb runs cPanel with LiteSpeed and CloudLinux LVE. You do not get root on shared. A well-cached store on LiteSpeed can still outperform a neglected VPS. Moving up means a different kind of machine with root and full control, not a faster twin of the same account.

Reasons that actually justify a VPS

LVE limits that hit while real customers are browsing or checking out are a solid signal. So is a need for Docker, a non-PHP daemon, or an extra IPv4 address you must control for rDNS. A custom kernel or anything Windows-related also cannot run on shared. Those needs point to a VPS with KVM and root.

CPU spikes from bots hitting xmlrpc.php are not a plan problem. That is an endpoint you can close. Slow wp-admin with a fast homepage usually means PHP workers or a heavy plugin, not the shared SKU. Address those first, then re-check resource usage.

Problems a VPS will not fix for you

Competitor “unlimited” claims, a page builder shipping megabytes of JavaScript, two cache plugins fighting each other, and oversized images do not improve because you gained root. They improve when you fix them, and that work is often easier on shared where LiteSpeed and caching are already in place. Closing xmlrpc and rate-limiting wp-login costs less than a migration and often removes the pain that felt like “we outgrew shared.”

curl -sI https://example.com | grep -iE ‘HTTP/|server|x-litespeed-cache|x-lsadc’

On a logged-out homepage you want a cache hit and a steady TTFB. Then open wp-admin and compare. If both are slow on shared, the same plugin stack will stay slow on a VPS. Save both responses so you can tell whether you outgrew the plan or a plugin.

Measure first, then choose the tier

Export about twenty minutes of Resource Usage from a normal busy window, not during a plugin update. If CPU is quiet but PHP is at max children, you are worker-bound or lock-bound. If RAM is the cap, object cache and image work often help more than a move. When you truly need root, start with the smallest VPS that fits your workload and keep a snapshot.

Leave the shared account active until the VPS answers on a public resolver and from a phone on cellular data. Canceling shared the same afternoon you change nameservers removes your easy rollback. Cached shared hosting is enough for many real shops. Take a VPS when you can name the need for root or isolation. Dedicated hardware is a later step, after a bottleneck you already measured on a VPS and still cannot fit.