The web client does not currently record PerformanceResource entries after the load event fires. This means that slow, asynchronous resources, that contribute to poor web vitals like LCP or CLS, will not be recorded.
This change modifies the PerformanceResource plugin to continue listening to PerformanceResource entries after the load event.
To accomplish this, we modify our resource prioritization in the following ways:
We always record entries for document, scripts, stylesheets and fonts (was previously capped).
We record entries for everything else (including images) up to the configured limit.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
The web client does not currently record PerformanceResource entries after the load event fires. This means that slow, asynchronous resources, that contribute to poor web vitals like LCP or CLS, will not be recorded.
This change modifies the PerformanceResource plugin to continue listening to PerformanceResource entries after the load event.
To accomplish this, we modify our resource prioritization in the following ways:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.