The current code uses the PageSpeed Insights API (PSI API) as a mechanism to get access to the Lighthouse audit data.
As we also need access to the PSI API data that is not included in the Lighthouse audit (for example, the field data that was retrieved via CrUX), we need to either add a separate tool to process PSI API as a result, or to rename the existing Lighthouse tool to denote that it encompasses the entire PSI API.
Feature Description
The current code uses the PageSpeed Insights API (PSI API) as a mechanism to get access to the Lighthouse audit data.
As we also need access to the PSI API data that is not included in the Lighthouse audit (for example, the field data that was retrieved via CrUX), we need to either add a separate tool to process PSI API as a result, or to rename the existing
Lighthouse
tool to denote that it encompasses the entire PSI API.