WooCommerce Filter Plugin Comparison: 10,000 items
Super Speedy Filters, WooCommerce core filters and HUSKY were tested on the same 10,000 catalogue items: 2,000 variable products plus 8,000 variations, with the same four filters and ten semantic request cases. Each configuration ran with Redis object caching off and on.
WooCommerce core recorded the lowest averages in this narrow 10,000-item catalogue test. Super Speedy Filters was close, while HUSKY used more PHP time and CPU in both cache modes. Every configuration returned the expected product count for all 20 recorded requests.
Side-by-side request performance
| Plugin | Redis | Correct | First TTFB | Second TTFB | PHP render | DB queries | Peak PHP memory | CPU core-seconds |
|---|---|---|---|---|---|---|---|---|
| Super Speedy Filters | Off | 20/20 | 151.880 ms | 152.550 ms | 104.094 ms | 119.70 | 18.00 MiB | 5.098 |
| Super Speedy Filters | On | 20/20 | 158.630 ms | 148.420 ms | 95.889 ms | 8.35 | 16.50 MiB | 4.736 |
| WooCommerce core filters | Off | 20/20 | 139.700 ms | 141.170 ms | 92.662 ms | 101.40 | 16.00 MiB | 3.755 |
| WooCommerce core filters | On | 20/20 | 142.030 ms | 130.690 ms | 83.234 ms | 4.10 | 16.00 MiB | 3.369 |
| HUSKY | Off | 20/20 | 213.490 ms | 207.430 ms | 159.226 ms | 168.05 | 16.50 MiB | 6.139 |
| HUSKY | On | 20/20 | 190.950 ms | 158.950 ms | 123.478 ms | 13.45 | 16.10 MiB | 5.159 |
The second request is useful for observing warm-cache behaviour, but it is not a substitute for the first request. For uncached users, the first pass is the relevant figure. For stores with persistent object caching, both passes matter.
Site response during the workload
| Plugin | Redis | Visitor TTFB during | wp-admin TTFB during |
|---|---|---|---|
| Super Speedy Filters | Off | 218.325 ms | 184.325 ms |
| Super Speedy Filters | On | 223.725 ms | 175.225 ms |
| WooCommerce core filters | Off | 158.725 ms | 125.100 ms |
| WooCommerce core filters | On | 148.000 ms | 148.875 ms |
| HUSKY | Off | 280.180 ms | 188.680 ms |
| HUSKY | On | 217.660 ms | 147.640 ms |
What the result means
WooCommerce core recorded the lowest averages in this narrow 10,000-item catalogue test. Super Speedy Filters was close, while HUSKY used more PHP time and CPU in both cache modes. These are performance results for a fixed configuration, not a complete feature comparison. WooCommerce core has no separate plugin cost, Super Speedy Filters is built for richer filter and SEO behaviour, and HUSKY has its own interface and feature trade-offs.
Method, versions and reproducibility
The catalogue contained 2,000 variable products and 8,000 variations. Each configuration ran the same ten semantic cases twice in a fixed order, starting with the shop page. The cases covered the shop, category, brand, colour, size and combined filters. Every recorded request returned the expected product count.
| Component | Value |
|---|---|
| Server | 4 AMD EPYC-Genoa vCPUs, 8.12 GB RAM and SSD storage |
| Stack | WordPress 7.0.4, WooCommerce 10.3.8, PHP 8.2.33 and MariaDB 10.11.17 |
| Tested software | Super Speedy Filters 6.47.2, WooCommerce core filters 10.3.8, HUSKY – Products Filter for WooCommerce Professional 1.4.3.1 |
| Catalogue | 10,000 catalogue items: 2,000 variable products plus 8,000 variations |
| Catalogue SHA-256 | eb4f3cf707c171af242b9f4d3aee35cf900c169fb56b7e870e9eb478bd9334b4 |
| Correctness | 20 of 20 requests correct in every configuration |
Download the complete reproduction ZIP. It contains the exact catalogue CSV, the ten-case corpus, scenarios, effective configurations, environment and software inventories, a reproduction guide and SHA-256 checksums. Plugin packages are not included.
Inspect the complete compact result JSON, chart data or readable data report.
This is one controlled run per plugin and cache mode. The exact files and configurations are published so the benchmark can be reproduced independently.
Comments