search

addyosmani / timing.js

Navigation Timing API measurement helpers
1.5k stars 114 forks source link

Differing loadTime value to Chrome DevTools #12

Closed foobartel closed 9 years ago

foobartel commented 9 years ago

The values returned from timing.js sometimes differ to those displayed in Chrome DevTools and it's not only a rounding issue, but rather due to a different calculation of load time. It seems that Chrome uses loadEventEnd - fetchStart rather than loadEventEnd - navigationStart to calculate total load time.

screen shot 2015-06-03 at 5 35 33 pm screen shot 2015-06-03 at 4 23 42 pm screen shot 2015-06-03 at 4 26 21 pm

addyosmani commented 9 years ago

Fixed per your patch :)