How to reduce huge content structure on page leading to Node Traverse reach Threshold limit?

Hi @veena1 

Ideally would be to have simply the page structure, of course without affecting the UX/UI. Not sure how hard would such a rework be for your team.

If that is out of question, you could try indeed to create XFs. I imagine the page itself would become lighter, even if the total amount of component and nodes involved will still be the same I assume (more or less). But I believe the traversal will happen for each separately (I am not an expert on this specific point, maybe someone can give us some deep insight on how AEM works regarding traversing resources and referenced resources).

You can also increase the traversal limit, but that is a bit dangerous: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/the-query-read-or-traversed-more-than-100000-nodes-to-avoid/m-p/357042

Hi @veena1 ,

Experience Fragments (XF) and Content Fragments (CF) are the best solutions to reduce node traversal. Additionally, reducing nesting, using caching, and leveraging CSS-based styling will significantly improve performance.

Some recommended actions:

• Convert reusable static content into experience fragments.
• Reduce nested structures inside components.
• Use content fragments instead of multiple text components.
• Store template-level structures in Editable Templates.
• Enable Dispatcher Caching for static pages.

Regards,

@veena1 

For the current page to work, you might need to update following config:

In parallel, you should try combining smaller components to create one composite component. That is reduce the number of script calls being made to resolve & render a component.

This would make it easy to author & debug as well.

Once new components are ready, gradually update old pages to use new composite component. Preferably target the page that is served / updated more frequently.