Server-timing entries are included on resource- and navigation-timing entries as
For example, when:
To save bytes, we will omit the zeroes, and irrelevant separators. So:
And last, if there is only one
return three entries:
As it turns out, all three server timing entries are on the navigation timing entry (base page), so step into the trie like this:
In there you will find your three server timing entries.
split at the comma:
One thing I'm not sure how to handle is breaking compatibility with the previous return values for things like
Should we add an optional parameter to
Or should we make a semver change to 1.x and call it a breaking change?