WooCommerce hosting in India: what your store actually needs
10 min read · 08-Apr-2026
villagehosting.in team
8 April 2026
WooCommerce minimum specs are not production specs
WooCommerce officially requires 64MB PHP memory. A real store with product images, WooCommerce extensions, and real traffic needs 256–512MB minimum. The 'minimum' specs are for a development environment with no real load. Plan for at least 2GB VPS RAM for any store with 100+ products and real traffic.
WooCommerce powers 28% of all online stores globally, and a large share of Indian eCommerce businesses run on it. It is flexible, free, and integrates with every Indian payment gateway.
But WooCommerce is also one of the most resource-hungry WordPress configurations. A store with 500 products and 100 concurrent visitors will crush a standard shared hosting plan. Most Indian WooCommerce store owners discover this on a sale day — when traffic spikes, the server collapses, and orders are lost.
This guide explains what your WooCommerce store actually needs, and how to match it to the right hosting plan.
The real server requirements for WooCommerce
WooCommerce's official "minimum requirements" are dangerously low. They say PHP 7.4, 64MB memory limit, MySQL 5.6. A store with those specs will work in development — and fail in production.
What a live WooCommerce store actually needs:
| Resource | Minimum for small store | Recommended for growth |
|---|---|---|
| PHP | 8.1+ | 8.3 |
| PHP memory | 256MB | 512MB |
| MySQL | 8.0 | 8.0 + Redis |
| Storage | 10GB SSD | 50GB+ NVMe |
| Bandwidth | 100GB/month | Unlimited or CDN-assisted |
| Concurrent users | 10–20 | 50–200+ |
Most ₹99/month shared hosting plans give you 128MB PHP memory and a shared MySQL server. This is why stores crash.
Why shared hosting fails WooCommerce
WooCommerce stores have a fundamentally different traffic pattern than blogs or brochure sites:
- No page caching for logged-in users — cart and checkout pages cannot be cached. Every logged-in customer hits PHP and MySQL directly.
- Cart fragments — WooCommerce makes an AJAX request on every page load to check the cart. On shared hosting, this is a full PHP execution for every visitor.
- Sale day traffic spikes — a flash sale or festival discount can 10× your normal traffic in minutes. Shared hosting has no headroom for this.
- Background processing — order emails, stock updates, and payment confirmations all run PHP in the background.
Choosing the right hosting plan for WooCommerce
Up to 50 orders/day: Managed WordPress hosting (Grove plan, ₹299/mo)
- LiteSpeed + LSCache handles anonymous browsing efficiently
- Redis object cache handles repeat database queries
- PHP 8.3 with 256MB memory limit
- Good enough for a store doing ₹50,000–₹2,00,000/month in revenue
- Limitation: logged-in customer sessions still compete for shared PHP workers
50–500 orders/day: VPS hosting (₹1,499–₹2,999/mo)
- Dedicated CPU cores — no sharing with other sites
- 2–4GB RAM — enough for PHP-FPM, MySQL, Redis running simultaneously
- WooCommerce can handle traffic spikes without crashing
- You can install WP-Rocket or LiteSpeed Cache with full object cache
500+ orders/day or festival season preparation: Managed VPS or Cloud (₹4,999+/mo)
- Auto-scaling handles traffic spikes
- Dedicated MySQL — no shared database server
- Elasticsearch for product search (WooCommerce's built-in search is slow at 1,000+ products)
- Redis cluster for session management
Essential WooCommerce optimisations
Regardless of hosting tier, do these:
1. Enable Redis for cart and session storage WooCommerce sessions default to MySQL. At 100 concurrent users, this creates hundreds of database rows. Redis stores sessions in memory — 10× faster.
Add to wp-config.php:
define('WC_SESSION_CACHE_GROUP', 'wc_session_id');
Then configure WooCommerce → Settings → Advanced → WooCommerce.com → Use Redis for sessions.
2. Exclude WooCommerce cart/checkout from page cache In LiteSpeed Cache → Cache → Excludes → Cache Excludes, add:
/cart/
/checkout/
/my-account/
/shop/?add-to-cart=
Never cache these pages — customers will see each other's carts.
3. Enable Cloudflare, but bypass the API Cloudflare caches your product pages at the edge. But if WooCommerce uses Stripe webhooks or PayU IPN, these need to bypass Cloudflare:
In Cloudflare → Rules → Page Rules, add:
yourdomain.com/?wc-api=* → Cache Level: Bypass
4. Optimise product images Enable WebP conversion in LiteSpeed Cache. Set WooCommerce → Settings → Products → Images to generate three sizes (thumbnail, catalog, product). Avoid uploading 4K images for 300px thumbnails.
5. Use a dedicated payment gateway plugin, not WooCommerce Payments WooCommerce Payments (Stripe) requires connecting to a Stripe-operated server for every transaction. For Indian stores, use the official Razorpay for WooCommerce or PayU Biz plugin — these process payments server-side without the middleware overhead.
Benchmarking your WooCommerce store
Before buying a bigger server, benchmark your current one:
- Open Chrome DevTools → Network tab
- Add a product to cart
- Watch the
/cart-fragmentsrequest time — if it is > 500ms, you have a server bottleneck - Use Loader.io (free tier) to simulate 50 concurrent users on your product pages
If product pages load in under 2 seconds for 50 concurrent users, you are fine on your current plan. If they slow down past 4 seconds or return 504 errors, it is time to upgrade.
What we include on every WooCommerce plan
Every VillageHosting plan includes:
- LiteSpeed Enterprise + LSCache (WooCommerce mode enabled)
- Redis object cache
- WooCommerce-compatible security via Imunify360
- Daily backups with one-click restore
- Free SSL (including wildcard on Grove+)
- Free migration of your existing WooCommerce store
We also offer a free WooCommerce audit for new customers. Send us your store URL on WhatsApp and we will identify the top 3 performance bottlenecks before you switch.