Hosting for WooCommerce Stores: What Actually Matters
What a WooCommerce store needs from its hosting: uncached checkout performance, PHP workers, an object cache, security, backups and room for sales peaks.
An online store is harder to host than a blog. Product pages can be cached, but carts, checkout and account pages are different for every customer, so the server has to build them in real time. When those pages are slow, customers abandon their orders. This guide explains what a WooCommerce store really needs from its hosting.
- Checkout, cart and account pages bypass the page cache, so raw server speed matters more than on content sites.
- Look at PHP workers, memory, an object cache and database performance, not just storage and traffic.
- Security, frequent backups and capacity for sales peaks are part of the hosting decision.
Why stores are different
On a typical blog, most visitors see the same pages, so a page cache can serve them without running WordPress at all. A store has three kinds of traffic:
- Browsing product and category pages, which can usually be cached.
- Cart and checkout, which are personal and cannot be cached.
- Background work: stock updates, order emails, payment callbacks, scheduled actions and reports.
The second and third kinds hit PHP and the database directly. If many customers check out at once, each of them needs a PHP process.
What to look for in store hosting
PHP workers and memory
PHP workers (or entry processes) limit how many uncached requests run simultaneously. If all workers are busy, the next customer waits in a queue or gets an error. Ask hosts how many workers a plan includes and how much memory each can use; WooCommerce’s own recommendations call for a generous PHP memory limit.
An object cache
Redis or Memcached stores database query results in memory, which helps carts, admin screens and logged-in customers. Many managed WordPress hosts include it.
Database performance
Orders, customers and product data grow over time. Fast storage, a current database version and WooCommerce’s modern order storage (High-Performance Order Storage, HPOS) keep queries quick. Clean up old sessions and logs regularly.
Reliable background tasks
WooCommerce schedules many jobs, such as emails and stock updates. Run WordPress cron from a real server cron job so they happen on time, not only when someone visits.
Security
- SSL everywhere, including the admin area.
- A web application firewall and malware scanning.
- Payment through a reputable gateway, so card data never touches your server.
- Two-factor authentication for every administrator and shop manager.
Backups
A store changes every time someone orders. Restoring yesterday’s backup can erase today’s orders. Choose hosting with frequent database backups and know how to restore without losing new orders, for example by exporting recent orders first.
Room for peaks
Campaigns, holidays and social media mentions can multiply traffic. Ask how the host handles spikes: temporary scaling, burst resources or an upgrade path without migration. Load-test before major campaigns if you can.
Which hosting type fits?
| Store size | Common choice |
|---|---|
| New store, few orders a day | Good shared hosting or entry managed WordPress |
| Growing store, regular daily sales | Managed WordPress/WooCommerce plan or managed VPS |
| Large catalogue, frequent campaigns | Cloud or VPS with object cache, scaled resources and monitoring |
For the basics of the three main hosting types, read shared vs VPS vs cloud hosting.
Store-specific speed tips
- Exclude cart, checkout and my-account pages from page caching, and confirm your cache does this automatically.
- Limit heavy plugins on checkout, such as page builders, sliders and chat widgets.
- Optimise product images and limit the number of variations loaded at once.
- Disable cart fragments or similar AJAX calls on pages that do not need them, if your theme allows.
Frequently asked questions
Can WooCommerce run on shared hosting?
Yes, for small stores on a good shared plan. Watch resource usage and checkout speed, and upgrade when they start to suffer.
How many PHP workers does my store need?
It depends on simultaneous uncached requests. Small stores may manage with a few; busy stores with many logged-in customers need more. Your host can show how often workers are exhausted.
Should I use a separate host for the store and the blog?
Usually not necessary. Keeping one well-hosted site is simpler. Split them only if one part has very different traffic or security needs.
