TurboBlocks
Disable unused CSS and JavaScript on WooCommerce sites with per-page rules and context-aware detection. Reduce page weight and improve Core Web Vitals without breaking checkout.
Why it exists
Generic "disable scripts" plugins treat every site the same. WooCommerce is not the same. It enqueues wc-cart-fragments, wc-add-to-cart, Woo Blocks vendor bundles and payment gateway scripts on every page, including your homepage, blog and landing pages, where none of it actually runs.
Most optimisation plugins give you a switch to turn Woo assets off globally. Then someone adds a mini-cart to the footer, or a product shortcode to a landing page, and it silently breaks.
TurboBlocks adds a content-aware layer in front of that switch: it keeps Woo handles on any page that genuinely contains a mini-cart widget, a Woo shortcode, or a woocommerce/* block, and strips them everywhere else.
What it does
Why it matters
Page weight is the most common cause of failing Core Web Vitals on WooCommerce sites. Cutting unused assets is the highest-leverage fix available, and the only reason it is not done more often is the risk of breaking checkout.
Requirements
Frequently asked questions
Will this break my checkout?
Preventing exactly that is the point of the detection layer. TurboBlocks does not strip WooCommerce assets from any page that actually contains a mini-cart widget, a Woo shortcode or a woocommerce/* block, and cart and checkout pages keep their handles. Where detection cannot infer intent, you set a per-page override.
How is this different from a caching plugin?
A caching plugin serves the same page faster. TurboBlocks makes the page smaller by not loading CSS and JavaScript that page never uses. They solve different problems and are usually run together.
Which WooCommerce assets does it know about?
It ships a catalogue covering WooCommerce Core, Woo Blocks vendor bundles, Stripe, PayPal and shipping handles, each with its own declared page conditions rather than a single global on/off.
Do I need to configure it page by page?
No. The content-aware detection handles the common cases on its own. Per-page overrides exist for the exceptions — a landing page that builds a product grid in a way detection cannot see, for example.
How do I get TurboBlocks?
It is not in the WordPress.org directory yet. The source is on GitHub, and you can contact us for a packaged build or to have it configured against your store.
Related plugins
Zignites Sentinel
Create a checkpoint of your active theme and plugins before updating, validate that the checkpoint is sound, and restore it if an update breaks the code layer.
View UtilitiesSite Extensions Snapshot
View every installed plugin and theme with status, version and author, then export the lot to CSV in one click. Built for audits, compliance checks and client handovers.
View WooCommerceReviewBoost Pro
Transform your WordPress site into a review powerhouse. Collect, manage, and display customer reviews with advanced features like review incentives, automated follow-ups, and rich snippets integration.
ViewInterested in TurboBlocks?
Tell us about your site and we will send you a build or quote the work.