The Opportunities section of the Lighthouse report lists resources that are being redirected:
How redirects slow down performance
Redirects introduce additional delays before the page can load.
When a browser requests a resource that has been redirected, the server usually returns an HTTP response like this:
HTTP/1.1 301 Moved Permanently
The browser must then make another HTTP request at the new location in order to retrieve the resource. This additional trip across the network can delay the loading of the resource by hundreds of milliseconds.
How to eliminate redirects
Eliminate the redirects by upading the links to these resources. Update the links to these resources. The links should point to the current locations of the resources. It's especially important to avoid redirects in resources required for your Critical Rendering Path.
If you're using redirects to divert mobile users to the mobile version of your page, consider re-designing your site to use Responsive Design.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.