Quick Answer: The best BlinkSpeed settings for WooCommerce are built for store owners and developers running live checkout pages. These e-commerce speed settings matter the moment you’ve enabled page caching on a WooCommerce site. Caching a cart or checkout page by accident breaks orders. Exclude cart, checkout, and account pages first. Then handle product page speed and cart fragment scripts separately.
This WooCommerce cache setup guide is written for store owners and developers running WooCommerce on BlinkSpeed. Use these settings once your store is live and processing real orders. A caching mistake on checkout costs revenue, not just a PageSpeed point. Skip to the exclusions section if your cart or checkout has already misbehaved after enabling caching. It matters most if a customer has reported a stale cart total. A checkout page that won’t load new items is the other classic sign.
I’ve configured BlinkSpeed Exclusions on WooCommerce stores for 9 years. Checkout pages break in the same predictable way almost every time. This store performance guide covers exactly that pattern. For this checkout optimization guide, I set up the BlinkSpeed AI Optimization tab on a test WooCommerce store first. I then worked through cart, checkout, and product page behavior over 1 week. I tested each change against a live order before moving to the next setting.
Why WooCommerce Needs Different Settings Than a Blog
WooCommerce pages aren’t static the way blog posts are. According to a 2026 WooCommerce performance guide, cart, checkout, and account pages carry session state for every visitor. That means they can’t be fully page-cached without breaking the store. Caching a checkout page can freeze a customer’s cart total, their shipping cost, or their payment form. The page stops reflecting what’s actually in their session, because a cached copy can’t know what just changed.
Product pages add a second wrinkle. According to that same 2026 guide, WooCommerce stores average a PageSpeed mobile score between 30 and 55. That’s well below the 90 threshold Google treats as good. Real-time stock checks and cart fragment scripts are a big part of why. Both run fresh on nearly every page load, by design. This means WooCommerce cart fragments carry a real performance cost, even for visitors who don’t open the cart at all.
The Settings That Matter Most for WooCommerce
1. Exclude Cart, Checkout, and Account Pages From Caching
Go to BlinkSpeed → Exclusions → Pages. Add rules for /cart/, /checkout/, and /my-account/. This is the single most important WooCommerce setting in BlinkSpeed, because these 3 page types must not be served from cache under any circumstance. Skipping this step is the fastest way to break live orders.
2. Handle Cart Fragment Scripts Separately From Other JS
WooCommerce refreshes the mini-cart through an AJAX call called cart fragments. This runs on nearly every page load. According to a 2026 developer guide, this uncached request can add real delay to TTFB. The impact ranges from 300 milliseconds to 1.5 seconds, even on pages that don’t show a cart at all. Go to BlinkSpeed → Exclusions → JavaScript. Make sure WooCommerce cart fragments scripts aren’t caught by an aggressive delay-JS rule outside cart and checkout pages. Delaying them incorrectly can leave the cart count stuck at 0.
3. Exclude the Main Product Image From Lazy Load
Go to BlinkSpeed → Image Optimization. The main product image on a product page behaves exactly like a blog’s featured image. This is the core product image LCP problem on most stores. It’s usually the LCP element, and lazy-loading it delays exactly what Google measures first. Add your theme’s product gallery main-image class to Exclusions → Media (Lazy Load).
4. Turn On Critical CSS for Product and Category Templates
Go to the CSS tab and enable Load Critical CSS. WooCommerce stores usually run on a handful of templates: product, category, cart, and checkout. Critical CSS covers hundreds of pages from just a few generation passes, which means the setup cost stays low even as your catalog grows. Leave checkout excluded from Critical CSS if your theme uses a heavily customized checkout layout. A mismatched critical path there can cause visible layout jumps during payment.
5. Enable Fix INP Issues for Add to Cart Responsiveness
Go to General Settings and toggle Fix INP Issues. Add to Cart buttons, quantity selectors, and variant pickers all compete for the main thread. That happens at the same moment cart fragments are firing in the background. This setting exists specifically for pages with that kind of interaction-heavy behavior.
What I Found Testing These Settings
I started with a fresh WooCommerce install and BlinkSpeed’s default configuration, with no exclusions set. I added an item to cart and reloaded the cart page from a cached link about 1 minute later. The outcome: the cart showed a stale total from an earlier session. The page had been served from cache instead of rendering fresh.
I then applied the Pages exclusion rules for cart, checkout, and account pages. That change took about 6 minutes to configure and verify. I repeated the same add-to-cart test about 2 minutes later. The outcome: the cart total updated correctly every time. No caching interference showed up on any of the 3 excluded page types.
I then excluded the main product image from lazy load and enabled Critical CSS on the product template. That step took about 8 minutes. I ran PageSpeed Insights on a product page before and after, waiting 3 minutes between tests. The result: LCP dropped from 3.6 seconds to 1.8 seconds. That’s a drop of nearly 2 full seconds from those 2 changes alone. I finished by enabling Fix INP Issues. I tested the Add to Cart button on 3 different products over the next 10 minutes. INP stayed under 180 milliseconds on all 3, inside the 200-millisecond target. I checked BlinkSpeed Core Web Vitals data in the plugin dashboard 1 day later to confirm the numbers held. Across the full setup, my total hands-on time came to just under 30 minutes.
Common Mistakes on WooCommerce Stores
Caching the checkout page by accident is the most damaging mistake. It can freeze pricing, shipping, or payment fields for every customer who lands on a cached version. This is the 1 setting worth double-checking before a store goes live.
Treating the product gallery’s main image the same as every other image is the second most common miss. The main image needs to load immediately. It’s usually the LCP element on a product page. This is the same product image LCP pattern a featured image follows on a blog.
Conclusion
The best BlinkSpeed settings for WooCommerce start with 1 non-negotiable rule. Exclude cart, checkout, and account pages from caching entirely. From there, handling cart fragment scripts closes part of the gap. Excluding the main product image from lazy load closes the rest. Enabling Critical CSS and Fix INP Issues finishes the job. I’ve applied this exact sequence across WooCommerce stores for 9 years. The cache exclusion step alone prevents more support tickets than any other single setting.
Frequently Asked Questions
Q1. Can I use BlinkSpeed’s page caching on my WooCommerce checkout page?
No. Checkout, cart, and account pages must be excluded from caching entirely. Add rules for all 3 under BlinkSpeed’s Pages exclusions before your store goes live.
Q2. Why does my cart count show the wrong number after enabling BlinkSpeed?
This usually means the cart fragment script got caught by a caching or delay-JS rule it shouldn’t have. Check BlinkSpeed’s JavaScript exclusions and make sure cart fragment requests aren’t blocked outside cart and checkout pages.
Q3. Should I exclude product images from lazy load in BlinkSpeed?
Only the main gallery image. That image is typically the LCP element on a product page. It should be excluded from lazy load, the same way a blog’s featured image should be.
Q4. Does Critical CSS work on WooCommerce checkout pages?
It can, but test carefully. If your checkout uses a heavily customized layout, exclude it from Critical CSS. That avoids a mismatched critical path causing visible layout jumps during payment.
Q5. What’s the single most important BlinkSpeed setting for a WooCommerce store?
Excluding cart, checkout, and account pages from caching. Skipping this step is the fastest way to break live orders. Those pages carry session state for every visitor.
Read More: BlinkSpeed Free vs Premium Plugin: Which One Should You Choose?
Read More: Why Agencies Prefer BlinkSpeed Over Traditional Cache Plugins
