search

YahooArchive / boomerang

End user oriented web performance testing and beaconing
http://lognormal.github.com/boomerang/doc/
Other
1.18k stars 447 forks source link

W3C Navigation Timing plugin #16

Closed bbrewer closed 13 years ago

bbrewer commented 13 years ago

I took a crack at a plugin that pulls all the data out of the Navigation Timing API (window.performance.navigation / window.performance.timing) and adds them to the beacon.

This adds a number of metrics like DNS/connect/ssl/FB times, load and unload event times, DOM loading/interactive/complete, and others to the mix.

Let me know if there's anything I can do to make it better..

bluesmoon commented 13 years ago

Also, add some documentation in the doc subfolder.

bbrewer commented 13 years ago

Thanks for the feedback. I'll revise and update the branch.

bbrewer commented 13 years ago

re: Google toolbar. Due to the breadth and depth of measurements required by the spec, I don't think a proper Navigation Timing implementation is something we're likely to find in Google Toolbar. I tried to look myself (Google toolbar + IE8/WinXP in parallels) but I couldn't find window.gtbExternal in a javascript console. Not sure where to go from here.

bbrewer commented 13 years ago

Oops! I only meant to comment, not comment and close. Maybe those buttons shouldn't be so close together :)

bluesmoon commented 13 years ago

Got it. It also looks like mozilla will just use window.performance instead of mozPerformance, IE has already moved to window.performance. I don't know about chrome & safari yet though.

bbrewer commented 13 years ago

Yeah, vendor prefixes are going away and everyone is standardizing on window.performance going forward. Chrome is already there. But I think the legacy prefixes still have value in the event the plugin encounters one of those old versions.