- WooCommerce is a database application wearing a WordPress costume — carts, sessions and checkout cannot be page-cached, so raw server speed is the whole game.
- This guide sizes a dedicated server for WooCommerce by order volume, tunes MySQL and Redis for uncacheable traffic, and hardens checkout for sale-day spikes.
Here is the fact that explains every slow WooCommerce store: the money pages cannot be cached. Page caches make your catalog fly, but the instant a customer adds to cart, starts a session, or hits checkout, every request goes straight to PHP and MySQL — raw, uncached, per-customer work. That is why stores that feel fast to browsers still hemorrhage sales at checkout, and why a dedicated server for WooCommerce pays for itself in recovered conversions: it makes the uncacheable path fast.
Sizing by Store Reality
| Store Profile | Signals | Recommended Spec | Est. Monthly |
|---|---|---|---|
| Growing store | Up to ~100 orders/day, catalog under 5k SKUs | Ryzen 6 core @ 4.5 GHz+, 32 GB, NVMe | $90–$130 |
| Established store | 100–500 orders/day, 5k–50k SKUs, plugins galore | Ryzen 8 core @ 5 GHz, 64 GB, NVMe RAID 1 | $140–$220 |
| High-volume / flash-sale brand | 500+ orders/day, sale-day spikes | 8–16 cores, 128 GB, RAID 10, managed | $250–$450 |
The pattern repeats from our CPU comparison: checkout is a chain of single-threaded PHP requests, so clock speed converts directly to conversion rate. Kernel truth: Amazon-class studies put ~1% revenue loss per 100 ms of added latency — on a store doing $50k/month, a slow server is a four-figure line item.
The Tuning That Actually Matters
- MySQL first: WooCommerce hammers
wp_options, sessions, and (pre-HPOS) postmeta. Give InnoDB a buffer pool that holds the working set, enable HPOS (High-Performance Order Storage), and put it all on NVMe — checkout writes are random I/O incarnate. - Redis object cache: the single biggest WooCommerce win — cart fragments, session lookups, and option reads stop hitting MySQL entirely. Localhost Redis on your own box is sub-millisecond.
- Page cache with surgical exclusions: cache the catalog aggressively; exclude cart/checkout/account and let fragments handle the mini-cart.
- PHP-FPM headroom: size workers for your sale-day concurrent checkouts, not Tuesday's — checkout requests are slow (payment API round-trips), so they hold workers longer than page views.
- Cron discipline: disable WP-Cron's per-visit trigger, run real cron every minute, and let Action Scheduler churn webhooks and emails in the background instead of inside a customer's request.
Sale-Day Survival
Flash sales are self-inflicted DDoS. Preparation: load-test checkout specifically (not the homepage) at 3–5x your expected peak, pre-scale PHP workers and MySQL connections, put static assets behind a CDN so the origin serves only the uncacheable money path, and have your host's DDoS protection aware a traffic spike is legitimate. Stores on shared or VPS hosting discover their limits at 00:01 on Black Friday; dedicated stores discovered them in a load test the week before.
Security and PCI Notes
Card data belongs with your gateway (Stripe/PayPal-hosted fields keep you in SAQ-A territory), but the server still owes customers TLS everywhere, aggressive patching, and isolation — a dedicated box means no stranger's vulnerable site shares your IP or your kernel. Run the full security checklist; e-commerce is the most-scanned target class on the internet.
Frequently Asked Questions
When should a WooCommerce store move to a dedicated server?
Hard signals: checkout TTFB over ~800 ms at busy hours, host resource warnings during promotions, or order volume where a 1% conversion change exceeds the hosting delta. Most stores cross it between 50–150 orders/day.
What is the best dedicated server for WooCommerce specifically?
High-clock Ryzen, 64 GB RAM, NVMe RAID, Redis, HPOS enabled — the "Established store" row above covers 90% of serious stores.
Managed or unmanaged for an e-commerce business?
Managed, almost always — revenue infrastructure deserves 24/7 eyes, and store owners have better uses for 3 AM than MySQL recovery.
Can WebsNP migrate a live store without downtime?
Yes — staged migration with a content freeze measured in minutes, not hours, timed to your quietest window. Free on every dedicated plan.
Every 100 ms you shave off checkout is money: order a WooCommerce-tuned dedicated server from WebsNP — Ryzen, NVMe, Redis-ready, migrated free. Send us your store's numbers for a sizing that matches your order volume.