Update pagespeedonline_v5 percentile #2242
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The 75th percentile is chosen for all metrics in pagespeed v5 https://developers.google.com/speed/docs/insights/v5/about#why-is-the-75th-percentile-chosen-for-all-metrics
|
Hi @iancamleite, Thanks for opening a PR. The files in docs/dyn are automatically generated using the public discovery documents. For example, for Regrettably this issue must be fixed at the source. Please follow this link to send feedback directly to the API team: https://developers.google.com/speed/docs/insights/v5/about#feedback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current documentation says the pagespeed v5 loading experience percentile is pc90, but the 75th percentile is chosen for all metrics in pagespeed v5.
This commit fixes the documentation on originLoadingExperience and loadingExperience.
Fixes #2241 馃