Optimal Page Performance
Page Caching is skipped when a page is viewed in either editing or previewing mode of the Page Designer tool, so any change can be immediately visible to the user. However in the plain storefront, the customer page cache instrumentations apply as coded. Slow rendering typically results from either the page not yet in the page cache when viewed outside of Page Designer, or a low-performing page implementation.
For slow performing pages, we recommend you check to see if the implementation has to be
revised:
- in the storefront, use the STFK.
- enable the Cache Info tool.
- look for the cache symbol for pipeline βInternal - Page Designerβ, and check its caching status.
For uncached occurrences that must be revisited for an implementation change, we recommend
you:
- use page caching unless itβs ultimately necessary to not cache the given page. See Page Caching for more information.
- refactor the business logic of the page avoiding costly operations, or mass amounts of operations, during one request.