Skip to content
FFuzzy

How-to

Optimize Large Catalog Performance

Use index tables, cache, count modes, and rebuild workflows to keep large WooCommerce catalogs responsive.

Updated May 25, 2026SEO-ready

When to use this

Use this when your store has a large catalog and filtering feels slow, or when you expect the catalog to grow and want to set safe defaults early.

Before you start

  • You have a working filter on a storefront page.
  • You can do a quick test after a big catalog change, such as a large import.

What affects speed

  • Index tables let Fuzzy read prepared data instead of scanning everything

    • on each request.

  • Caching reuses filter results so repeat requests are cheaper.
  • Count mode decides how the per-value counts are produced. Static and

    • instant modes are lighter; live counts recalculate the most.

  • Live counts and random sorting get heavier as the catalog grows.

Steps

  1. Enable index tables so filtering reads from the prepared index.
  2. Turn on result caching so repeated filter requests reuse work.
  3. Choose a count mode that fits catalog size. Prefer a lighter mode over

    4. live counts on large catalogs.

  4. Be cautious with random sort on large catalogs, since it is heavier.
  5. Rebuild the index after big catalog changes, such as a bulk import or

    6. mass attribute edit, so the index matches the current data.

  6. Retest a typical filter combination and confirm it responds quickly.

Expected result

Filtering stays responsive on a large catalog, counts are accurate enough for shoppers, and the index reflects the current products after major changes.

Troubleshooting

  • Counts look wrong after an import. Rebuild the index.
  • Still slow with everything on. Switch to a lighter count mode and avoid

    • random sort on the largest pages.

  • Explanation: How index tables work and why they exist.
  • Explanation: Why live counts and random sort get heavier on large catalogs.
  • Reference: Plugin Settings — Performance.