simplemage / magento2-cachewarmup

simplemage/magento2-cachewarmup

SimpleMage Cache Warmup

magento2-module Compatibility: 2.4.8-2.4.9 Code Quality: Fail Tests: N/A Security: Pass GPL-3.0

Are you the maintainer of simplemage?

Packagento pulls simplemage's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

SimpleMage CacheWarmup module for Magento 2 (Adobe Commerce)

Overview

The SimpleMage CacheWarmup module is designed to enhance the performance of your Magento store by automating the process of warming up the cache for your website's pages. This module is compatible with both Magento Full Page Cache and Varnish, ensuring that your store's pages are preloaded into the cache, reducing load times for your visitors.

Using this module you do not need advanced rules or settings in Magento, you can add specific URLs from a file added in the admin panel that are important for your business - the most visited subpages or new products, e.g. 1000-2000 most frequently displayed addresses from Google Analytics or another analytics tool with visit statistics.

It is particularly useful for setups with multiple Varnish servers, as it can handle complex infrastructures seamlessly - without coding.

Key Features

  • Compatibility: Works with both Magento Full Page Cache and Varnish.
  • URLs from file: Supports cache warmup based on a list of URLs imported from a file (e.g., from Google Analytics) - can warmup custom pages from every module provider e.g. blog module or category pages with filters applied.
  • Automated custom file read: If you want to prepare custom automatic file generation with list of URLs you can create your own script and upload file to static path.
  • Multi-Server Support: Handles infrastructures with multiple Varnish servers or single Varnish instance.
  • Cronjob Integration: Automates cache warmup at scheduled intervals via cronjob.
  • SSL Verification: Includes an option to disable SSL verification for local Varnish testing.

Limitations

  • Customer group: In this version the module does not support customer groups - it saves pages in the cache only for not logged in clients
  • Clean cache: If the server performs a full page cache cleanup, the pages will be saved in the cache only after the cronjob is executed again

Installation

  1. Use composer to install

    composer require simplemage/magento2-cachewarmup
    

or download the module files and place them in the app/code/SimpleMage/CacheWarmup directory within your Magento installation

  1. Run the following commands to enable the module:
    php bin/magento setup:upgrade
    php bin/magento setup:di:compile
    php bin/magento cache:flush
    
  2. Configure the module via the Magento admin panel under Stores > Configuration > SimpleMage > Cache Warmup
  • General Settings
    • Varnish Server IPs - if you have multiple Varnish servers put here public IPs of this servers, if you have Varnish installed on the same server (or not have Varnish installed) leave it blank
    • File source - select data source (default option is File upload) - if you want to create custom script to prepare automatically URLs to warmup please select option Static file path and save your file in Magento system path var/import/warmup_urls.txt
    • File with URLs to warmup - upload file with URLs you want to warump - supports simple TXT file with URLs separated by new line - you can find example file in repository example-file.txt
    • Skip verify host SSL certificate - use only on localhost for testing purposes
  • Cronjob Settings
    • Enable warmup cronjob - enable or disable warmup cronjob
    • Cron schedule - cron expression configuration
    • Enable debug mode - enable debugging of every query for every URL from the file

Troubleshooting

  1. Cache not warming up properly

If you notice that certain pages are not being cached, follow these steps:

  • Enable Debug Mode: Turn on debug mode in the module settings.
  • Check Logs: Review the logs to see the status of the requests made by the module.
    • If the status is not 200, there may be a connection issue between your Magento application server and the Varnish server(s).
    • Ensure that your Magento server can send requests to the public IP address of your Varnish server(s).
  1. Local Varnish Testing

If you are testing Varnish locally and encountering issues:

  • Problem with SSL verification: Use the option in the module settings to disable SSL verification Stores > Configuration > SimpleMage > Cache Warmup > General Settings > Skip verify host SSL certificate. This is useful for local environments where SSL certificates may not be properly configured.

Support

For any issues or questions regarding the module, please open an issue on our GitHub repository.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.0.1 stable Fail Magento 2.4.8-2.4.9 Details 2025-03-27 08:06:21
1.0.0 stable Not tested Not yet tested Details 2025-03-27 07:56:17

Requires 2

Package Constraint
guzzlehttp/guzzle 7.*
magento/framework *

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Fail di error Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Pass 0
PHPMD Pass 0
Cpd Pass 0
Composer validate Info 3 valid; 3 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 4 1
2.4.8 1 1
2.4.9 1 1

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
GPL-3.0

More from simplemage

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.