WooCommerce 11.1 skips block registration on API requests — and says Store/REST calls are 30–42% faster

WooCommerce 11.1 introduces a BlockRegistrationContext guard that skips WooCommerce block and pattern registration on requests that cannot render or edit blocks. Woo says its benchmarks found Store API and REST requests 13–18 milliseconds, or roughly 30–42%, faster. Front-end, admin and block-editor contexts continue registering blocks normally. Extensions that intentionally render Woo blocks in a context now skipped can opt back in with the `woocommerce_should_register_blocks` filter. The same release also brings product variation image galleries into core and migrates functionality from the former Additional Variation Images extension.

WordPress and WooCommerce bootstrap a large amount of framework and block infrastructure on each request. Avoiding work that cannot affect an API response is a straightforward performance win, but it changes an implicit extension assumption: Woo blocks are no longer guaranteed to be registered in every request context. That makes 11.1 both a performance release and a compatibility boundary for extensions doing unusual server-side block rendering.

The new registration context identifies requests where WooCommerce blocks and patterns cannot be rendered or edited and skips their initialization. Woo’s own measurements report a 13–18 ms reduction on Store API and REST requests, corresponding to about 30–42% in the tested paths.

Extensions that depend on Woo blocks in a skipped context can return true from the `woocommerce_should_register_blocks` filter. That makes the new default explicit: unusual integrations should opt into the cost rather than every API request paying it.

WooCommerce 11.1 also integrates variation image-gallery functionality into core and includes migration behavior for the previous extension. Stores and extensions that customized that feature should test the upgrade separately from the API performance improvement.