In that case, @adlik, I think there are two parts to what you could
consider doing:If it were me, I would capture the "real" timings on the
initial page load, event if it meant potentially delaying the initial
Page View call to wait for the browser to make them available in
`performance.timing`For the "dynamic" page views (i.e. those subsequent
ones), I would work with the Devs to define at least two timing
events:"Navigation" - i.e. the point at which the user triggers an
action that prompts a ...