This article provides solutions for increased website load times or outages due to full page cache (for example Fastly) having been disabled for any block on any page(s) that need to be cached.
Affected products and versions
- Adobe Commerce on cloud infrastructure 2.x.x
- Adobe Commerce on-premises 2.x.x
The site experiences slow performance because there are cache blocks on pages which need to be cacheable but have been set to
There are pages that need to be cached by Adobe Commerce. These pages have the biggest throughput. Each request of these types of pages not from cache, makes Adobe Commerce perform slower.
These pages are:
- Catalog Category (PLP)
- Catalog Product Page (DPD)
- Static Content Pages (Home Page, Contact Us, etc.)
Cacheable and uncacheable are terms used to indicate whether or not a page should be cached. By default, all pages are cacheable. However, if any block in a layout is designated as uncacheable, the entire page is uncacheable.
The screen shot below shows a block with a setting
cacheable="false” ** ** which creates an uncacheable page.
Examples of uncacheable pages include compare products, cart, and checkout pages.
The following list of pages are not cached (Fastly, Block, and Layout caches are avoided.). This occurs because of the “cacheable” configuration in layout.
Check if the files specified above have the setting
cacheable="false” . If they have, check if this setting is needed or required.
- If needed, consider moving non-cacheable blocks to private content mechanism instead.
- If not needed, remove the attribute
cacheable="false”and flush the layout cache.
For Adobe Commerce on cloud infrastructure 2.4.1 and later, you can use the Site-Wide Analysis Tool to automatically check if your Full Page Cache is not configured correctly.
Adobe Commerce cache overview in our developer documentation.