Timing values reported can come from two clocks: Date.now via the spf.now function, and performance.now via the resourceTiming API. Currently, SPF mixes those clocks, which can cause skew. (This is visible in Chrome 48, for example.) To fix, always prefer the performance.now clock if available.
Timing values reported can come from two clocks:
Date.now
via thespf.now
function, andperformance.now
via theresourceTiming
API. Currently, SPF mixes those clocks, which can cause skew. (This is visible in Chrome 48, for example.) To fix, always prefer theperformance.now
clock if available.