Blocksy ships no page builder of its own — normally paired with Elementor or plain Gutenberg, each already covered by its own adapter. Blocksy's own footprint is template chrome and the header builder's mobile/off-canvas menu, both plain static HTML, plus a WooCommerce mini-cart flyout in the header builder that needs a live cart-fragments bridge.
Static + Bridges
Every template file renders plain server-side HTML, and the header builder's mobile/off-canvas menu toggle is a client-side class swap with no server round-trip.
The header builder's WooCommerce cart flyout needs a live request each time its count and contents refresh; everything else on the page is static.
WooCommerce core's own cart-fragments endpoint (wc-ajax=get_refreshed_fragments) refreshes the header cart flyout's live count and contents — the same dependency the WooCommerce integration already declares, surfaced here because Blocksy's header builder is what places the widget.
No special setup — detected automatically once active.
This classification is rule-derived from reading Blocksy's theme code, not from testing against a live install. It covers Blocksy's own theme layer only — the separate Blocksy Companion plugin's AJAX product filters (its Pro tier) aren't declared here, since that plugin's own behavior would need its own adapter if profiled.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp