As a page creator, I want to understand which page components take more time to render in the backend, so that I can improve my page performance.

Context

When a page (content page, widget page, etc) is rendered, each of its components that rely on FREEMARKER is rendered on the backend and sent to the front end as HTML to be displayed.

This render time can imply freemarker performance issues if the component is not designed and implemented correctly.

Scope

The proposed solution to make it easy to debug these scenarios is to add a new section to PAGE AUDIT in which users can see a LIST of page components (fragments, widgets), along with the backend render time that is needed to render each of them in the backend and send it to the front end for display. in this way, users will notice which fragments struggle for rendering and can review their implementation if needed.

FULL DESCRIPTION OF SCOPE: https://liferay.atlassian.net/wiki/spaces/ENGECHO/pages/2312536121/Allow+customers+to+prevent+performance+issues+in+content+pages#Provide-Page-Creators-with-indications-on-components-backend-render-timings

 Additional Notes

Use Feature Flag

• Title: Render Times in Page Audit

• Description: List the page components render times in server side to identify low performing fragments, widgets or templates