Running a large WooCommerce store teaches you something that generic WordPress hosting advice never mentions.
Page caching does not help you. Every logged-in customer, every active cart, every checkout session bypasses the page cache and hits PHP and MySQL directly. When 300 customers browse simultaneously during a sale, that is 300 concurrent uncached PHP requests running against a product database with millions of rows.
You are not looking for the fastest WordPress host. You are looking for the host that handles this specific workload: high concurrent authenticated traffic, database-heavy product queries, real-time inventory updates, and payment gateway callbacks running in parallel.
The providers below understand this problem. Several are built specifically for it.
What Large WooCommerce Stores Actually Hit
High IOPS NVMe storage. A WooCommerce database with 10,000 products, attribute tables, variation tables, and order history runs constant random read operations. The IOPS difference between storage types is most visible on databases, and WooCommerce databases are query-intensive.
Redis object caching. WooCommerce makes many repeated database queries per request. Product attribute lookups, tax tables, shipping zones, and customer session data are all query candidates. Redis caches these results and eliminates the redundant database hits.
Dedicated database resources. When PHP and MySQL compete for the same RAM, database performance degrades under load. Separating the database onto its own server or into a managed database service eliminates this competition.
PHP workers sized for authenticated sessions. Logged-in customers bypass full-page cache. Every authenticated page load occupies a PHP-FPM worker for its duration. Underpowered PHP worker pools cause queue buildup and slow checkouts.
Generous PHP execution time. Large product imports, bulk order exports, and payment gateway callbacks can take 60+ seconds. Default PHP timeout kills these.
Payment gateway timeouts. Stripe, PayPal, and other gateway callbacks arrive asynchronously and require PHP execution. Long execution times on order processing can time out during high-traffic events.
Persistent object storage for media. 10,000 product images, sized variants, and thumbnails accumulate to gigabytes. Offloading product images to object storage keeps the server storage footprint manageable and CDN-deliverable.
Search performance. WooCommerce’s native product search is database-query-based. With 10,000+ products, search queries become slow. Dedicated search solutions (Elasticsearch, Algolia) or better database indexing become necessary.
Quick Comparison
| Provider | Redis | PHP Worker Config | NVMe | WooCommerce Specialist | Dedicated DB Option |
|---|---|---|---|---|---|
| Liquid Web / Nexcess | Yes | Configurable | Yes | Yes (dedicated WC plans) | Yes |
| Kinsta | Built-in | Configurable | Yes | Partial | No |
| Cloudways | Built-in | Configurable | Via provider | No | Managed DB add-on |
| WP Engine | Available | Standard | Yes | Partial | Available |
| ScalaHosting | Available | Configurable | Yes | No | Separate VPS option |
| Pressable | Via plugin | Standard | Yes | No | No |
Liquid Web / Nexcess
Who it is for: WooCommerce merchants at significant scale (large product catalogues, high order volume, or complex product configurations) who need a managed platform built specifically around WooCommerce performance.
Liquid Web’s Nexcess brand offers managed WooCommerce hosting that includes performance monitoring configured for WooCommerce-specific metrics: add-to-cart response times, checkout completion rates, and order processing queue depth. The platform is tuned for WooCommerce query patterns out of the box.
The Nexcess Managed WooCommerce tier includes a plugin performance monitor that tests active plugins against your site specifically, not just general WordPress benchmarks. For stores where a payment gateway plugin or inventory sync plugin is causing checkout slowdowns, this identifies the specific bottleneck.
Automatic scaling during traffic spikes is handled at the Nexcess platform level. A product launch or sale event that drives 5x normal traffic does not require manual server changes.
Plans start at: $19 per month (Nexcess managed WooCommerce), scales to dedicated
Kinsta
Who it is for: WooCommerce merchants running stores that also have significant content marketing, SEO-driven product pages, and a user base with a mix of anonymous browsers and authenticated customers.
Kinsta’s platform handles the split WooCommerce traffic pattern well. Anonymous visitors browsing products hit the full-page cache. Authenticated customers with active carts and logged-in sessions bypass the page cache and get served through PHP with Redis object caching accelerating database queries.
The automatic cache bypass rules for WooCommerce are pre-configured: cart, checkout, account pages, and sessions with WooCommerce cookies always bypass the page cache. Setting these up manually on other platforms requires careful configuration.
The Google Cloud C3D infrastructure underlying Kinsta provides the compute performance for complex product queries. For WooCommerce stores with variable products (5+ attributes with 10+ options each), query complexity multiplies and benefits from fast compute.
Cloudways
Who it is for: WooCommerce merchants who need to choose their underlying cloud provider (and potentially use DigitalOcean Premium with NVMe storage), scale server resources without migration, and configure the hosting stack with more granularity than managed platforms allow.
The Cloudways platform’s server resizing without migration is practically valuable for WooCommerce merchants. As a catalogue grows and order history accumulates, the database grows and the application needs more RAM. Resizing a Cloudways server upgrades the resources in-place without downtime.
The managed database add-on on Cloudways provisions a separate database server from the web server. For WooCommerce at scale, database isolation eliminates the resource competition pattern that causes checkout slowdowns during traffic peaks.
Redis is built-in on all Cloudways servers and the Redis Object Cache plugin configuration is pre-configured for WordPress.
WP Engine
Who it is for: Enterprise WooCommerce operations with dedicated IT or development teams, compliance requirements, and the need for SLA-backed managed support for their ecommerce infrastructure.
WP Engine’s Smart Plugin Manager handles updates for WooCommerce and extensions with automated testing before applying updates. For stores where a WooCommerce extension update breaking checkout would be a significant incident, tested automated updates reduce this risk.
Their enterprise WooCommerce plans include dedicated infrastructure with SLA commitments. For merchants where WooCommerce downtime has a direct, calculable revenue impact, the SLA provides contractual recourse that standard managed hosting does not.
Pressable
Pressable covers mid-size WooCommerce stores that have grown beyond shared hosting but do not yet need the specialist infrastructure of Nexcess or Kinsta.
The managed stack handles the WooCommerce cache bypass logic correctly, and the staging environment supports testing extension updates before applying them to the live store. For stores in the 10,000 to 30,000 product range with steady rather than spike-driven traffic, Pressable provides reliable managed WordPress at a predictable price.
ScalaHosting
Who it is for: Growing WooCommerce stores that have outgrown shared hosting and need managed VPS with Redis and NVMe without the premium pricing of the fully managed tier.
ScalaHosting managed VPS provides the server-level control to configure PHP-FPM pool settings specifically for WooCommerce’s authenticated session patterns, Redis with a memory limit appropriate for WooCommerce object cache, and MySQL tuning including InnoDB buffer pool sizing.
For WooCommerce stores with 10,000 to 50,000 products and moderate order volume, ScalaHosting managed VPS hits the right trade-off between resource availability, configuration control, and cost.
Plans start at: $30 per month (managed cloud VPS)
Database Maintenance for Large Catalogues
WooCommerce accumulates waste in the database over time. Run these quarterly to keep performance stable:
Under WooCommerce, Status, Tools: delete auto-draft orders, delete orphaned order items, delete expired transients, and clean up rate limit logs. These rows accumulate and slow queries without contributing to your actual data.
For the wp_postmeta table, which grows significantly with product attributes and variation data, verify that the meta_key column is indexed:
SHOW INDEX FROM wp_postmeta;
If meta_key does not appear in the index list, add it:
ALTER TABLE wp_postmeta ADD INDEX meta_key (meta_key(191));
Stores that also run subscription products or membership access alongside the WooCommerce catalogue share the database load patterns covered in the membership site hosting guide.
Run these MySQL queries periodically to find the tables consuming the most space and verify indexes are in place:
# Check table sizes
SELECT table_name, ROUND(((data_length + index_length) / 1024 / 1024), 2) as size_mb
FROM information_schema.tables
WHERE table_schema = 'your_database'
ORDER BY size_mb DESC LIMIT 20;The wp_wc_order_product_lookup table and wp_wc_customer_lookup table grow with every order. WooCommerce includes a database optimisation tool under WooCommerce, Status, Tools that clears auto-draft orders, orphaned order items, and transients that accumulate over time.
For stores with subscription products or membership components, the relationship between WooCommerce infrastructure and membership site hosting requirements overlaps significantly. Stores combining product sales with subscription access share the same database pattern challenges.
Frequently Asked Questions
At what product count does hosting become a bottleneck?
Product count alone is not the bottleneck. The combination of product count, variation count, and concurrent authenticated users determines the load. A store with 50,000 simple products and low concurrent users runs on less infrastructure than a store with 5,000 variable products (each with 100 variations) and 200 concurrent customers during a sale. Variable products generate exponentially more database rows than simple products.
Does WooCommerce need a dedicated database server at scale?
When MySQL and PHP compete for RAM on the same server, MySQL loses consistently during traffic peaks. PHP workers consume memory as requests arrive. MySQL’s InnoDB buffer pool shrinks under pressure. Query times increase. Checkout becomes slow. Separating the database onto its own server eliminates this competition. Cloudways’s managed database add-on or Liquid Web’s database server options provide this separation without running your own database infrastructure.
How do I prevent cart and checkout from serving cached pages?
Configure your CDN and server cache to bypass when WooCommerce session cookies are present. The cookies to bypass on are woocommerce_cart_hash, woocommerce_items_in_cart, and wc_session. Kinsta and Nexcess configure this automatically. On other platforms, verify this bypass before going live.
