Your WooCommerce store worked fine while you were adding products. Then the first proper week of orders arrived and the checkout started to hang, the admin crawled while you packed parcels, and a customer messaged to say the payment page timed out. The host’s plan page still says “fast WordPress hosting”. So what does hosting for a WooCommerce store actually need that a normal site does not?
This guide answers that without naming a winner. Hosts change, and the right one for a store depends on the store. What does not change is what WooCommerce asks of a server, and how to test whether a plan delivers it.
Why a store is harder to host than a brochure site
On an ordinary business site, nearly every visitor sees the same pages. A cache can build each page once and hand out copies, so the server barely works. A shop is different in a few specific ways.
The pages that matter most cannot be cached
The cart, checkout and my-account pages show different content to each customer, so caching plugins and good hosts deliberately skip them. Every visit to those pages runs PHP and queries the database from scratch. These are exactly the pages where a slow response loses an order.
Customers carry sessions
Once someone adds to cart, WooCommerce tracks them with a session, and their later page views may also bypass the cache. A busy store therefore has many more uncached requests than its visitor count suggests.
The admin is busy too
Order screens, reports, product edits and stock updates all run in the WordPress admin, which is never cached. Two or three staff working at once, during a sale, add real load.
Background jobs run all the time
WooCommerce uses a scheduled task system called Action Scheduler for things like processing webhooks, sending follow-up emails and syncing with other services. Shipping and inventory integrations add their own jobs. These need WordPress cron, or better a real server cron, running reliably.
Payment and shipping services call back
When a customer pays, the payment gateway usually notifies your store in the background to confirm the order. If the server is overloaded or a security rule blocks that request, the money is taken but the order stays “pending”. Our guide to fixing WooCommerce checkout errors covers that symptom from the store side.
What WooCommerce hosting needs, item by item
Use this as your checklist when reading any plan. Ask the host directly for anything not stated.
- Enough simultaneous PHP processes. Called PHP workers, entry processes or concurrent processes. This decides how many uncached requests are served at the same moment, and it is the limit stores hit first.
- Adequate memory per process. WooCommerce and its extensions need more than a plain blog. Check the PHP memory limit you can set.
- A current, supported PHP version that you can switch between yourself, so you can match what WooCommerce and your extensions support.
- A properly tuned database server with fast disk storage. Stores make many small queries.
- Object caching, such as Redis or Memcached, available on the plan. It speeds up the uncached pages by keeping repeated database results in memory.
- Page caching that respects WooCommerce. Server-level caching must exclude cart, checkout, account pages and visitors with cart cookies. Ask how the host handles this.
- Reliable cron or the ability to set a real server cron job, so scheduled actions do not pile up.
- Staging. A one-click copy of the store to test updates. On a shop, updates should never be tried on the live site first.
- Frequent backups, and a clear way to restore them. A store’s database changes with every order, so a backup from yesterday may miss a day of orders. Ask how often the database is backed up and whether you can restore it on its own.
- Working outgoing email, or support for an SMTP or transactional email service, so order emails reach customers.
- Free SSL on every domain and subdomain. Checkout must run over HTTPS.
- A firewall that does not block payment callbacks. Security rules must allow the gateway’s notifications through.
Hosting for a WooCommerce store: which type to start on
A small store with a modest catalogue and steady orders can run well on a good higher-tier shared plan, if the plan’s process limits are clearly stated and generous enough. Once orders come in bursts, staff work in the admin at the same time, or you rely on several integrations, a managed VPS or cloud plan with resources set aside for you becomes the steadier choice. Our comparison of the three main hosting types explains what you take on with each.
“WooCommerce hosting” labels on a plan are marketing, not a standard. Some are genuinely tuned for stores; others are ordinary shared plans with WooCommerce preinstalled. The checklist above is how you tell them apart.
Questions to put to a host before you buy
- How many PHP workers or concurrent processes does this plan allow, and what happens when they are all busy?
- Is Redis or another object cache included, and is it set up for me?
- Does your server cache exclude WooCommerce cart, checkout and account pages automatically?
- Can I run a real cron job instead of WordPress’s built-in one?
- How often are backups taken, how long are they kept, and can I restore just the database?
- Is there staging, and can I push changes from staging to live without overwriting new orders?
- If your firewall blocks a payment gateway’s callbacks, how would I find out and get it fixed?
- Can I upgrade to more resources without moving servers before a sale?
Clear, specific answers are a good sign. “Our hosting is optimised for WooCommerce” with no detail is not an answer.
Test before you trust it
A plan can look right on paper and still struggle. Before moving a live store, or before a sale on the current host:
- Set up a staging copy and walk through add-to-cart, checkout with a test payment, and the account page. Time how long each step feels, not only the homepage.
- Have two or three people use the admin at once while someone else places test orders.
- Check the resource usage graphs during and after the test. If you hit process or memory limits with a handful of people, a real rush will be worse.
- Confirm that order emails arrive and that the gateway marks test orders as paid.
- Look at the scheduled actions list under WooCommerce, then Status, for jobs that are piling up or failing.
A sale is the worst time to discover the limits, which is why our checklist for getting a store ready for a festival sale starts with this kind of test.
When the store is slow but the hosting is not to blame
The host often gets the blame when the cause is inside the store. Before upgrading, look for:
- A heavy theme or page builder loading large scripts on every page, including checkout.
- Many extensions each adding their own database queries.
- Product images uploaded at full camera size.
- Old orders, sessions and logs bloating the database over years.
- An extension that calls an outside service on every page load.
Moving any of these to a bigger server only delays the problem. Measure first: a speed test on a cached product page and an uncached checkout page, plus the host’s resource graphs, usually shows which side the bottleneck is on.
Moving a live store to new hosting
Changing hosting for a WooCommerce store is more delicate than moving a brochure site, because orders keep arriving while you copy. A few habits keep it clean:
- Pick a quiet time of day and week for the final switch, based on your own order history.
- Do a full trial copy first, test checkout on it, then plan a short final sync of the database just before switching DNS, so no orders are left behind on the old server.
- Some owners put the store into a brief maintenance mode during that final sync. Tell customers in advance if you do.
- Your server IP address changes in the move, so check any integration or firewall rule that allow-lists the old IP, and confirm gateway callbacks still reach the store.
- After the switch, place a real low-value order end to end and check it appears in the admin, the gateway dashboard and your shipping tool.
- Keep the old hosting live for a while in case you need to look something up.
What changes the cost of store hosting
Store-ready plans cost more than entry shared hosting because they set aside more memory and processes per account, include object caching, staging and better backups, and often come with support that understands WooCommerce. Managed plans also include someone else’s time keeping the server patched. Compare plans on these items and on the renewal rate, not the first-term discount. Our main guide on web hosting price covers how hosting tiers are usually priced and where the renewal catch sits.
Whatever plan you choose, write down its limits and the date you tested it, so the next comparison starts from facts. If your store is struggling now and you want to know whether the store or the server is the real cause before you spend anything, our WooCommerce support team can look at both with you, and our help with moving hosts covers the switch if a move turns out to be the answer.
If the store is already slow on the hosting you have, start with why a WooCommerce site gets slow before moving.
Next in this series: Website Down Because Hosting Expired? Do This First
