No minification of clay files impacting page load response times
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
legacy-article
learn-legacy-article-disclaimer-text
Issue
- We see more number of Clay UI related network calls in the browser network tab in clean instance of Liferay and they are not getting cached also. It has JS and CSS files which are not minified into fewer combo files.
Resolution
- This is the expected behavior because Liferay is now using ESM, the browser's native module loading architecture to load JS files.
- Because of http/2 there is no longer a bottleneck for the number of simultaneous requests.
-
The clay files are in fact being minified and they are being requested in parallel rather than all bundled into one
/combo request. These are both expected and shouldn’t impact performance at all because of how http/2 allows for simultaneous requests.
did-this-article-resolve-your-issue