You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 6, 2020. It is now read-only.
@addyosmani and @housseindjirdeh – We should consider adding PSI to the required metrics with a link explaining what it is.
Frequently implementations can trade-off faster "boot" times for degraded PSI and vice-versa. Since the goal is to understand the implementations (while we work on standardization of features), this metric could help visitors gain more insight into the motivations of each implementation.
The text was updated successfully, but these errors were encountered:
At some point (no rush) we might find value in exploring an automated pipeline for periodically re-running our WebPageTest reports for each app and extracting the relevant scores we want to track from the WPT API. I believe what's included from the Lighthouse report can also be extracted from there, but we can chat more about whether this is something we want to do at a later point 😄
@addyosmani and @housseindjirdeh – We should consider adding PSI to the required metrics with a link explaining what it is.
Frequently implementations can trade-off faster "boot" times for degraded PSI and vice-versa. Since the goal is to understand the implementations (while we work on standardization of features), this metric could help visitors gain more insight into the motivations of each implementation.
The text was updated successfully, but these errors were encountered: