How to reduce WooCommerce wc-ajax=get_refreshed_fragments overhead

How To Implement

• 1 Check version and current behaviour before changing anything

  Go to WooCommerce > Status and note the WC Version, active theme, and any template overrides. WooCommerce says that from 7.8 onwards, cart fragments stopped being enqueued on all routes by default, so a current store that still fires get_refreshed_fragments on non-cart pages is usually opting back in through theme or plugin behaviour.

• 2 Confirm where the request fires and what triggers it

  Open the homepage, a category page, a product page, and one non-shop content template. In Chrome DevTools > Network, filter for get_refreshed_fragments, then inspect the Initiator column or the request’s Initiator tab. Chrome documents that this shows what caused the request; WooCommerce says the common post-7.8 causes are a rendered Cart widget, a third-party script registering cart-fragments as a dependency, or code that explicitly enqueues the script.

• 3 If the store uses a block theme or Site Editor header, move to the Mini-Cart block

  In block-theme setups, edit the header in Appearance > Editor and use the Mini-Cart block/template part rather than a legacy widget-based cart. WooCommerce’s Mini-Cart docs show the template part under Appearance > Editor > Patterns > Template Parts > Mini-Cart. WooCommerce also says the Mini-Cart block does not use the cart-fragments API; from 10.4, the Interactivity API Mini Cart is the default implementation and WooCommerce says it ships smaller JavaScript bundles.

• 4 Handle classic themes differently

  If the Cart widget lives in a widget area, replace that widget with the Mini-Cart block in the same header/sidebar area where the theme allows it. If the theme hard-codes the mini-cart widget in a PHP template, this is a theme/template job: WooCommerce explicitly warns that some classic themes do this, including Storefront-era patterns, so removing a widget in WP Admin alone may not stop the request.

• 5 Use the quickest no-code reduction if you need a safe first step

  In Perfmatters > General > WooCommerce, enable Disable Cart Fragmentation. Perfmatters says this checks for the woocommerce_cart_hash cookie and disables fragments when no cart is present. Measurement note: capture a before/after waterfall and run a live add-to-cart test immediately after saving, because a plugin toggle can reduce load while still breaking a theme’s expected cart behaviour.

• 6 If you must keep the legacy widget for now, scope the script to cart-relevant pages only

  WooCommerce documents the following woocommerce_get_script_data filter so wc-cart-fragments still loads but does not execute outside Woo/cart/checkout routes:

  “php add_filter( 'woocommerce_get_script_data', function( $script_data, $handle ) { if ( 'wc-cart-fragments' === $handle ) { if ( is_woocommerce() || is_cart() || is_checkout() ) { return $script_data; } return null; } return $script_data; }, 10, 2 ); “

  Use this via a child theme or a snippets plugin, not by editing core files. WooCommerce’s own caveats matter here: custom pages that behave like shop/cart pages but do not meet those conditional checks may stop updating correctly, and cached pages that still expose a mini-cart can show stale cart state.

• 7 Validate on a real mobile device before sign-off

  Chrome’s docs state that remote debugging real devices gives the best feel for performance and touch, so do the final check on a real Android handset using Chrome remote debugging rather than desktop emulation alone. Test home/category/product pages, add an item, confirm the header cart count or drawer updates, then open cart and checkout. If you are on WooCommerce 10.4+, also test any extension that customises Mini Cart behaviour because WooCommerce flags that as a compatibility check for the new Interactivity API default.

How To Measure

Pitfalls

• Mistake: disabling fragments globally when a live header cart is still central to the UX. WooCommerce’s own caveats say non-standard cart-like pages can stop updating correctly, and cached pages that expose a mini-cart may not refresh to the shopper’s session if you scope execution too aggressively.
• Mistake: solving the symptom, not the cause. Delaying or disabling the script can reduce the waterfall cost, but WooCommerce’s preferred structural fix is to replace the legacy Cart widget with the Mini-Cart block, especially if the theme or plugin stack is still depending on the old widget.
• Mistake: trusting desktop simulation as the final word. Google distinguishes lab data from field data, and Chrome notes that real-device remote debugging gives the best feel for performance and touch; for this technique, sign-off should happen on a physical handset.
• Edge case: assuming 10.4’s new Mini Cart is always drop-in safe. WooCommerce says the Interactivity API Mini Cart is now the default, but extensions that customise Mini Cart behaviour should be tested against it.

Examples

FAQs

Sources & Further Reading

• WooCommerce 10.4: The Interactivity API Mini Cart Goes Live – Official release note confirming that the Interactivity API Mini Cart became the default in 10.4, with smaller JS bundles and extension-testing caveats. Published 10 December 2025.
• Understanding the Interactivity API-driven future for WooCommerce Blocks – Useful context on how WooCommerce is moving interactive blocks, including MiniCart, towards the Interactivity API. Published 30 October 2025.
• Mini-Cart block Documentation – Official user documentation for where the Mini-Cart lives in headers and how to access/edit the Mini-Cart template part in the Site Editor. Date not stated on page; accessed 18 June 2026.
• Understanding the WooCommerce System Status Report – Official reference for checking WooCommerce version, theme, blocks package and template overrides before diagnosing the issue. Date not stated on page; accessed 18 June 2026.
• Disable WooCommerce cart fragments AJAX – Vendor documentation for the Perfmatters toggle, including its woocommerce_cart_hash cookie logic and admin path. Treat performance claims as vendor-directional. Date not stated on page; accessed 18 June 2026.
• Optimize WooCommerce get refreshed fragments – Vendor note explaining why synthetic tests often show the request on each run and how cached empty-cart responses are handled. Last updated 9 November 2023.
• Inspect network activity – Official Chrome DevTools doc confirming that the Initiator field shows what caused a resource request, which is useful when tracing get_refreshed_fragments. Published around late 2024 in search metadata; exact on-page publish date not surfaced in retrieved excerpt.
• Remote debug Android devices – Official method for testing the change on a real Android device. Published 13 April 2015.
• Document request latency – Official Chrome guidance linking TTFB to document latency and citing the commonly used 800 ms TTFB benchmark. Published 27 March 2025.
• Web Vitals – Google guidance for the Core Web Vitals thresholds used here: LCP ≤2.5s, INP ≤200 ms, CLS ≤0.1 at the 75th percentile. Date not surfaced in retrieved excerpt; accessed 18 June 2026.
• Why lab and field data can be different – Google explanation of why lab waterfalls and real-user data can disagree, and why field data should guide prioritisation. Last updated 18 July 2022.
• Measure ecommerce – Official GA4 ecommerce event reference for add_to_cart, view_cart, begin_checkout, purchase and related measurement. Updated 4 May 2026.

About This Page

• Written By: Eliot Webb – Founder & WooCommerce CRO Consultant
• Last Reviewed: 18 Jun 2026
• Last Updated: 18 Jun 2026