WooCommerce Hosting Requirements: What Your Store Actually Needs to Run Well

A standard WordPress blog is primarily a read operation -- the server generates HTML once, caches it, and serves the cached version to most visitors. WooCommerce is a different workload. Every cart interaction, checkout step, and session update requires fresh PHP execution and database writes. That shift changes the infrastructure requirement in ways that standard shared hosting cannot handle at meaningful transaction volume.

Why WooCommerce Hits Shared Hosting Hard

Dynamic Requests That Cannot Be Cached

Every time a user adds an item to a cart, applies a coupon, or reaches the checkout page, the server runs a PHP script and queries the MySQL database. These requests cannot be served from a page cache because the response is user-specific and changes with each interaction.

A blog running 10,000 pageviews/day might generate 200 uncached PHP requests (admin logins, form submissions, search queries). A WooCommerce store doing 200 transactions/day generates thousands of uncached PHP requests -- cart updates, checkout steps, payment processing callbacks, stock validation calls. The PHP execution load is not comparable.

Session Management and Database Write Load

WooCommerce maintains individual user sessions to track cart state. This creates a continuous stream of database writes alongside reads -- increasing Disk I/O demands beyond what a read-heavy content site requires. On shared hosting with a shared database server, this write load compounds with other customers' workloads during peak hours.

WooCommerce Admin Overhead

The WooCommerce admin panel -- order management, inventory updates, report generation -- is significantly heavier than the standard WordPress dashboard. Without sufficient PHP memory allocation, the admin panel becomes unresponsive during busy periods or when running bulk operations.

Minimum Server Requirements by Store Size

Infrastructure needs scale with transaction volume and concurrency -- the number of simultaneous users on the site at the same moment.

PHP memory baseline: 256 MB is the floor to keep WooCommerce running at all. For a production store, 512 MB is the practical minimum; 768 MB handles most medium-store workloads without out-of-memory errors during plugin updates or traffic spikes. Per WooCommerce's official documentation, PHP 8.2 or 8.3 is the current recommended version -- older versions are slower and present security risks for e-commerce data.

The Caching Problem Specific to WooCommerce

Standard page caching, if misconfigured for WooCommerce, creates a data integrity risk rather than solving a performance problem.

The cart fragmentation issue: If your caching layer serves cached versions of the Cart, Checkout, or My Account pages, a cached page intended for one user can be served to another. The result is incorrect cart contents, wrong pricing, or another user's account data displayed. This is a misconfiguration problem, not an inherent WooCommerce limitation, but it happens consistently on hosting environments that do not apply WooCommerce-aware caching exclusions.

The correct configuration: Cart, Checkout, My Account, and any page containing the [woocommerce_*] shortcodes must be excluded from page caching. WooCommerce-aware hosting platforms (SiteGround, Kinsta) apply these exclusions automatically. On self-managed setups, this must be configured explicitly in your caching plugin or server-level cache rules.

PHP Workers: The Primary WooCommerce Bottleneck

A PHP worker handles one uncached request at a time. If your plan allocates 2 PHP workers and 5 users submit cart updates simultaneously, the first 2 requests are processed while the other 3 queue. If the queue grows faster than workers can clear it, the server returns 502 or 503 errors.

On cheap shared hosting, PHP workers are pooled across all accounts on the server. During peak hours, you are competing for workers with every other customer on that physical server. This is the failure mode that produces WooCommerce checkout errors and cart timeouts under moderate traffic.

On SiteGround GrowBig and GoGeek, PHP worker allocation is higher and prioritized by plan tier. On Kinsta, each site runs in an isolated container with dedicated PHP workers -- no pool contention from other customers. On an InterServer VPS, you configure PHP-FPM worker pools directly and set limits appropriate to your workload.

Object Caching (Redis): Required at Medium Scale

For small stores, standard page caching and sufficient PHP workers cover most of the requirement. For medium-to-large stores with repetitive database queries, Redis object caching is the next infrastructure requirement.

Redis stores frequent database query results in server RAM. Instead of the database executing "What is the price of Product X?" on every request, Redis returns the cached result from memory. For a store with hundreds of SKUs, active promotional pricing, and inventory queries on every product page load, Redis reduces database query load substantially -- freeing CPU for PHP execution.

Kinsta includes Redis object caching on all plans. SiteGround offers a Redis addon on higher tiers. On an InterServer VPS, Redis is a standard installation that you configure to the specific memory allocation your workload requires.

Recommended Hosting by Store Profile

See SiteGround Plans for WooCommerce | See Kinsta Plans

FAQ

Can WooCommerce run on a $5/month shared host? At near-zero traffic, yes. Once you have simultaneous visitors submitting cart operations, the shared PHP worker pool and memory limits produce a slow checkout experience. The failure mode is not a crash -- it is a degraded experience that shows up in abandoned cart rates before it shows up in error logs.

What PHP version does WooCommerce require in 2026? PHP 8.2 or 8.3 is the current recommendation per WooCommerce documentation. Older PHP versions are slower for object-oriented code execution and are no longer receiving security patches -- a meaningful risk for any site processing payment data.

How does a CDN help WooCommerce if checkout pages cannot be cached? A CDN offloads static assets -- images, CSS, JS -- which often represent 80-90% of a page's weight by file size. By serving static assets from the CDN edge, the origin server's PHP workers and CPU handle only the dynamic checkout logic. This effectively increases PHP worker capacity for the requests that matter.

Is an SSL certificate required for WooCommerce? Yes. HTTPS is required for PCI compliance and is standard practice for any site transmitting payment data. Most reputable hosts include free Let's Encrypt SSL certificates that provision and renew automatically.

Related:

• When SiteGround Is the Right Call (And When It's Overkill)
• SiteGround vs Kinsta: Which Is Worth the Price Difference?
• SiteGround Review: Is It Worth It for Growing WordPress Sites?
• WordPress Hosting Comparison: SiteGround, Kinsta, and InterServer