An online store needs more from its hosting than a brochure site does. Every cart, checkout and account page is unique to the shopper, so it can’t be served from cache. That puts the load on PHP and the database, and every order is data you can’t afford to lose. Good WooCommerce hosting gives you spare server capacity, a fast database, reliable scheduled tasks, payment-aware security and backups far more often than once a day.
Key takeaways
- Cart, checkout and My Account must never be cached, so they run on raw server power.
- WooCommerce now asks for PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6, and 256 MB of memory.
- Use a hosted payment form such as Stripe’s, so card numbers never touch your server.
- A daily backup can lose a day of orders. Busy stores need backups every few hours.
- Host close to your customers: for an Australian store, that means Australian servers.
How is a store different from a brochure site?
A brochure site shows the same pages to everyone. The server can build each page once, save a copy and hand that copy to every visitor. That’s caching, and it’s why a small site on modest hosting can still feel fast.
A store can cache its home, category and product pages. But the moment someone adds to their cart, logs in or checks out, each page has to be built fresh for that shopper. Every order also writes to the database, sends emails and triggers stock updates. The busier the store, the more of this uncached work the server has to do at once.
What does WooCommerce need from a server?
An uncached cart, checkout and account area
WooCommerce’s own guide says Cart, My Account and Checkout “need to stay dynamic”, because they show information specific to the current customer (WooCommerce Developer Docs). Caching them can show one shopper’s cart to another. The same guide lists cookies, such as woocommerce_items_in_cart, that should bypass the cache.
It also warns that some hosts’ server-side caching doesn’t exclude the My Account page, which can trap customers in a password reset loop. Ask your host exactly what its cache skips.
Current software and enough memory
WooCommerce’s current requirements are PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or newer, HTTPS, and a WordPress memory limit of at least 256 MB (WooCommerce). Older versions still work, but WooCommerce warns they’re end-of-life and a security risk.
Memory is only part of it. Each uncached page ties up a PHP process until it finishes. If ten shoppers check out while a bot crawls your catalogue, a plan with too few CPU cores makes everyone wait.
A fast, tidy database
Orders, sessions and stock all live in the database. WooCommerce’s High-Performance Order Storage moves orders out of the general WordPress tables into their own, which means “fewer read/write operations and fewer busy tables” (WooCommerce Developer Docs). It’s been on by default for new stores since WooCommerce 8.2 in October 2023. Older stores may still need to switch it on.
Scheduled tasks that actually run
WooCommerce relies on scheduled jobs for things like cancelling unpaid orders, sending follow-up emails and syncing stock. By default, WordPress runs these jobs only when someone loads a page. The WordPress.org handbook recommends using the server’s own task scheduler instead, which also reduces “extra resource usage” (WordPress.org).
How does PCI DSS affect store hosting?
PCI DSS is the card industry’s security standard, and any business that takes card payments must comply. How much work that means depends on whether card details touch your server. Stripe notes that handling card data directly can mean “more than 300 security controls”, while its hosted payment fields send card details straight to Stripe (Stripe).
So the hosting rule is simple: never let card numbers reach your server. Use a hosted payment form, keep HTTPS on every page and keep third-party scripts on the checkout to a minimum. You still need to confirm compliance each year. Our guide to PCI compliance for small business covers the paperwork.
How often should a store be backed up?
A brochure site changes when you edit it. A store changes every time someone buys. If your only backup runs at 2am and the site breaks at 4pm, restoring it can wipe out 14 hours of orders, customer accounts and stock changes.
For an active store, look for backups every few hours or hourly, stored off the server, and a restore process that doesn’t overwrite new orders. Before a big update, take a fresh backup. Updates to WooCommerce itself often change the database, which rolling back the plugin won’t undo.
In our experience, this is where stores need more than hosting. WooCommerce maintenance covers updates, checkout testing and restores that keep orders safe.
Does server location matter for an online store?
Yes, because uncached pages can’t be served from a nearby copy. Each cart and checkout request has to travel to your server and back. One recent measurement put the round trip from Sydney to Los Angeles at 136.6 milliseconds, against 9.7 milliseconds from Sydney to Melbourne (HATSnet).
Small delays add up. Deloitte found a 0.1-second mobile speed gain lifted retail conversions by 8.4% (web.dev). Our guide to WooCommerce checkout speed goes deeper on the checkout itself.
What should I ask a host before moving my store?
- Which pages and cookies does your cache skip? Cart, checkout, My Account and the WooCommerce cookies should all bypass it.
- How many CPU cores and how much memory do I get? Look for clear numbers, not “unlimited”.
- Which PHP and database versions do you run? They should meet WooCommerce’s current requirements.
- Can scheduled tasks run on a real server cron?
- How often are backups taken, and can you restore without losing orders?
- Where are your servers? The answer should match where your customers are.
If your store is already slow, our guide to why WooCommerce is slow helps you tell hosting problems from plugin problems.
How our hosting fits online stores
Our WooCommerce hosting runs in NEXTDC data centres in Brisbane and Melbourne, close to Australian shoppers. Every plan sets out its CPU cores, memory and disk, and you can tailor the mix in the plan builder. Business plans add phone support 7 days, and VPS plans suit busy stores that need dedicated resources.
Every plan includes free SSL and free migration, so we move your store for you. Compare our hosting plans to find the right size.
Frequently asked questions
Can I run WooCommerce on cheap shared hosting?
A small store with a few orders a week can. Problems start as traffic grows, because cart and checkout pages can’t be cached and compete for limited CPU and memory. If checkout slows during sales or busy evenings, the plan has run out of room.
How much memory does WooCommerce need?
WooCommerce asks for a WordPress memory limit of at least 256 MB. That’s a minimum for one request. The total memory and CPU cores on your plan decide how many shoppers the store can serve at the same time.
Is a VPS better for WooCommerce?
For busy stores, usually. A VPS gives you dedicated CPU and memory, so other sites can’t slow your checkout. Smaller stores often do well on a good business plan with clear resources. Move up when checkout times slip during peak periods.
Does my host make my store PCI compliant?
No host can do that alone. PCI DSS is a shared responsibility. Use a hosted payment form so card numbers never reach your server, keep HTTPS everywhere, keep plugins updated and complete your annual self-assessment with your payment provider.
Should I use a CDN for my WooCommerce store?
A CDN helps with images, scripts and cached product pages, especially for shoppers far from your server. It can’t speed up the cart or checkout, which still run on your server. Make sure the CDN skips the same pages and cookies as your server cache.
Sources
- Configuring caching plugins, WooCommerce Developer Docs, accessed November 2026
- Server requirements, WooCommerce, accessed November 2026
- High-Performance Order Storage, WooCommerce Developer Docs, accessed November 2026
- Hooking WP-Cron into the system task scheduler, WordPress Plugin Handbook, accessed November 2026
- Integration security guide, Stripe, accessed November 2026
- Sydney to Los Angeles round-trip latency, HATSnet, 20 October 2026
- Milliseconds make millions, web.dev (Deloitte study), 2020