WooCommerce is significantly more demanding than a standard WordPress site. It runs more database queries per page, handles session data for every visitor, processes payment gateway callbacks, sends transactional emails, and has zero tolerance for downtime during a sale. Most cheap shared hosting fails under this load. Here's what your store actually needs, and why each requirement matters.
WooCommerce requires PHP 7.4 at minimum but performs significantly better on PHP 8.2. The performance difference is measurable, PHP 8.x includes OPcache improvements and JIT compilation that meaningfully reduce page generation time compared to 7.x. Confirm your host lets you select your PHP version from the control panel (cPanel → Software → Select PHP Version) rather than assigning a global default across the server.
PHP memory limit matters equally. WooCommerce recommends a minimum of 256MB; 512MB is preferable for stores with complex product data or many active plugins. Budget hosts frequently cap this at 128MB, which causes white screen errors and checkout failures under load. You can check your current memory limit in WooCommerce → Status → System Status, under the PHP section. If you see "Memory limit: 128M" and your store is running slow, that cap is likely a contributing factor.
A brochure site with low traffic is forgiving of slow hosting, pages load from cache, PHP is barely invoked, and database queries are minimal. A WooCommerce store is fundamentally different. Cart session management, stock checks on every add-to-cart, payment gateway webhooks, order confirmation emails, inventory updates, and WP-Cron tasks all run simultaneously. On overcrowded shared hosting where CPU and database connections are rationed across hundreds of sites, these operations queue up and time out.
The most common symptom is not a crash, it's slow checkout. Customers at the payment stage encounter a page that takes 4–8 seconds to load. That delay, at the highest-intent moment of the shopping journey, causes abandonment. The problem is hosting, not WooCommerce itself. For stores processing fewer than 50 orders a month, well-configured shared hosting on a good server is adequate. Above that threshold, or during any promotional event that spikes traffic, dedicated or cloud resources with guaranteed CPU allocation are worth the additional cost.
Every WooCommerce store must run on HTTPS. Without it, browsers warn visitors their connection isn't secure before they reach checkout, payment gateways like Stripe and PayPal refuse to load their JavaScript on non-HTTPS pages, and you fail any PCI DSS compliance requirement. SSL also affects search rankings, Google has used HTTPS as a ranking signal since 2014.
Free Let's Encrypt certificates are available through cPanel on most reputable hosts and renew automatically every 90 days. Install the certificate in cPanel → SSL/TLS → Let's Encrypt SSL, then verify it covers both yourdomain.com and www.yourdomain.com. After installing, use the Really Simple SSL plugin or WP Force SSL to ensure all traffic redirects to HTTPS, a single HTTP page in the checkout flow will trigger mixed content warnings and may break payment gateway scripts.
Standard full-page caching breaks WooCommerce. Cart contents, the checkout page, account pages, and the real-time "added to cart" state all contain user-specific data that must be served fresh. Serving a cached cart page to a different user is a serious bug, one customer would see another's items. Most caching systems automatically exclude these pages when they detect WooCommerce is active.
LiteSpeed Cache (available on LiteSpeed-powered hosts) handles WooCommerce cache exclusions correctly out of the box. Enable WooCommerce integration in LiteSpeed Cache → WooCommerce settings. WP Rocket also handles WooCommerce exclusions well and adds additional performance optimisations. The result is that your shop and product pages are served from fast server-level cache, while cart, checkout, and account pages are served fresh from PHP, making uncached PHP performance more important for WooCommerce than for a standard WordPress site.
WooCommerce is database-intensive. Product data, order records, customer data, and session data all live in MySQL. Execution time (the maximum number of seconds PHP is allowed to run) matters for import operations, bulk order processing, and subscription renewals. WooCommerce recommends a minimum of 60 seconds; 120 seconds is safer for stores running large product imports or bulk operations. Budget hosts often cap this at 30 seconds, which causes import operations to time out mid-process.
MySQL version also matters. WooCommerce recommends MySQL 5.6 or higher, or MariaDB 10.0 or higher. Most current hosts run MariaDB 10.4 or newer, which is fine. If you're on a very old server, check your MySQL version in WooCommerce → Status → System Status. Running WooCommerce on MySQL 5.5 or below causes compatibility warnings and can produce unexpected query behaviour.
Losing a WordPress blog is recoverable, you restore from backup or rewrite content. Losing a WooCommerce store means lost orders, lost customer data, potential failure to fulfil orders already paid for, and serious trust damage. For GDPR-regulated stores, losing customer data without adequate controls can carry legal risk. Daily automated backups are a minimum requirement; twice-daily is better for stores with meaningful order volume.
Knowing a backup exists is different from knowing it works. Test your restore process before you need it. Restore a backup to a staging environment and verify the store functions correctly, products load, checkout works, orders are intact. Most store owners who lose data had backups that were either incomplete, corrupt, or covering the wrong database. Verify your backup includes both files and the database, and test the restore at least every few months.
LiteSpeed with WooCommerce-aware caching, PHP 8.2, SSL included, daily backups, and free migration on every plan.
View Hosting Plans