Add support for tracking page load metrics of prerendered pages |
||||
Issue descriptionpage_load_metrics doesn't currently support tracking metrics for prerendered pages. We should enable tracking of them if/when they get foregrounded. It's not clear what start time to use for prerenders however. From a user perception standpoint, the start time is the time they initiated the navigation, whereas navigation_start tracks the time that the navigation was initiated in the background as a prerender.
,
Oct 7 2016
Loading triager here. Marking as available since this is more of a request than a bug and not high priority.
,
Mar 20 2017
,
Apr 3 2017
I think the right long term plan here is to measure all navigation timing starting from the user input which triggered the navigation. Once we have general page load metrics from user input, it should be possible for us to seamlessly add coverage here.
,
Apr 3 2017
That makes sense to me. It'd be ideal to change the public definition of navigation_start to use the user input event timestamp as well. Otherwise what we measure internally will be inconsistent w/ what web devs measure.
,
Jul 26 2017
I believe this was fixed with Omnibox.SuggestionUsed*Prerender (and to some extent the various *PrefetchTTFCP*) which both take the foregrounding time as the start time. |
||||
►
Sign in to add a comment |
||||
Comment 1 by bmcquade@chromium.org
, Sep 19 2016