Trader Information
Back to topOverview
Back to topVarnish is a high-performance HTTP reverse proxy and full-page cache that many Adobe Commerce and Magento Open Source stores put in front of the application to serve category, product, and CMS pages straight from memory instead of rebuilding them on every request. It is the caching engine Adobe recommends for production, and Magento also ships a built-in Full Page Cache (FPC) that works the same way for smaller stores. Either cache only helps once a page has been requested at least once: the very first shopper to open a given category or filtered view still pays for a full, uncached render, and after every deploy, cache flush, or reindex the whole cache starts empty again. PPL Category Filter Cache Warmer closes that gap, a standalone full-page-cache warmer that pre-fills your existing Full Page Cache or Varnish before shoppers arrive, so the first click on a category or layered-navigation filter page is served from cache instead of a slow full render. It crawls your category pages and, optionally, the first layered-navigation filter levels for each store, requesting them exactly the way a guest visitor would - never overriding cache keys, editing your VCL, or purging - and reports a per-URL HIT / MISS / UNCACHEABLE result after each deploy, cache flush, or reindex so you can confirm coverage.
Features
- Crawls category pages and, optionally, the first layered-navigation filter levels for each store.
- Sends plain guest GET requests using the storefront's own rendered layered-navigation links, so only valid, in-stock, same-origin combinations are warmed.
- Strips sort, pagination, page-size, and marketing parameters, warming only the default view.
- Reports HIT / MISS / UNCACHEABLE per URL, from the command line or on a cron schedule.
- Works with both the built-in Full Page Cache and Varnish, filling your existing cache only - it never overrides cache keys, changes VCL, or purges.
- Store-scoped configuration with breadth caps, parallelism, timeout, and TLS controls.
- Fully standalone: no PPL module and no third-party extension required.
Standalone and safe
The warmer only fills your existing cache; it never overrides cache keys, changes VCL, or purges. Your cache stack keeps full control over cache keys, X-Magento-Vary, and tag-based invalidation. Configuration is store-scoped, with breadth caps, parallelism, timeout, and TLS controls so a warm-up run stays within limits you set.
Ideal for
Merchants and agencies on Adobe Commerce or Magento Open Source who use the built-in Full Page Cache or Varnish and want the first shopper on each category and filter page to hit a warm cache after every deploy, cache flush, or reindex.
Compatibility
Supports the 2.4 environments listed in the Marketplace compatibility matrix, with exact PHP and package requirements declared in composer.json. Works with the built-in Full Page Cache and with Varnish. No PPL foundation module and no third-party extension is required.
Varnish is a trademark of Varnish Software AB. This extension is developed by PPL and is not affiliated with, endorsed by, or sponsored by Varnish Software AB.
Technical Specifications
Back to topSeller profile
Pawel Pliousnin Digital Solutions
Seller contact
Current Version
1.3.0
Adobe Commerce platform compatibility
Adobe Commerce (cloud): 2.4 (current)
Adobe Commerce (on-prem): 2.4 (current)
Magento Open Source: 2.4 (current)
Type
Stable Build
Updated
21 August, 2026
Categories
Extensions, Site Optimization, Performance
Documentation
License Type
Policy
Quality Report
Back to topAll tests were conducted on the latest versions of Adobe Commerce that existed for the compatible release lines at the moment of the extension submission. Latest versions of all other software were used, as applicable.
Release Notes
Back to top1.3.0:
- Compatible with Adobe Commerce (cloud) : 2.4
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
1.3.0
Initial release.
Highlights
- Warms Magento category, layered-navigation and toolbar URLs through real guest HTTP requests for both Magento's
built-in full-page cache and Varnish.
- Supports Luma and Hyva storefronts with native Magento layered navigation.
- Integrates with PPL Discovery Filters and warms both the full listing page and the cacheable AJAX fragment
(`ppl_df_fragment=1`) used by filter clicks, clear-all actions and browser-history navigation.
- Discovers filter, sorting, direction, page-size, view-mode and pagination actions from rendered storefront
markup instead of relying on catalog assumptions.
- Provides admin configuration, a customer-defined cron schedule in Magento's configured admin time zone and
the `ppl:cfcw:warm` command with store selection, category-only mode and fail-on-error support.
- Adds a form-key-protected Queue Warm Run button. It creates a one-off background Magento cron job for all
active, enabled store views without blocking the configuration page or requiring the recurring schedule.
- Prevents overlapping CLI and cron runs with a shared lock and reports HIT, MISS, UNCACHEABLE, UNKNOWN and ERROR
totals.
Performance and cache efficiency
- Uses bounded parallel HTTP requests and streams terminal pages and AJAX fragments without buffering their full
response bodies.
- Limits each category to a configurable logical-state budget and distributes action candidates fairly across
filters and toolbar controls.
- Fixes the customer-facing listing depth at one action beyond the category page. CLI can select depth 0 for
category-only warming; larger combinations are intentionally not exposed because they can exceed practical
full-page-cache capacity.
- Recursively canonicalizes nested filter keys and unordered OR values, so equivalent Discovery Filters URLs are
warmed once instead of consuming budget under multiple query-string orders.
Compatibility fixes
- Detects Hyva Discovery Filters through `data-ppl-di
Support
Back to topThe best place to start if you need help with a specific extension is to contact the developer. All Adobe Commerce developers have both a contact email and a support email listed.
Contact Vendor