WooCommerce adds significant PHP and database load to WordPress. Product pages, category pages, and checkout all involve complex queries and personalised session data that complicate caching. A 1-second delay in page load time is associated with measurable drops in conversion rate, and the checkout page, which can't be cached, is where this matters most. Here's how to systematically speed up a WooCommerce store without breaking functionality.
Standard full-page caching serves the same pre-built HTML to every visitor. That works for a blog or brochure site. For WooCommerce, the cart, checkout, account pages, and the real-time "added to cart" indicator all contain user-specific data that must be generated fresh per visitor. Most caching systems handle this by automatically excluding these pages from cache, but it means a significant portion of the customer journey always bypasses caching entirely.
The practical implication is that your shop index, product category pages, and individual product pages benefit strongly from caching. Those pages can be served in under 100ms from a well-configured cache. But anything involving the cart or checkout hits PHP and MySQL directly on every request. This shifts performance focus: for WooCommerce, uncached PHP execution speed matters more than for a standard WordPress site.
In LiteSpeed Cache (the recommended caching plugin on LiteSpeed servers), go to LiteSpeed Cache → WooCommerce. Ensure "Separate Cart Caching" is enabled, and verify the exclusion list includes /cart/, /checkout/, and /my-account/. LiteSpeed Cache handles these exclusions automatically when it detects WooCommerce, but confirm they're in place especially after plugin updates.
Enable CSS and JavaScript minification and combination in LiteSpeed Cache → Page Optimization. Enable lazy loading for images. For WP Rocket users, the WooCommerce-specific settings appear under WP Rocket → eCommerce, enable the cache exclusion for WooCommerce pages and "Cart fragments" optimisation, which reduces the AJAX requests WooCommerce makes on every page load to check cart state. Disabling the cart fragments request (when the cart is empty) alone can shave 200–400ms from page load time across your store.
Redis object caching dramatically improves WooCommerce performance for pages that bypass full-page cache. When Redis is active, WordPress stores expensive database query results, product pricing calculations, and user session data in memory. When the next request needs the same data, it's retrieved from RAM rather than running a fresh database query. This is especially valuable for checkout and cart pages where full-page caching can't help.
If your host offers Redis, enable it. On most cPanel hosts this requires a Redis plugin (Redis Object Cache by Till Krüss is the standard free option) and a Redis server running on the hosting account. Configure the plugin connection settings (host: 127.0.0.1, port: 6379 for typical setups) and enable the drop-in cache. Verify it's working under Settings → Redis Object Cache, the status should show "Connected" and "Drop-in: Valid". For stores processing significant order volume, Redis can reduce checkout page generation time by 40–60% compared to database-only operation.
WooCommerce generates a large volume of database records over time: orders, customer records, product meta rows, product variation data, and transients (temporary cached values stored in the database). As these accumulate, some queries slow down. Regular database maintenance keeps query performance consistent.
Use WP-Optimize to clean the database on a schedule. Target: post revisions (can be disabled in wp-config.php by adding define('WP_POST_REVISIONS', 5);), expired transients, orphaned order meta, completed order records beyond your data retention period, and the wp_options autoload data. Run SELECT * FROM wp_options WHERE autoload = 'yes' ORDER BY LENGTH(option_value) DESC LIMIT 20; in phpMyAdmin to identify large autoloaded options that slow down every WordPress page load. A WooCommerce store that's been running for two years may have several hundred megabytes of redundant data in the database.
Product catalogues generate thousands of images: main product images, gallery images, variation-specific images, and multiple WordPress-generated thumbnail sizes. Unoptimised product images are the most common performance bottleneck in WooCommerce stores, particularly on category and shop pages where many products are displayed simultaneously.
Use Imagify or ShortPixel to compress images during upload, both integrate with WordPress's media library and can bulk-process existing images. Set them to WebP conversion: WebP images are 25–35% smaller than equivalent JPEG files with no visible quality difference. Ensure WordPress is serving the correct image sizes for each display context. WooCommerce defines specific image dimensions (set under WooCommerce → Settings → Products → Display): a 1200x1200px image on a category page showing a 300x300px thumbnail is delivering 16 times more data than necessary. Regenerate thumbnails after adjusting these settings using the Regenerate Thumbnails plugin.
Every active WordPress plugin adds PHP execution time to every page load. WooCommerce stores tend to accumulate plugins over time, payment gateways, shipping calculators, review plugins, marketing tools, and analytics integrations. Audit your active plugins against what's actually being used. A plugin that was installed for a one-time task and never deactivated adds overhead to every request indefinitely.
Specifically for WooCommerce, be selective with product page plugins. Plugins that add functionality to every product page (wishlists, comparison tools, recently viewed) execute on every product page load, including for visitors who never use that feature. Test whether each conversion-focused plugin actually improves conversions for your store, A/B testing beats assumptions. Query Monitor is a useful free plugin for identifying which plugins are responsible for the most database queries and PHP time on any given page.
Caching, database tuning, and image optimisation all help, but they can't compensate for fundamentally underpowered hosting. PHP memory limit (256MB minimum), execution time (60+ seconds), PHP workers (the number of concurrent PHP processes), and raw server speed all determine the performance floor of your store. A WooCommerce store on a fast LiteSpeed server with adequate PHP workers will outperform the same store on overcrowded shared hosting regardless of what plugins are installed.
Measure your store's performance with Google PageSpeed Insights and WebPageTest. Look specifically at Time to First Byte (TTFB), this reflects server response speed before any client-side rendering occurs. A TTFB above 600ms on a product page indicates a hosting or caching problem rather than a front-end issue. For checkout pages, a TTFB above 1 second at low traffic levels is a clear signal that server resources are insufficient for your workload.
HostBible plans include LiteSpeed with WooCommerce cache exclusions configured, adequate PHP memory and workers, and daily backups of your store data.
View Hosting Plans