WooCommerce on a VPS: requirements, caching rules and honest advice

When WooCommerce really needs a VPS

A small store with a few dozen products and modest traffic can run on good shared or managed hosting. The signs that you are outgrowing it are practical: the admin dashboard feels slow, checkout times out at peak hours, imports or bulk edits fail, and the host starts throttling your CPU or limiting processes.

Other triggers are a large catalogue, many variations per product, heavy plugins such as subscriptions or multi-currency, and traffic spikes from ads or email campaigns. In these cases dedicated CPU and RAM matter more than a longer feature list. For general WordPress setup details, see our guide on running WordPress on a VPS; this page focuses on what is different for a shop.

WooCommerce VPS requirements

WooCommerce publishes its own minimum requirements, and they change over time, so check the official page for the exact PHP and database versions before you build. As a practical baseline for a live store, plan for the following:

• RAM: 4 GB is a sensible start for a small live shop, and 8 GB or more suits a larger catalogue, many plugins or regular campaigns. Leave room for the database, since it is the busiest part.
• PHP: a currently supported version, with PHP-FPM and OPcache enabled. Old PHP versions are slower and no longer receive security fixes.
• Database: MariaDB or MySQL in a version the WooCommerce requirements page lists, tuned so that its buffer can hold the working set in memory.
• Redis as a persistent object cache, which takes repeated queries away from the database.
• NVMe or other fast SSD storage, because orders, sessions and product lookups are database-heavy.
• HTTPS with an automatically renewed certificate. Checkout without it is not acceptable.

Caching: what to cache and what to skip

Page caching is still your biggest win for catalogue and content pages, but a shop has pages that must never be served from a shared cache. Cart, checkout and the customer account pages are personal, and caching them can show one customer another customer's basket. Good cache plugins and server rules exclude these by default, but verify it, especially if you add a custom setup.

Make sure these things work as intended:

• Exclude the cart, checkout and my-account pages from page cache.
• Skip cache for visitors with a cart cookie or logged-in session.
• Use Redis object cache so dynamic pages stay fast even when they cannot be cached whole.
• Test as a guest and as a logged-in customer: add to cart, apply a coupon, complete a test order.
• Clear or rebuild cache after price, stock and theme changes.

Backups, security and payments

A shop stores orders and customer data, so a lost database costs money, not just time. Take frequent database backups, for busy shops several times a day, and keep copies off the server. Restore a backup to a test server at least once, so you know it works and how long it takes.

Use SSH keys, a firewall that opens only the ports you need, automatic OS security updates and weekly updates of WordPress, WooCommerce and plugins. Keep card data away from your server by using a hosted payment page or a payment gateway that handles card entry, which also keeps your compliance burden lower. A security plugin and a web application firewall in front of the site, for example through a CDN, add another layer.

Managed hosting or your own VPS: honest advice

A VPS gives better performance per unit of cost and full control, but it also gives you the job of server administration. If an outage on a sales day would hurt and you do not have the skills or time to react, managed WooCommerce hosting or a VPS with a managed service plan is the safer option, even if the plan looks more expensive on paper.

When NOT to choose a VPS: if the store is brand new with little traffic, if nobody on your team can manage a server, or if the real bottleneck is a heavy theme or too many plugins. A bigger server will not fix slow code. Profile the store first, remove what you do not need, and upgrade when measurements show the server is the limit.

If you go with a VPS, compare plans in the table below by RAM, NVMe storage and renewal price, not only the first-term offer.