Blog Sections Open
How to Verify That Caching Is Actually Working in Evolution CMS
If pages still feel slow even when snippets are cached, start by confirming what is actually being served from cache and what is not.
It is easy to assume caching is enabled just because snippets are called in cached mode. In practice, slow pages often come from a different layer: dynamic output that bypasses cache, heavy database work in plugins, or page fragments that regenerate more often than expected.
What to check first
- compare first-load and repeat-load timings on the same page
- look at the page timing placeholders such as
[^s^],[^t^], and[^q^] - temporarily remove heavy snippets and compare the result
- verify that page output is not being forced uncached by a surrounding call pattern
A useful rule
If the second request is not noticeably faster than the first, caching is either not working the way you think or the main bottleneck is outside the normal page cache path. That could mean plugins, file operations, external API calls, or expensive TV processing.
On older sites, the right question is not only is caching enabled? but also which layer is still dynamic?
Fixing txNewsletters Encoding and Mail Delivery Problems on cp1251 Sites
What to check when txNewsletters works structurally but breaks on character encoding or refuses to deliver mail reliably.
Speeding Up AjaxSearch on Large YAMS Sites with TV-Based Content
How to reduce AjaxSearch response time when a multilingual Evolution CMS site stores most searchable text in TVs.