Skip to main content

How to speed up warming

Pages Warming works as follows: The cron job initiates the warming task, where the extension retrieves a list of URLs from the Pages and checks each one. Any URLs that are excluded through the exclusion configuration are filtered out and will be removed. Next, the extension sends a curl request to the server hosting the cached page. Once the server responds, the extension marks the page as Cached.

The speed of this caching process is influenced by the Magento Cache System (such as Built-in, Varnish, Redis, etc.), which in turn depends on various factors like server performance, load, the time taken by the server to generate a page. These processes are handled on the server-side, and while the extension can’t directly optimize page caching or the page code itself, it can have a minor effect on speeding up the overall process.

Steps to improving warming performance​

Use the tips below to try and speed up the page warming process.

  1. Create several Warm rules with different priorities. For example, divide the pages of your site by type (Products, Categories, CMS, Blog pages, etc.).
  2. Change the Warming strategy from Warm Rules (default) to Warm Rules + URL variations.
  3. Change the Warming level to Custom - expert mode and set your own Concurrent requests value. Not all servers support multiple threads, so ensure your server supports the specified value and that changing the settings does not result in errors, and the pages continue to cache successfully.
  4. Optimize your URL list by using the exclusion configuration to remove unnecessary pages from the warming process (for example, pages with selected filters).
  5. Check the cron frequency on your site. If cron runs infrequently, increase the frequency, for example, to once per minute.

After adjusting the settings, the Average warming speed should increase. If you don't see an effect, it's likely due to the page caching process on the server. Contact your system administrator or hosting provider to ensure that the server is optimally configured.