Wow, I had no idea the basics were already available in IE9/Chrome. It
seems like that's enough to start using this right now.
Has anyone heard of a cloud hosted vendor that will aggregate this
information via an Ajax call from a javascript include? I'm surprised
Google Analytics doesn't have this already...
-Chase
On Apr 18, 8:14 am, Pat Meenan <
patmee...@gmail.com> wrote:
> Actually, that's exactly what the Resource Timing part of the web timing
> spec is trying to tackle. It's probably still a ways off from being
> sorted out because it's a pretty nasty hairball of security and privacy
> concerns but the goal is to give javascript on the page access to
> per-resource timing information -
http://lists.w3.org/Archives/Public/public-web-perf/2010Nov/0001.html
>
> As far as the start time (and actually a lot more great data) is
> available from the web performance spec which is already implemented in
> Chrome and IE9 (with Firefox support coming later this year) :
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Ov...
>
> Lots of great work going on in the browsers to be able to get real field
> performance data.
>
> On 4/18/2011 7:27 AM, Guy Podjarny wrote:
>
>
>
>
>
>
>
> > This sounds like a great enhancement, but I think it won't be able to
> > capture real user data.
>
> > In order for it to capture real user data it would have to allow
> > JavaScript to access the HAR files and upload them, which has major
> > security and privacy implications.
>
> > So I think the end result would be a capability like yslow's
> > measurement, meaning you grab the browser's timings, but only when
> > it's your own browser.
>
> > One simpler bit of info browsers could make available is the time the
> > page request was issued. This would make JavaScript based timing
> > measurements more accurate, without compromising security.
>
> > Cheers,
> > Guypo
>
> > Guy Podjarny | CTO, Blaze |
613-800-0413 x202
>