WooCommerce stores are harder to speed up than a typical WordPress site. Every product page loads dynamic pricing, stock levels, and variation data from the database. Category pages render dozens of product cards with images, ratings, and add-to-cart buttons. Plugins for reviews, wishlists, upsells, and payment gateways all add their own scripts and stylesheets on top. If your store still feels slow after installing a performance plugin, the good news is that BlinkSpeed has specific settings built for exactly this kind of site – they just need to be configured with WooCommerce’s structure in mind, not just turned on and left at their defaults.
This guide walks through where a slow WooCommerce store actually loses time, which BlinkSpeed settings address each bottleneck, and how to configure everything so your shop runs fast without breaking checkout, cart updates, or your account dashboard along the way.
Where a WooCommerce Store Actually Loses Speed
Before changing settings, it helps to know what is typically slow on an ecommerce site and why a generic caching plugin setup often does not fully fix it.
Database load on product and category pages. Every time a product page renders, WooCommerce queries the database for price, stock status, variations, related products, and reviews. Multiply this across hundreds of products and thousands of monthly visits, and the cumulative database load becomes a real bottleneck if pages are not cached.
Image weight. Product photography is usually the single heaviest asset type on a store – multiple images per product, often at high resolution to support zoom functionality, displayed across shop grids, single product pages, and related-product widgets simultaneously.
Plugin-heavy frontend. A typical WooCommerce setup runs payment gateway scripts, shipping calculators, review plugins, wishlist plugins, and upsell or cross-sell tools – each adding their own CSS and JavaScript to the page.
Mobile traffic share. Ecommerce traffic skews heavily mobile, and mobile devices process JavaScript more slowly and have less reliable bandwidth than desktop, which exposes any unoptimised script or oversized image far more severely.
BlinkSpeed addresses all four of these directly, provided the right settings are configured for a store rather than a simple blog or brochure site.
Step 1 – Get HTML Caching Working Correctly for a WooCommerce Speed Fix
Go to BlinkSpeed → HTML Caches and enable HTML Caching.
This is the foundation of any WooCommerce speed fix; it eliminates the repeated database queries WooCommerce runs on every single page view by serving a static, pre-rendered version of the page to subsequent visitors instead.
Enable Caching for Pages with GET Parameters
WooCommerce shop and category pages frequently use query strings for sorting (?orderby=price) and pagination (?paged=2). Go to BlinkSpeed → HTML Caches and enable Enable Caching for Pages with GET Parameters. Without this, every sorted or paginated view of your shop bypasses the cache and triggers a fresh, slow render – which on a store with a large catalogue and active filtering can mean a large share of your real browsing traffic never benefits from caching at all.
Enable Preload Caching to Avoid Cold Product Pages
With a catalogue of any meaningful size, many product pages are visited infrequently enough that their cache regularly expires between visits. Go to BlinkSpeed → HTML Caches, enable Preload Caching, and set Preload Pages Per Minute to somewhere between 4 and 8 for a typical store. This runs a background process that keeps your product and category pages pre-warmed in the cache, so even a rarely-visited product page loads from cache rather than forcing the next visitor through a slow, uncached render.
One Important Exception: Cart, Checkout, and Account Pages
It’s worth noting that BlinkSpeed automatically detects WooCommerce and completely excludes the cart, checkout, receipt, confirmation, and My Account pages from this caching system – these pages contain session-specific content (your cart contents, order details, account info) that must never be served as a shared static file to different visitors. This happens automatically with no configuration needed, and it means your settings here apply fully to your shop, product, and category pages without any risk to the personalised parts of the buying flow.
Step 2 – Configure Image Settings for Product Page Optimization
Since product photography is usually the heaviest part of a store, image settings deliver some of the biggest wins for product page optimization.
Enable WebP Conversion
Go to BlinkSpeed → Image Optimization and enable Convert to WebP for both JPG and PNG. WebP delivers the same visual quality as a standard JPEG or PNG at roughly 30–50% smaller file size – a meaningful reduction when multiplied across a catalogue of products, each with several images.
License note: on the free version, WebP conversion only runs on the homepage. Since most shopping activity happens on product and category pages rather than the homepage, getting the full benefit of this feature for a real store requires a premium license, after which you can run BlinkSpeed → Optimize with AI to process your entire catalogue.
Enable Responsive Images
Go to BlinkSpeed → Image Optimization and enable Responsive Images. This serves a smaller, appropriately-sized image to mobile visitors rather than the same full desktop-resolution file – directly relevant given how much shopping traffic happens on phones.
Enable Lazy Loading, With One Key Exception
Go to BlinkSpeed → Image Optimization and enable Lazy Load for images. Product pages typically have a gallery, related-product carousels, and review images further down the page – none of which need to load immediately.
The one image that should never be lazy loaded is the main product photo, since it is very likely your page’s Largest Contentful Paint element. Go to BlinkSpeed → Exclusions → Media Exclusions → Exclude Media from Lazy Loading and add a matching string for it – typically a class like woocommerce-product-gallery__image on default WooCommerce themes – so it loads immediately and with priority instead of waiting for the visitor to scroll.
Step 3 – Configure CSS and JavaScript Optimisation Without Breaking Shop Functionality
Go to BlinkSpeed → CSS Optimization and enable CSS Optimization, then enable Load Critical CSS and run the AI Optimisation process so above-the-fold styles are generated for your product and category templates specifically. Since WooCommerce pages tend to follow a consistent template structure, critical CSS generated once typically applies well across your whole catalogue, speeding up how quickly the price and add-to-cart button visually appear.
Go to BlinkSpeed → JavaScript Optimization, enable Enable JavaScript Optimization, and set Lazyload Javascript to Yes. This minifies your JS and defers non-essential scripts until the visitor interacts with the page, which is one of the more effective ways to improve a stubbornly slow Lighthouse score on a script-heavy storefront.
Protect the Add-to-Cart Script
WooCommerce’s AJAX add-to-cart functionality needs to be ready the moment a shopper clicks the button – and the click itself is the interaction that would otherwise trigger BlinkSpeed’s JavaScript delay system, creating a timing conflict on the very first click. Go to BlinkSpeed → Exclusions → JS Exclusions → Exclude Javascript from Lazyload and add:
| woocommerce/assets/js/frontend/add-to-cart.min.js defer |
The defer modifier keeps the script non-blocking for page render speed while making sure it is active and ready as soon as the HTML finishes parsing, rather than waiting for an interaction.
Protect Variation Scripts on Variable Products
If your store sells products with size, colour, or other variations, add the same kind of protection for the variation script:
| woocommerce/assets/js/frontend/add-to-cart-variation.min.js defer |
A WooCommerce Configuration Checklist
| Setting | Location | Recommended Value |
|---|---|---|
| Enable HTML Caching | HTML Caches | On |
| Enable Caching for GET Parameters | HTML Caches | On |
| Preload Caching | HTML Caches | On, 4–8 pages/min |
| Enable GZIP Compression | HTML Caches | On |
| Enable Leverage Browsing Cache | HTML Caches | On |
| Enable CSS Optimization | CSS Optimization | On |
| Load Critical CSS | CSS Optimization | On |
| Enable JavaScript Optimization | JavaScript Optimization | On |
| Lazyload Javascript | JavaScript Optimization | Yes |
| Exclude add-to-cart.min.js | JS Exclusions | defer modifier |
| Enable Lazy Load (Images) | Image Optimization | On |
| Exclude main product image | Media Exclusions | Add gallery image class |
| Convert to WebP | Image Optimization | On (premium for full catalogue) |
| Responsive Images | Image Optimization | On |
| Fix INP Issues | General Settings | On |
Step 4 – Improve Mobile Speed for Mobile Shoppers
Because so much shopping traffic is mobile, it’s worth checking your mobile-specific settings separately from desktop.
Go to BlinkSpeed → General Settings and enable Fix INP Issues. This adds preconnect hints for third-party domains – particularly relevant for payment gateway scripts, review widgets, and marketing pixels that mobile CPUs take longer to connect to and execute compared to desktop.
Confirm Responsive Images and Convert to WebP are both active, since the combined effect of smaller dimensions and a more efficient format has an outsized impact on mobile load times where bandwidth is more constrained.
Step 5 – Use the AI Optimisation Dashboard to Process Your Catalogue
A common reason a “configured” store still feels slow is that settings were enabled but the actual processing – Critical CSS generation and WebP conversion – has not run yet. Go to BlinkSpeed → Optimize with AI and click Start Optimization. This crawls your site’s URLs and queues each one for Critical CSS extraction and image conversion. For a store with a large catalogue, this can take some time depending on your preload speed setting – check the progress dashboard and confirm your most important category and product pages show as complete before judging results.
Common Reasons a WooCommerce Store Still Feels Slow After Setup
| Symptom | Likely Cause | Fix |
|---|---|---|
| Shop sorting/filtering still feels slow | GET parameter caching not enabled | Enable Caching for Pages with GET Parameters |
| Product pages slow on first visit each day | No preload caching configured | Enable Preload Caching at 4–8 pages/min |
| Add-to-cart button unresponsive on first click | JS lazy load delaying the cart script | Exclude add-to-cart.min.js with defer modifier |
| Product images still large/slow | WebP not running on inner pages | Confirm premium license; run AI Optimisation |
| Hero/main product image loads late | Main image being lazy loaded | Exclude it via Media Exclusions |
| Mobile noticeably slower than desktop | Responsive Images or Fix INP Issues disabled | Enable both settings |
| Cart/checkout/account pages don’t speed up | These pages are intentionally excluded by design | Expected — see note in Step 1 |
Frequently Asked Questions
Q1. What is the single most impactful setting for a WooCommerce speed fix?
For most stores, enabling HTML Caching combined with Preload Caching produces the largest single improvement, since it removes the repeated database queries WooCommerce runs on every page load for pricing, stock, and product data. Image optimisation (WebP and responsive images) is usually the second-biggest factor given how image-heavy most catalogues are.
Q2. Why does my checkout page feel just as slow as before I installed BlinkSpeed?
Checkout, along with cart and account pages, is automatically excluded from BlinkSpeed’s optimisation because it displays session-specific content – your specific cart items, your specific order, your specific account details – that can never safely be cached or shared between visitors. Checkout speed instead depends on your server’s processing speed, how many payment gateways and shipping calculators are active, and how lean your checkout page template is. The faster checkout speed gains from BlinkSpeed come indirectly, by making sure shoppers reach checkout in the first place rather than abandoning a slow product or category page earlier in their visit.
Q3. Will product page optimization actually affect my sales, or just my PageSpeed score?
It affects both, and the sales impact is usually the more meaningful one. Slow product and category pages are associated with higher bounce rates and lower add-to-cart rates in most studies on ecommerce performance. Since shoppers typically browse several product and category pages before deciding to buy, speeding up exactly those pages addresses the part of the shopping journey with the most opportunities to influence whether a sale happens at all.
Q4. Does an ecommerce speed plugin like BlinkSpeed work with WooCommerce extensions like Subscriptions or Bookings?
Generally yes. BlinkSpeed’s core optimisations – HTML caching, CSS/JS optimisation, image handling – operate at the page output level and are compatible with most WooCommerce extensions, since these extensions typically render within WooCommerce’s standard page structure. The same caution that applies to cart and checkout applies to any extension page showing live, session-specific data – such as a subscription management screen or a booking calendar with real-time availability. If you notice incorrect cached content on a page like this, add its specific URL to Exclude Pages from HTML Caching as a precaution.
Q5. How long should I wait after configuring settings before judging the results?
Lab test scores like PageSpeed Insights update immediately once you clear the cache and the AI Optimisation process has completed for the page you’re testing. Real-world improvement, measured through BlinkSpeed’s own Core Web Vitals logs, typically takes a few days of traffic to show a clear pattern. If you’re checking Google Search Console’s Core Web Vitals report specifically, allow up to 28 days, since that report is a rolling average of real visitor data rather than a live snapshot.
Q6. Can a cart performance fix from another plugin be used alongside BlinkSpeed?
It’s not generally recommended to run two plugins optimising the same pages, since overlapping caching or script-handling logic tends to produce unpredictable results. Since BlinkSpeed already leaves cart and checkout untouched by design, a separate plugin focused specifically on cart functionality (such as a persistent cart across devices, or an AJAX cart drawer) can be used without conflicting with BlinkSpeed’s optimisation of the rest of the store.
Q7. My store has thousands of products. Will the AI Optimisation process handle that?
Yes, though it will take longer than a small catalogue. The process works through your URL queue at the rate set in Preload Pages Per Minute, so a very large catalogue will take proportionally longer to fully process for Critical CSS and WebP conversion. You don’t need to wait for the entire catalogue to finish before benefiting – pages are usable and improved as soon as they’re individually marked complete, and BlinkSpeed processes new or updated product pages incrementally rather than requiring a full restart each time.
Summary
A genuinely effective BlinkSpeed WooCommerce optimization setup focuses on the pages that carry the most traffic and the most weight – shop pages, product pages, and category archives – with HTML caching, preload caching, WebP conversion, responsive images, lazy loading, and Critical CSS all configured specifically with a catalogue-driven site in mind. A small number of targeted JavaScript exclusions, like deferring the add-to-cart script, keep core shopping functionality reliable while everything else stays fully optimised.
Cart, checkout, and account pages are automatically excluded from this optimisation since they show personalised, session-specific content that should never be cached – this is expected behaviour, not something to configure around. Run through the checklist above, complete the AI Optimisation process for your catalogue, and check mobile settings separately given how much shopping traffic happens on phones, and most of the slowness reported on a WooCommerce store resolves without any risk to the buying process itself.
