WooCommerce Hosting Requirements: What a Store Really Needs
A WooCommerce store is not a WordPress blog with a shopping cart bolted on. Every product page, every “add to cart” click and every checkout step runs a database query a static page never has to. Hosting that handles a five-page brochure site comfortably can fall over once the same server processes orders, syncs stock and holds customer sessions at the same time.
Most hosting plans, and most hosting marketing, do not distinguish between the two. A “WordPress” plan and a “WooCommerce-ready” plan are often the same product with different words on the sales page. What actually matters is underneath: memory, simultaneous processes and whether the database is fast enough for a busy checkout. This article is part of GoodHost’s broader WordPress hosting knowledge centre, and focuses on what changes once WooCommerce enters the mix.
Short answer: A WooCommerce store needs more memory, more simultaneous processes and faster database access than a standard WordPress site, because every product view, cart update and checkout step runs database queries in real time. Look at a plan’s resource limits, not its marketing label, before choosing hosting for a store.
What makes WooCommerce heavier on hosting than a normal WordPress site?
WooCommerce adds a large number of database tables and queries that a standard site never touches: products, variations, orders, cart sessions, stock levels and tax calculations, all read and written constantly as customers browse. A brochure site is mostly read-only; a store is read and write, all day.
Every time a shopper adds an item to their cart, WooCommerce writes to the database to remember it, and every product page pulls stock and pricing data live. Multiply that by however many people are browsing at once, and a plan sized for a low-traffic blog runs out of headroom fast on a store with genuine sales.
What resource limits actually matter for a WooCommerce store?
Four things matter most in practice: entry processes, which control how many requests your account can handle at the same instant; RAM, since PHP and the database both need memory to work with; IOPS, the speed at which the storage disk can read and write; and vCPU, the processing power available for calculations like tax and shipping at checkout.
- Entry processes. If this number is too low, extra shoppers queue behind existing ones during a busy period, and pages start timing out.
- RAM. WooCommerce plugins and extensions are memory-hungry compared to a plain blog theme, and low memory shows up as random errors under load.
- IOPS and IO throughput. Every order write and stock update is a disk operation, and a slow disk becomes obvious the moment two or three orders land close together.
- vCPU. Tax calculation, shipping rate lookups and payment gateway communication all use processing power on top of the normal page-building work.
GoodHost publishes these figures directly for its WordPress plans rather than selling by a vague “visits per month” number, which is worth knowing because most hosts do not disclose the underlying limits at all.
| Plan | Price/month + GST | Storage | vCPU | RAM | Entry processes | IOPS |
|---|---|---|---|---|---|---|
| WP 10 | $45 | 10 GB | 400% | 4 GB | 40 | 4,000 |
| WP 20 | $79 | 20 GB | 600% | 6 GB | 60 | 6,000 |
| WP 50 | $169 | 50 GB | 800% | 8 GB | 100 | 8,000 |
Does storage space matter as much as processing power?
Less than people expect, unless you sell a large catalogue with a lot of product images. A store with 50 products and standard photos will not fill 10 GB quickly, but several thousand SKUs with multiple images per variation will need watching more closely as the catalogue grows.
Processing power and memory tend to be the limiting factor first, since they get hit on every page view, not just when you upload something new. Our guide to real WordPress hosting costs in Australia breaks down how pricing scales with what you use.
Do shared cPanel plans work for a small WooCommerce store?
They can, for a genuinely small store, but with caveats. Shared cPanel hosting uses CloudLinux to isolate each account on a shared server, which helps against other sites’ traffic spikes, but the resource ceiling is generally lower than a dedicated WordPress container plan.
A store doing a handful of orders a week can often run acceptably on a mid-tier shared plan. Once order volume grows, or you add extensions like subscriptions or bookings, the database load usually outgrows shared hosting, and a container plan starts to make more sense.
What happens if the store outgrows its hosting?
The usual symptoms are slow checkout, product pages that time out during busy periods, and the site becoming unresponsive right when a sale drives extra traffic, exactly the worst time for it to happen. These are resource problems, not bugs, and no amount of plugin tweaking fixes a plan genuinely out of headroom.
If your site is already slowing under normal load, it is worth ruling out the non-hosting causes first. Our article on why a WordPress site actually slows down covers plugin bloat and database clutter before you assume the plan itself is the problem.
How do you choose the right plan size for a new store?
Start with your realistic traffic and catalogue size rather than the biggest plan available, and plan to move up a tier as the store grows. A new store with under 100 products and modest traffic will usually be comfortable on an entry-level plan; one expecting real order volume from the outset should size up.
- Estimate your product count and whether you expect significant traffic spikes around sales.
- Check whether the plan states real resource limits or only a vague visits figure.
- Confirm the plan runs one site per account rather than sharing resources with unrelated sites.
- Leave room to upgrade without a full migration, since pro-rata billing makes stepping up mid-term straightforward.
It is also worth understanding what a hosting plan’s stated visit allowance actually means in practice, since that figure gets thrown around a lot in comparisons. Our explainer on what happens when a WordPress plan hits its visit limit covers that directly.
Frequently asked questions
Do I need a dedicated WooCommerce hosting plan or will normal WordPress hosting work?
A WordPress-specific plan with adequate memory, entry processes and IOPS will run WooCommerce fine. There is no strict technical requirement for a plan labelled specifically “WooCommerce hosting”, as long as the underlying resources are sufficient for your order volume and catalogue size.
How many products can a small hosting plan realistically handle?
There is no fixed number, since it depends on image sizes and traffic as much as product count, but a few hundred products with standard photos is generally comfortable on an entry-level WordPress plan for a low-to-moderate traffic store to run.
Does WooCommerce need a specific PHP memory limit?
WooCommerce’s own documentation recommends a reasonably generous PHP memory limit, and running short on memory tends to show up as random 500 errors, particularly on the checkout or when extensions are active. A plan with adequate RAM behind it avoids this.
Can I run WooCommerce on shared hosting during a sale event?
You can, but a sale event is exactly when resource limits get tested hardest, since traffic and order volume spike together at the same time. If sale periods matter to your business, size your hosting for the busy day, not the average one.
Does the number of installed extensions affect hosting requirements?
Yes. Each active extension, subscriptions, bookings, a particular payment gateway, adds its own database queries and memory use on top of core WooCommerce, so a heavily extended store needs more headroom than a store running the plugin on its own.
Work out your product count and expected order volume first, then check that against a plan’s published limits rather than its marketing. GoodHost’s performance hosting page lists the specs for exactly that comparison.