WooCommerce Hosting Requirements and Configuration

WooCommerce is a full e-commerce platform layered on top of WordPress. It works on basic hosting but performs poorly until properly configured — slow cart updates, sluggish checkout, occasional failed transactions. This guide covers what WooCommerce actually needs from hosting (PHP version, memory limits, caching strategy), the settings that matter for performance and reliability, and how to set them up on iWebVault.

Hosting-level requirements

PHP version

• WooCommerce officially supports PHP 7.4+ but recommends 8.1+ for performance.
• Use PHP 8.2 or 8.3 if your plugins/theme are compatible.
• cPanel → Select PHP Version → set to 8.2.

PHP 8 is dramatically faster than 7.4 — single biggest free performance gain. Verify themes and plugins are PHP 8 compatible first; WooCommerce extensions usually are. PHP version guide.

PHP settings

cPanel → Select PHP Version → Options:

PHP extensions

Required: bcmath, curl, dom, fileinfo, gd, hash, intl, json, mbstring, mysqli, openssl, simplexml, xml, zip.

cPanel → Select PHP Version → Extensions tab — enable any missing. Most are on by default on iWebVault.

SSL — mandatory

You cannot run a real WooCommerce store without HTTPS:

• Payment gateways require HTTPS.
• Browsers warn users on non-HTTPS checkout pages.
• PCI compliance for credit card handling requires HTTPS.

iWebVault auto-issues SSL via AutoSSL. Verify cPanel → SSL/TLS Status → all your domain entries are green. SSL guide.

Plan sizing

WooCommerce stores benefit from more resources than typical blogs:

• Small store (under 100 products, low traffic). Mid-tier shared hosting works.
• Medium store (100-1000 products, regular traffic). Higher-tier shared or entry VPS.
• Large store (1000+ products, high traffic, complex extensions). Managed WordPress VPS or dedicated.

Watch resource usage in cPanel during sales events / promotions — if you’re hitting limits, time to upgrade.

Caching for WooCommerce

WooCommerce has dynamic pages (cart, checkout, account) that MUST NOT cache, and static pages (product listings, individual products, shop home) that SHOULD cache aggressively.

LiteSpeed Cache configuration

LSCache has WooCommerce integration that handles exclusions automatically:

1. Install LiteSpeed Cache. Setup guide.
2. Activate WooCommerce.
3. LSCache automatically detects WooCommerce and applies cache rules.
4. LSCache menu → Cache → ESI tab → enable ESI (Edge Side Includes) — lets the cart fragment update without uncaching the whole page.

Pages excluded automatically:

• Cart page.
• Checkout page.
• My Account.
• Order Received / Thank You page.
• WooCommerce REST API endpoints used by Ajax cart updates.

Pages that cache normally:

• Shop page (product listings).
• Individual product pages.
• Category and tag archives.
• Static pages (about, contact, blog).

Cache automatically purges when products are updated, stock changes, or new orders are placed (so out-of-stock indicators stay current).

Database optimization for WooCommerce

WooCommerce stores grow databases fast — orders, customers, sessions, transient data. Regular maintenance keeps things fast:

Enable HPOS (High-Performance Order Storage)

WooCommerce 8.2+ supports storing orders in dedicated tables instead of the WordPress posts table. Dramatic performance improvement for stores with many orders.

• WooCommerce → Settings → Advanced → Features → enable “High-Performance Order Storage”.
• Migrate existing orders (WooCommerce handles automatically).
• Some old extensions may not be HPOS-compatible — check before enabling.

Regular cleanup

• WooCommerce → Status → Tools → Clear customer sessions: removes expired session data.
• WooCommerce → Status → Tools → Delete WooCommerce transients: clears cached query results.
• Install plugin like WP-Optimize for scheduled cleanup of revisions, transients, spam comments.

Email — order confirmations

Order confirmation emails are critical to customer experience. Don’t rely on PHP mail():

• Install WP Mail SMTP or FluentSMTP. SMTP guide.
• Configure to use authenticated SMTP through a mailbox like orders@yourdomain.com.
• For high-volume stores, use a transactional service (SendGrid, Mailgun) for better deliverability.

Set up SPF, DKIM, DMARC for the sending domain. Authentication guide. Customers shouldn’t have “Order confirmation” emails landing in spam.

Payment gateways

• Stripe — widely used, accepts cards globally, good docs.
• PayPal — familiar to customers, easy setup.
• Authorize.net — US-centric, established.
• Regional gateways — Paystack/Flutterwave for Nigeria, Razorpay for India, etc. Use whichever is best for your customers’ region.

WooCommerce extension marketplace has plugins for hundreds of gateways. Stick to popular well-maintained ones.

Image optimization for product photos

E-commerce sites are image-heavy. Optimization matters:

• LiteSpeed Cache → Image Optimization → enable WebP generation.
• Product images: standardize size before upload (e.g. 1000×1000). WordPress generates thumbnails automatically.
• Don’t upload 4MB images straight from a phone — resize first.
• WooCommerce → Settings → Products → Display tab → set appropriate image sizes.

Backups specifically for stores

For e-commerce, backups are higher-stakes:

• Daily backups (more frequent than weekly).
• Multiple restore points (a problem might not be noticed for days).
• Off-site copies (third-party backup destination via JetBackup remote).
• Test restores periodically — backups you’ve never tested might not work.

Losing 48 hours of orders is significantly worse than losing 48 hours of blog comments. JetBackup guide.

Security considerations

• PCI compliance. If processing cards directly, PCI DSS applies. Easier route: use Stripe/PayPal/etc. with hosted fields — they handle compliance, you don’t touch card data.
• Strong admin passwords + 2FA. Admin compromise on an e-commerce site = customer data exposure = legal liability.
• Regular security scans. Imunify360 scans included. Add Wordfence or similar WordPress-specific scanner.
• Limit admin access. Different roles for different staff (shop_manager for content, administrator only for owners).

Common WooCommerce hosting issues

“Checkout is slow / sometimes fails.” Memory limit too low, or external API timeout (payment gateway). Raise memory_limit to 512M. Check if your gateway is slow / having issues independently.

“Order confirmation emails not arriving.” Switch to SMTP via WP Mail SMTP. Verify SPF/DKIM/DMARC. Check Customer Order Received status in WooCommerce — order is created server-side even if email fails.

“Cart shows wrong items / abandoned cart behavior weird.” Cache caching the cart page. With LSCache + WooCommerce, this shouldn’t happen — verify WooCommerce integration is active. Other caching plugins must be disabled.

“Site slow during sales / Black Friday.” Resource limits being hit. Temporary upgrade or pre-event upgrade before peak. Monitor with cPanel Metrics during the peak.

“Admin pages (orders, products) very slow.” Often database needs optimization. Enable HPOS. Clear transients. Consider Action Scheduler cleanup (WooCommerce → Status → Scheduled Actions).

What’s next

• Performance tuning: LiteSpeed Cache setup.
• Reliable mail: SMTP guide.
• SSL: AutoSSL guide.
• Backups: JetBackup guide.

WooCommerce works fine on iWebVault hosting once configured. Get PHP version and memory sized right, configure LSCache with the WooCommerce module, set up SMTP for reliable order emails, and back up daily. With those four in place, you’re set up better than most stores running on “premium” managed hosting.