Performance Revolution: setup and help

Upload the ZIP in Modules > Module Manager, install it and click Configure. The back-office menu is Performance, with Dashboard, Cache, Assets, Queries, Backup, Settings and System Check.

Before enabling additional layers, record how your homepage, category, product, cart, account and checkout behave. Test in a customer browser as well as an employee browser. Select the intended shop and back up configuration before changing core caching or CDN rules.

Start in Settings > Cache Backend. The PHP process needs write access to the PrestaShop cache and generated-asset directories. The PrestaShop Redis object-cache installation also needs access to the affected core cache class and configuration files. Cloudflare actions require a token authorized for the selected zone and the requested operations.

Save and check the selected adapter on Dashboard. If Redis cannot connect, verify hostname, port, authentication, database and PHP Redis support. Do not assume choosing the module backend also enables the core object cache.

Open Cache > Overview for Global Cache, Front Office, Back Office and Webservice scope switches. Their module defaults are on. The global switch controls module cache usage, and scope switches restrict the corresponding request contexts.

Use Cache > Layers for layer controls, Browser to inspect entries, Pages to inspect page-cache data and Presets to review available presets. Read a preset before applying it because it changes several settings together.

Auto-detection tries Redis, then APCu, then File. If the adapter you selected is unavailable, the module runs auto-detection again, so after saving check the adapter actually in use on Dashboard. File storage needs a writable cache directory; check that cache files are being written.

Open Settings > Fragment Caching.

A developer can cache a category fragment while including category identity:

{mpr_cache id="category_products" ttl=3600 tags=["product","category"] vary=["category" => $category.id]}
  {foreach from=$products item=product}
    {include file='catalog/_partials/miniatures/product.tpl' product=$product}
  {/foreach}
{/mpr_cache}

The cache key includes language, shop, currency and default customer group unless context inclusion is disabled. Add every other value that affects the fragment to vary. Do not place customer-specific markup in a shared fragment without appropriate variation or dynamic replacement.

Use dynamic placeholders for supported current-request values:

<span class="cart-count">{mpr_dynamic name="cart_count"}</span>
<span class="cart-total">{mpr_dynamic name="cart_total"}</span>
<span class="customer-name">{mpr_dynamic name="customer_name" default=""}</span>
<span class="csrf-token">{mpr_dynamic name="csrf_token"}</span>

Supported names also cover customer, language, currency and shop values. A custom provider can use actionMPRDynamicContent:

public function hookActionMPRDynamicContent($params)
{
    if (($params['name'] ?? '') === 'loyalty_points') {
        return (string) $this->getCurrentCustomerPoints();
    }
    return $params['default'] ?? '';
}

Open Settings > Query Cache.

Use Queries to inspect collected queries. Enable profiling while diagnosing a problem, then review its overhead before keeping it active.

Open Settings > Asset Optimization. Enable and test one change at a time on your theme.

Enabling generated CSS does not launch a browser during a storefront request. Build it with the separate workers. Generated Initial CSS Status reports readiness. The critical-CSS worker requires Node 22.12 or later and its configured browser environment. Follow the worker's bundled instructions for generation and deployment.

These CLI commands inspect or seed its work; they do not themselves complete browser generation:

php modules/mprperformancerevolution/cli/critical-css.php --targets
php modules/mprperformancerevolution/cli/critical-css.php --seed
php modules/mprperformancerevolution/cli/critical-css.php --status
php modules/mprperformancerevolution/cli/page-type-css.php --status

Rebuild the offline CSS data after relevant stylesheet, template, script or content changes. When the generated data is missing or invalid, the module falls back to the complete stylesheets.

Open Settings > Instant Navigation.

Cart, checkout, account, sign-in, query-string links, files, nofollow links and module tools are excluded by the built-in policy. The server also validates speculative requests.

Open Settings > Images.

Runtime AVIF encoding can use GD imageavif or Imagick with AVIF support. GD AVIF generally needs PHP 8.1 or later. Batch generation can also use the bundled Python backend when Python, Pillow, pillow_avif and process execution are available. WebP uses supported GD functionality.

Additional internal defaults apply to listing images: the image-type filter defaults off, and the type list is default_sm,default_md,default_lg,home_default,product_main,product_main_2x. These are not separate visible fields in the standard Images form. Likewise, the internal RUM sample rate is 0.1.

For a controlled batch, run from the installed shop:

php modules/mprperformancerevolution/scripts/generate-images-cli.php --quality=50 --webp-quality=80 --webp --limit=100

Use repeatable --path=PATH to restrict work within the shop root. --force regenerates existing variants. Review converted, skipped and error counts before a larger batch.

Open Settings > Origin Page Cache.

This is a real origin full-page cache using the module cache manager. It is separate from CDN HTML caching and Smarty fragments. Cart, account, checkout, admin, AJAX, unsafe session-cookie and unknown-query requests bypass according to the runtime policy.

Enable it only after checking a clean anonymous page and the required bypass cases. Request the same anonymous URL twice and inspect X-MPR-PageCache. Then test login, cart creation, currency/language changes and private pages in separate browser sessions.

Open Settings > CDN Page Cache. Start with the default Strict cookie policy.

After saving, use the CDN Actions to apply and verify the rule setup and inspect its result. A cookie-policy change reapplies rules and purges the zone. Do not treat a failed or pending rule transition as a completed setup.

Test anonymous caching and private bypass separately. Logins, carts, checkout, account pages, AJAX, protected module routes, personalization and unsafe request states must not share anonymous HTML. Preserve the generated-asset retention period when long-lived HTML still refers to old assets.

The module sends cache headers and runs supported Cloudflare operations. How the edge actually caches still depends on your zone rules, the API token's permissions and whether a response can be cached. Some Cloudflare purge methods are not available on every plan.

Open Settings > Cache Warming.

Copy the actual generated token into your server scheduler. A typical runner command is:

* * * * * php /var/www/html/modules/mprperformancerevolution/cron.php --token=YOUR_TOKEN --max-tasks=20 --max-seconds=55 --context=cron

Adjust PHP and shop paths. The runner also handles declared cleanup, pending invalidations/purges, image jobs and CSS maintenance according to task state. Enabling a feature and scheduling its task are separate checks.

A manual post-deploy pass can use:

php modules/mprperformancerevolution/cli/warm-cache.php --full --both --url-set=all --concurrency=1 --resolve-ip=127.0.0.1 --max-seconds=120

Use --edge for edge-only, --cron for cron mode and --help for supported arguments. Read the summary for disabled, failed or blocked external-write states. A paused or budget-limited pass can be expected with conservative defaults.

Open Settings > Monitoring. Enable Metrics Collection defaults on, Metrics Retention to 30 days and Real User Metrics to on. The internal RUM sample rate is 10 percent. Dashboard metrics include adapter state, hits, misses, hit ratio, memory, slow queries and available TTFB, FCP, LCP, CLS and INP measurements.

Open Settings > Dev Mode to temporarily suspend cache-related settings. Dev Mode starts inactive, saves the previous configuration and restores it on deactivation or expiry. Employee Debug Mode starts off and enables PrestaShop development output only for recognized employees with the module's validated debug cookie.

Under Settings > Debug, Debug Overlay, Enable Debug Panel and Profiler Panel default off. Allowed IP Addresses and Allowed Employee IDs start empty. Profiler: Employees Only defaults on. Keep diagnostics restricted while testing and turn them off when finished.

Optional profiler files exist at optional-overrides/classes/Hook.php and optional-overrides/classes/db/Db.php. Use the guarded profiler override installation workflow so existing overrides are checked. Clear PrestaShop class/cache state as instructed by that workflow. Do not overwrite unrelated overrides with an unconditional copy. Remove optional profiler overrides through the same workflow when no longer needed.

After each configuration change, check the homepage, listing, product, cart and checkout, then confirm cache headers and bypass reasons in separate customer sessions. Catalog, stock, price and content hooks invalidate supported cache tags, but theme, integration and CDN rule changes can still need explicit cache clearing.

Stored monitoring data

Review the collected data before sharing diagnostic exports:

• Slow queries can contain the complete SQL statement, execution time, controller, stack trace, occurrence count and first/last-seen timestamps. SQL or trace text may contain customer, cart or order identifiers, so restrict access to these diagnostics.
• Real-user monitoring (RUM) stores the page URL, device class, connection type, available browser timings, DOM timings, resource summary, shop and timestamp. It can also record the navigation delivery type. These are diagnostics, but URLs and resource details still need review before sharing.
• The schema also creates metric value/context and hour/day/week/month summary tables, but the current version never writes to them, so they stay empty.

The RUM aggregation path summarizes raw data older than 24 hours into hourly URL/device/shop sample counts and averages, then deletes the aggregated raw rows. This work is attempted opportunistically on a small fraction of beacon requests. Although the aggregate schema contains p75_lcp, the current executed query and insert do not calculate or populate that value. Do not describe those averages as a 75th percentile.

If the adapter differs from your selection, inspect backend availability and Redis endpoint resolution. If a page bypasses, read its diagnostic reason before raising limits or changing cookie policy. For stale HTML, check origin and edge layers separately and confirm invalidation completed.

If bundling, deferral or CSS changes break a component, disable the affected setting, clear its generated files or cache and test again. For generated CSS, check the status and the worker log. For image errors, check encoder support and write permissions. For pending warming, check the runner, the feature switch, host load and budgets.

Before uninstalling, remove optional profiler overrides you installed and review active CDN rules. Disable or remove module-owned edge rules through the CDN workflow so the zone does not keep caching private routes without the intended origin protection. Back up configuration and generated data you need.

Uninstall removes scheduled tasks, employee debug bootstrap, the installed Redis cache class, module menu entries and module database tables. Review PrestaShop's core cache configuration and any external CDN configuration afterwards; do not assume all remote setup is undone by Module Manager.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.