WooCommerce Hosting Requirements: Why Shared Hosting Fails Online Stores

Most WooCommerce hosting requirements published online stop at the minimums: a PHP version, a database version, an SSL certificate. Those numbers get a store installed, but they say nothing about whether it survives a Friday promotion with 300 people in the cart. Shared hosting usually clears the minimums and still fails online stores, and the reason is architectural rather than accidental.

This post covers what WooCommerce genuinely needs to run well, the specific bottleneck that breaks shared plans, and how to tell when your store has outgrown its server.

The official WooCommerce requirements, and what they leave out

WooCommerce publishes a modest baseline in its server requirements documentation: PHP 7.4 or higher, MySQL 5.7 or MariaDB 10.5 or higher, a WordPress memory limit of at least 256 MB, and HTTPS support. Those are floors, not recommendations. A store running on the floor behaves like a car idling in first gear.

For a real store in 2026, the practical spec sheet looks different:

• PHP 8.3 or newer with OPcache enabled, which typically handles 2x to 3x the requests per second of PHP 7.4 on identical hardware. Our breakdown of why PHP 8.3+ is mandatory for WordPress performance goes deeper.
• MySQL 8.0 or MariaDB 10.6+ on dedicated resources, with InnoDB and enough buffer pool to hold the working set in memory.
• 512 MB to 1 GB PHP memory limit, because WooCommerce plus a payment gateway, a shipping calculator and a page builder routinely pass 256 MB.
• Redis or Memcached object caching, which is the single biggest win for logged-in and cart traffic.
• A real cron system, since WP-Cron fires on page loads and stalls scheduled orders, subscription renewals and stock syncs.
• Server-level page caching with cart and checkout exclusions, plus HTTPS and a modern TLS configuration.

The bottleneck nobody advertises: PHP workers

A blog page can be cached once and served to ten thousand visitors as a static file. A WooCommerce cart cannot. Cart, checkout, my-account and any page showing personalised pricing must be generated fresh, per visitor, by PHP, which means they consume a PHP worker for the full duration of the request.

Here is the arithmetic that decides whether your store stays up. If a checkout request takes 800 ms and your plan allows 4 concurrent PHP workers, the ceiling is roughly 5 uncached requests per second. Every request past that queues, and queued requests turn into 504 errors and abandoned carts. Shared hosting rarely publishes worker counts at all, which should tell you something.

Add AJAX to the picture and it gets worse. WooCommerce fires admin-ajax.php or Store API calls for cart fragments, live search and variation switching, so a single shopper browsing three product pages can trigger a dozen uncacheable PHP hits.

Why shared hosting fails online stores specifically

Shared hosting works fine for brochure sites and low-traffic blogs. It struggles with commerce for reasons that have little to do with the price tag.

For a closer look at this topic, see our guide: Dedicated vs. Cloud Hosting for Growing WooCommerce Stores.

We cover this topic in more depth in Scaling WooCommerce for Black Friday: A Hosting Architecture Guide.

We cover this topic in more depth in How to Speed Up the WooCommerce Checkout Process on Mobile.

• Noisy neighbours. Hundreds of accounts sit on one machine, and a neighbour’s runaway backup script eats the CPU your checkout needed. If you have ever chased phantom slowdowns, our guide to debugging high CPU usage shows how to prove it.
• Hard CPU and entry-process limits. Most cheap plans throttle or suspend accounts that exceed a quota, and a flash sale is exactly the moment you exceed it.
• Shared database servers. WooCommerce writes constantly to orders, sessions and stock tables, and write contention on a busy MySQL host shows up as slow admin screens first, then failed orders.
• Caching that cannot help. Shared hosts lean on page caching for their benchmarks, and page caching is switched off for the exact URLs where money changes hands.
• Bandwidth promises with fine print. The truth about “unlimited bandwidth” is that the limiting factor was never bandwidth, it was CPU and I/O.
• Crawl and index side effects. Slow, error-prone responses reduce how much Googlebot fetches, and shared hosting can quietly damage your crawl budget while product pages sit unindexed.
• Thin security posture. Shared environments often lack a managed WAF, isolated file permissions and per-site malware scanning, which matters when card data passes through your checkout flow.

None of this is a moral failing on the host’s part. Shared plans are priced at a few dollars a month because resources are oversold on the assumption that most sites idle. Stores do not idle.

What slowness actually costs a store

Google’s Core Web Vitals guidance sets a Largest Contentful Paint target of 2.5 seconds, and industry conversion studies have repeatedly found meaningful drop-off for each additional second of load time on commerce pages. The damage compounds because slow pages hurt paid traffic economics, organic rankings and repeat visits at the same time.

Checkout failure is worse than slowness. A 30-second gateway timeout during a promotion can cost more in one evening than a year of the hosting upgrade you postponed.

Signals you have outgrown your current host

1. WooCommerce admin pages, especially the Orders screen, take more than 3 seconds to load.
2. You see 503 or 504 errors during campaigns, or after an email send.
3. Scheduled tasks (subscription renewals, abandoned cart emails, stock syncs) run late or not at all.
4. Your host emails you about CPU or entry-process limits more than once a quarter.
5. Time to First Byte sits above 600 ms on cart and checkout URLs.
6. Traffic is above roughly 25,000 to 50,000 monthly visits, or you carry more than a few thousand SKUs.

Two or more of these together mean the fix is infrastructure, not another optimisation plugin.

How to choose the best WooCommerce hosting in 2026

Whether you compare GoDaddy, Bluehost, Hostinger or a specialist managed platform, judge the plan on what it publishes rather than what it promises. Ask for the numbers.

• Published PHP worker counts and a clear upgrade path. Vague answers here are the reddest flag in the category.
• Redis object caching included, not sold as an add-on. See how Redis compares with Memcached for high-traffic stores.
• Server-level caching with WooCommerce-aware rules, so cart, checkout and account pages bypass cache automatically.
• Isolated resources, whether that is a container, a VPS or a managed platform tier.
• Staging plus daily backups with fast restore, because you will test a plugin update on a live store exactly once before learning this lesson.
• Support staffed by people who know WooCommerce, not a ticket queue that blames your theme by default.

On price, expect roughly $5 to $15 per month for shared, $25 to $100 per month for managed hosting built for commerce, and $150 and up once you are handling serious order volume. Free WooCommerce hosting exists, and it is a demo environment, not a storefront. If budget is genuinely tight, a properly resourced affordable WordPress hosting plan beats an oversold one at the same price.

Frequently Asked Questions

What are the disadvantages of shared hosting?

The main disadvantages are shared CPU and memory, capped concurrent PHP processes (often 2 to 6), shared database servers and limited security isolation. One overloaded neighbour can slow every account on the machine, and most plans throttle rather than scale when traffic spikes.

What are the downsides of using WooCommerce?

WooCommerce is resource-hungry compared with hosted platforms, because every order, session and cart update is a database write that cannot be cached. You are also responsible for updates, security and PCI-relevant configuration, which the PCI Security Standards Council documents in detail. The trade-off is full ownership of data, checkout flow and fees.

What is the difference between shared hosting and WordPress hosting?

Shared hosting is a general-purpose environment sold by disk space, while managed WordPress hosting is tuned for one application: WordPress-aware caching, object caching, staging, automatic core updates and support that knows the stack. The difference in real-world speed is often 3x to 10x on uncached requests.

Is a VPS better than shared hosting?

Yes for a store, because a VPS gives you dedicated CPU and RAM instead of a contended pool, typically starting around $20 to $40 per month. The catch is that an unmanaged VPS makes you the sysadmin, so managed platforms often deliver better uptime for the same budget. Store owners running courses or gated content should also look at membership-focused hosting, where logged-in traffic is similarly uncacheable.

Ready to move your store off shared hosting?

We migrate WooCommerce stores free, keep orders intact and publish the worker and resource limits behind every plan. Take a look at our WooCommerce hosting plans and we will tell you honestly which tier your current traffic needs.