3 ms·
It's worth noting that this won't help you with timing the first page loaded, just the ones after that. Impressive nonetheless.
by spicyj 16y ago
It's worth noting that this won't help you with timing the first page loaded, just the ones after that. Impressive nonetheless.
- bluesmoon 16y agoI'm hoping that browsers will soon support WebTiming: http://dev.w3.org/2006/webapi/WebTiming/ http://dev.w3.org/2006/webapi/WebTiming/ We'll add support into boomerang for those APIs However, until then, you can still measure the time from first-byte to onload by starting a timer at the top of your page. It's crude, but it works.
- sh1mmer 16y agoThe IE9 preview-release they talked about at Velocity does and it sounds like other browser manufacturers are in given the discussion on the browser panel, but as usual that means it's 2 years before it's useful.
- bluesmoon 16y agoOk, I've added the WebTiming API checks to boomerang.
- stretchwithme 16y agoyou just scored high on the DeveloperTiming API.
- sh1mmer 16y agoThat's a really good point, it's actually a constraint of the architecture of the web. This framework is based on our own research of the best way to reliably measure page performance is across page loads. Boomerang itself is actually a generic beaconing framework so you can use it to beacon anything but it also has a lot of bootstrap code as well for performance testing. Phil has done some great documentation on how to do beaconing right to go with the framework and you should expect more of that.