One of the most important settings blocks for the WordPress cache system.
Enables or disables the whole WordPress cache system. Note that WordPress content optimization is controlled by the ‘Enable content processing’ option independently.
- Lazy revalidation
Allows updating the content in the background without being noticed by users and search engines, while maintaining the maximum speed of the pages. Very relevant to entered by Google regularly checking pages for speed in the Search Console.
- Temporary cache not optimized content after forced revalidation
Since when updating, users are shown the previous version of the page from the cache, this setting allows you to immediately display the current content, but for now temporarily without optimization. It is useful when you need to immediately display changes on the site, but optimization takes time. It happens when manual revalidation or revalidation after post changing occurs.
- Temporary cache not optimized content after auto-revalidation
Same as previous but after auto-revalidation occurs.
- Early pages processing (warming up)
When pages are revalidated or deleted, they will be re-optimized immediately, not just the first time they are accessed.
The posts cache will be updated automatically when they are changed in accordance with the specified mode. You can additionally specify both other pages of the site by URI, and expressions for special pages.
When the specified taxonomies are changed, the entire cache will be updated in accordance with the specified mode.
- Maximum number of parallel processing
The simultaneous number of pages to be optimized will be no more than the number specified here.
- Time before next processing
Sets the interval before the next optimization. It is necessary to adjust the load on the hosting.
- Time to live for auto-revalidation
Not earlier than the expiration of this time after the last change of the content, it will be forcibly updated. You can turn off this option by setting everywhere 0.
- Time to live for cleanup
Not earlier than the expiration of this time after the last change of content, it will be completely removed by using the ‘Cleanup’ function to decrease cache storage space. If there is no need to save space, it can be simply turned off by setting everywhere 0.
- Auto-cleanup interval
How often cleanup will be executed using ‘Time to live for cleanup’.
Here can be specified the encodings in which the server will serve the content. ‘Uncompressed’ is always on because this is required by the data transfer standard.
If there is enough hosting space, then the data can be stored in this compressed form, which will slightly speed up the delivery of content if the request came with the same compression.
If the request came with GZip, Deflate or Compress encoding, then the content will be served without re-encoding as quickly as possible. Also, compression saves space for cached data.
If there is enough hosting space, then the data can be stored in uncompressed form, which will slightly speed up the delivery of content if the request also came without compression.
It’s the settings for fragmentation technology. The content is divided into parts, which are stored independently and allows to select the parts that are identical in content. This contributes to significant savings in cache storage space on the hosting, since many pages have the same parts, such as header, footer, comment block, etc.
- Optimize storaging
Enables this mode.
Enables/disables a specific separator for easy customization, so as not to delete an element.
- Element(s) XPath selector
One or more elements can be specified through an XPath selector.
Split content before the element.
Split content after the element.
The division into parts can be checked with the ‘Enable’ debugging option enabled and loading the checked page with the
?seraph_accel_proc=1 parameter. In the page HTML code, we need to search for special separating elements
<!-- seraph-accel-cont-sep --> and check their location in accordance with the specified settings.
These settings allow to cache particular headers, e.g. cookies, by adding them as a regular expressions patterns. If the pattern matches the header will be added to the page’s cache.
Here is the pattern example for a header with cookie
wordpress_test_cookie which is already added by default: