Skip to content
Servers

WooCommerce VPS Hosting: When Your Store Needs More Control

In this article7 sections

A WooCommerce store can run on shared hosting for a long time. The point to move to a virtual private server (VPS) is not a particular number of products or a sudden spike in visitors; it is when your store needs resources, background jobs, or configuration that your shared plan cannot reliably provide. This guide explains what WooCommerce VPS hosting changes, how to choose a sensible starting size, and what to check before moving a live shop.

If you are still validating a small catalogue, shared hosting may be enough. If the store already takes regular orders or you need control over PHP, Redis, cron and background work, compare the Siteharbour WooCommerce VPS plans below.

Quick plan recommendation: VPS-2 (4 vCores, 8 GB RAM, 75 GB NVMe) is the practical starting point for most live stores. Choose VPS-1 (2 vCores, 4 GB RAM, 40 GB NVMe) for a lean new store or staging environment. Move to VPS-3 (6 vCores, 12 GB RAM, 100 GB NVMe) when a large catalogue, B2B pricing, logged-in traffic, or heavier order bursts need more headroom. Choose VPS-2 for a live WooCommerce store or compare all WooCommerce VPS plans.

What WooCommerce VPS hosting gives you

A VPS gives your site a defined share of CPU and memory and, depending on the service, administrator access to its operating system and web stack. That control can help you tune PHP workers, database settings, object caching, scheduled tasks, and monitoring around a busy store. It also means that server updates, security, backups, and recovery need an owner. A VPS is not automatically faster simply because it is called a VPS; the software configuration and the work performed by each page request still matter.

Store pages are a mix of cacheable and personal data. Product and category pages can often be cached, while cart, checkout, account, and other session-specific pages must stay dynamic. A cache rule that serves one shopper another shopper’s cart is a serious functional and privacy problem. Test logged-in and logged-out journeys after changing any page cache or CDN rules.

WooCommerce also performs background work. Order emails, stock changes, webhooks, scheduled sales, subscription renewals, and Action Scheduler jobs all compete with normal page requests. On a small store, defaults may be fine. On a store with imports, many plugins, or bursts of orders, inspect the pending-action queue and slow requests before choosing more hardware. A larger VPS cannot repair a broken plugin or an unindexed database query.

Shared hosting or a VPS: which fits?

Choose shared hosting when Consider a VPS when
You are launching or testing a modest store, traffic is predictable, and the plan supports the required PHP and database versions. Traffic and order bursts cause resource limits, slow admin screens, or timeouts that remain after basic plugin and database tuning.
You want a control panel and provider-managed server components with minimal maintenance. You need root access, custom services, Redis, specific PHP-FPM settings, or more control over scheduled tasks.
Your workload fits within the account limits and occasional background tasks complete on time. Imports, integrations, a large catalogue, or frequent asynchronous jobs need more predictable resources.

Shared hosting is not inherently unsuitable for WooCommerce, and VPS hosting is not a ranking signal. Start with evidence: check server resource usage, PHP errors, slow queries, plugin activity, and the time taken for a real checkout. Review the WordPress hosting overview if your main question is how the platform is supported, then compare hosting options based on the limits you actually encounter.

If you are weighing the lower-maintenance starting point against a server, read our companion guide to WooCommerce shared hosting for plan checks, account limits, and a move-up checklist.

How much VPS capacity does a WooCommerce store need?

Think in terms of concurrent work, not monthly visitors alone. A product page served from cache can be inexpensive; a busy checkout that runs tax, shipping, fraud, inventory, and payment logic is more demanding. Imports and scheduled actions add their own load. The number of active plugins, image sizes, search features, and external API calls can change the picture substantially.

  • Small store or staging: a modest VPS may be enough for a lightly loaded shop, development, or a migration rehearsal. Leave memory for the operating system, database, web server, and monitoring; do not assign all RAM to PHP.
  • Production store with steady orders: choose room for PHP workers and the database to handle overlapping customer requests, then measure during normal and peak periods.
  • Large catalogue, promotions, or B2B: plan a load test, monitor checkout response times and queue backlog, and consider separating database or cache services only when measurements justify the added complexity.

Use this as a starting point, then size for the busiest hour rather than the monthly visitor total. The Siteharbour WooCommerce setup page recommends VPS-2 for a typical live shop and VPS-3 or VPS-4 for large catalogues. It also lists the current price, included traffic for each data-centre region, and setup details at the point of purchase.

Plan Resources Best fit Next step
VPS-1 2 vCores · 4 GB RAM · 40 GB NVMe Staging, a new low-volume store, or a lean catalogue with little concurrent checkout traffic. Choose VPS-1
VPS-2 4 vCores · 8 GB RAM · 75 GB NVMe The default choice for a live store that needs reserved resources for uncached cart and checkout requests. Choose VPS-2
VPS-3 6 vCores · 12 GB RAM · 100 GB NVMe Large catalogue, B2B pricing, busy promotions, many logged-in customers, or heavy product filtering. Choose VPS-3
VPS-4 8 vCores · 24 GB RAM · 200 GB NVMe High-volume workloads or several stores that share one server and have been load-tested together. Choose VPS-4

Not sure between VPS-1 and VPS-2? If customers place orders every day, checkout speed affects revenue, or several plugins run on each order, start with VPS-2. If the shop is still in development or has only occasional orders, VPS-1 keeps the starting cost lower and can be upgraded in place as demand grows. Do not choose VPS-3 just because the catalogue has many SKUs: choose it when measured concurrent traffic, memory use, imports, or query load calls for it.

Prepare the server before moving the shop

Check WooCommerce’s current server requirements and match WordPress, PHP, database, and HTTPS support to those requirements before migration. Requirements evolve, and a plugin can impose additional needs. Confirm PHP extensions used by your payment, shipping, and import tools. Keep the PHP version consistent between command-line tasks and web requests where possible.

A sensible production setup includes an actively supported operating system, a maintained web server and PHP runtime, a database with routine backups, HTTPS, a firewall, SSH keys rather than exposed password access where supported, and a documented update process. Restrict administrator access, use unique credentials, and test restoration from backup. Backups that have never been restored are an assumption, not a recovery plan.

Before DNS changes, copy the site and database, lower DNS TTL ahead of time if possible, and test the staging copy. Confirm product pages, variations, coupons, tax, shipping, transactional email, webhooks, and payment gateway callbacks. Freeze orders or plan a final database sync during the switch so new orders are not lost. Keep the old host available until DNS has settled and the new store has passed a real test order.

Keep checkout quick and safe

Enable page caching for public product and category pages only when the cache understands WooCommerce sessions. Exclude cart, checkout, account, and any page that displays customer-specific information. Purge cache after product or pricing changes, and test with two separate browser sessions. A persistent object cache such as Redis may reduce repeated database work, but it needs correct configuration and capacity; it does not replace page caching or database maintenance.

Use image dimensions appropriate to the theme and compress uploads, remove plugins that are no longer used, and investigate slow database queries before installing more optimization tools. Schedule large imports and maintenance outside busy hours. Track uptime, disk space, memory pressure, PHP errors, payment failures, and the Action Scheduler backlog. Set alerts before disk space or queues become an outage.

Common mistakes when choosing WooCommerce VPS hosting

  • Buying far more server than the store can use: begin with measured requirements and leave a clear upgrade path.
  • Assuming a VPS is fully managed: confirm who handles operating system updates, hardening, monitoring, backups, and incidents. Siteharbour can perform initial setup, but ongoing server administration depends on the selected service scope.
  • Caching checkout: this can show stale or another visitor’s session data. Exclude dynamic store pages.
  • Ignoring email and payment delivery: test domain authentication, gateway callbacks, and order notifications after migration.
  • Moving DNS before testing: stage the copy, run a complete order, and have a rollback plan.

When it is time to upgrade

Upgrade when monitoring shows sustained CPU or memory pressure, resource-limit events, slow uncached pages, growing background queues, or failed checkouts that persist after application-level fixes. Keep the measurements and timestamps; they make it easier to choose between adding capacity, tuning PHP and the database, or fixing a plugin. If you need more control over the server or predictable resources for orders, explore WooCommerce VPS hosting. If your store is still small and you prefer a control panel, review shared hosting first.

Ready to move? Most established stores should compare VPS-2 for WooCommerce first; shops with sustained high concurrency or heavy catalogues should review VPS-3. The one-time setup installs and secures the server stack; after handover, the VPS is self-managed. Check the current price, region traffic allowance, and service terms on the WooCommerce VPS page before checkout.

Share this guide