FiboSearch – Ajax Search for WooCommerce vs Zero Blocks Given

The most popular WooCommerce product search plugin. It gives your users a well-designed advanced AJAX search bar with live search suggestions. By default, WooCommerce provides a very simple search solution, without live product search or even SKU search. FiboSearch (formerly Ajax Search for WooCommerce) provides advanced search with live suggestions. Who doesn’t love instant, as-you-type suggestions? In 2025, customers expect smart product search. Baymard Institute’s latest UX research reveals that search autocomplete, auto-suggest, or an instant search feature is now offered on 96% of major e-commerce sites. It’s a must-have feature for every online business that can’t afford to lose customers. Why? FiboSearch helps users save time and makes shopping easier. As a result, Fibo really boosts sales. Features ✅ Search by product title, long and short description ✅ Search by SKU ✅ Show product image in live search results ✅ Show product price in live search results ✅ Show product description in live search results ✅ Show SKU in live search results ✅ Mobile first – special mobile search mode for better UX ✅ Details panels with extended information – “add to cart” button with a quantity field and extended product data displayed on hovering over the live suggestion ✅ Easy implementation in your theme – embed the plugin using a shortcode, as a menu item or as a widget ✅ Terms search – search for product categories and tags ✅ Search history – the current search history is presented when the user clicked/taped on the search bar, but hasn’t yet typed the query. ✅ Limit displayed suggestions – the number is customizable ✅ The minimum number of characters required to display suggestions – the number is customizable ✅ Better ordering – a smart algorithm ensures that the displayed results are as accurate as possible ✅ Support for WooCommerce search results page – after typing enter, users get the same results as in FiboSearch bar ✅ Grouping instant search results by type – displaying e.g. first matching categories, then matching products ✅ Google Analytics support ✅ Multilingual support including WPML, Polylang and qTranslate-XT ✅ Personalization of search bar and autocomplete suggestions – labels, colors, preloader, image and more Try the PRO version FiboSearch also comes in a Pro version, with a modern, inverted index-based search engine. FiboSearch Pro works up to 10× faster than the Free version or other popular search solutions for WooCommerce. Upgrade to PRO and boost your sales! PRO features ✅ Ultra-fast search engine based on the inverted index – works very fast, even with 100,000+ products ✅ Fuzzy search – works even with minor typos ✅ Search in custom fields with dedicated support for ACF ✅ Search in attributes ✅ Search in categories. Supports category thumbnails. ✅ Search in tags ✅ Search in brands (We support WooCommerce Brands, Perfect Brands for WooCommerce, Brands for WooCommerce, YITH WooCommerce Brands). Supports brand thumbnails. ✅ Search by variation product SKU – also shows variable products in live search after typing in the exact matching SKU ✅ Search for posts – also shows matching posts in live search ✅ Search for pages – also shows matching posts in live search ✅ Synonyms ✅ Conditional exclusion of products ✅ TranslatePress compatible ✅ Professional and fast help with embedding or replacing the search bar in your theme ✅ and more… ✅ SEE ALL PRO FEATURES! Showcase See how it works for others: Showcase. Feedback Any suggestions or comments are welcome. Feel free to contact us via the contact form.

Most WooCommerce stores ship 80-150 KB of block CSS and JS that the store never actually renders. The WC BlockPatterns scanner is the one that bugs me most – it hits the filesystem on every request to scan a directory of pattern templates you don’t use. Then add core WP global-styles, wp-block-library and font-faces on top, and you’re loading a Gutenberg frontend you probably switched off a long time ago. Zero Blocks Given turns it off at the source, through WooCommerce’s own dependency injection container. No CSS dequeue band-aid, no UI checkboxes, no PRO upsell. One constant in wp-config.php, pick a tier, done. How it works Here’s the thing – WC registers its block hooks as closures wrapping instance methods on container-managed objects. So you can’t remove_action() them by string. You have to fetch the same instance back from the DI container and pass it in as the callable. That’s what this does: $bp = \Automattic\WooCommerce\Blocks\Package::container()->get( BlockPatterns::class ); remove_action( 'init', [ $bp, 'register_block_patterns' ] ); The DI-container path is the one that survives WC upgrades cleanly. String-callback matching and dequeue tricks tend to drift every release, so I went with the container. Four modes. Three ways to set them. Mode What it turns off When to use it patterns WC BlockPatterns directory scanner only Block-based Cart/Checkout – keeps all blocks rendering, just skips the file-I/O scan blocks patterns + BlockTypesController + Notices styles + wc-blocks-style handle Classic-shortcode WC stores all blocks + WP global-styles pipeline + theme.json + font-faces + head strip Sites with no Gutenberg frontend at all nuclear all + unregister_block_type() for every core block Page-builder sites – strips the editor inserter clean Default is all. Set the mode you want with any of these: The settings – click the Settings link on the Plugins screen. Native HTML dialog, four radios, save. No menu items, nothing else added to your admin. A constant in wp-config.php – define( 'ZEROBLG_MODE', 'patterns' );. This wins over the dialog. Good devops escape hatch. A filter in a theme or mu-plugin – add_filter( 'zeroblg/mode', fn() => 'blocks' );. Used when neither the constant nor the dialog set a value. Resolution order: constant, then settings, then filter, then all. An invalid value at any step just falls through to the next. A few real cases Service-form site on WC. You sell consultations, not products – no cart, no checkout. mode=all strips every block stylesheet across the site. Classic-shortcode WC store. You use [woocommerce_cart] and [woocommerce_checkout], no block UI. mode=blocks turns off the block frontend without touching your classic flow. Block-checkout store with bloated patterns. You run the new Cart/Checkout blocks but never the WC pattern library. mode=patterns skips just the directory scanner – saves the disk hit, leaves your checkout alone. FrankenPHP / worker mode. All hooks are idempotent, no $GLOBALS writes, \Throwable catches around the DI lookups. Safe in a worker. Elementor / Divi WC stores. The page builder renders its own checkout, so mode=all clears the WC and WP block CSS your theme never uses anyway. Why I built it this way Activate it and it works – mode=all is the default, no setup needed. No settings page to learn. One constant or one filter is the whole API. Pure PHP. No database rows, no admin scripts, no frontend JS. No external requests, no tracking, nothing phoning home. GDPR is a non-issue. It uses the same Package::container() lookup as WC core, so it follows WC’s own object lifecycle instead of guessing. Worker-safe – FrankenPHP, Roadrunner, Swoole. No die, no exit, no session writes. mu-plugin friendly. Drop the folder into wp-content/mu-plugins/ and it loads itself. GPL, no upsells. No PRO tier, no Freemius, no admin notice nagging you for a review. From the maker of WP Multitool This plugin handles the frontend block bloat. If you also want the backend cleaned up, that’s what WP Multitool does – slow queries, autoload bloat, the database bottlenecks that caching plugins just hide instead of fixing. Most optimization plugins guess at the problem. WP Multitool runs EXPLAIN and shows you. 14 tools in there – slow-query analyzer, autoload optimizer, index suggestions, fatal-error recovery – and a free site scanner if you want to see what’s slow before paying for anything. If Zero Blocks Given earned a spot in your stack, that one probably will too.