Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Multiple Performance Issues Identified via Lighthouse, Google Insights and Web Audit Tools

Written By

David Simon

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

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • How do I increase site performance with Lighthouse, Google Insights and Web Audit Tools?

Environment

  • Quarterly Releases
  • DXP 7.0
  • DXP 7.1
  • DXP 7.2
  • DXP 7.3
  • DXP 7.4

Resolution

Firstly, please note that Liferay does not have any official commitments with third-party analytics tools such as Google PageSpeed or Lighthouse.
These tools and their evaluation criteria can change frequently, which makes maintaining compatibility quite challenging.
However, we do have a couple of articles I could share with you:

Secondly, these kinds of results seem to fall under performance-related concerns, which can often be complex and require in-depth investigation to identify the root cause.

Compression should be handled by the web server.

From Liferay perspective, we recommend to use minified themes and minify CSS/JS via build.gradle or Liferay Workspace.
Enable MinifierFilter in portal-ext.properties (usually already on by default):

minifier.enabled=true

For best results, use CDNs for serving large libraries or static assets if possible.

Given all this, the best course of action would be to reach out to the Global Services team, who can provide the necessary support and expertise for this type of issue.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?