W3C home > Mailing lists > Public > public-web-perf@w3.org > September 2010

Re: [NavigationTiming] Updates

From: Nik Matsievsky <speed@webo.name>
Date: Thu, 16 Sep 2010 13:11:46 +0400
Message-ID: <4c91df50.487e0e0a.02ec.ffffb3de@mx.google.com>
To: "Jason Sobel" <jsobel@facebook.com>,"Anderson Quach" <aquach@microsoft.com>,"public-web-perf@w3.org" <public-web-perf@w3.org>
As for me, this info is very helpful in understanding complex web pages bottlenecks. For example to decide do we need more ads or widgets for current web page, or there are enough external objects. Of course this info can be retrieved from general list of resources, but looping in JS is expensive, etc,etc. So I'm voting to add these values to spec.

Thank you,
Nik Matsievsky

----- Reply message -----
От: "Jason Sobel" <jsobel@facebook.com>
Дата: чт, сен 16, 2010 05:37
Тема: [NavigationTiming] Updates
Кому: "Anderson Quach" <aquach@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>

Personally I feel like this data isn't very useful. I'd rather revisit after Resource Timing develops further. Though if others think this is high value it doesn't seem particularly expensive or unreasonable.

From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Anderson Quach
Sent: Wednesday, September 15, 2010 6:00 PM
To: public-web-perf@w3.org
Subject: RE: [NavigationTiming] Updates

The addition of requestCount and uniqueDomains is intended to describe at the top-level if the root document was request intensive and from multiple domains.  This type of information can complement Resource Timing as those details are soon to be flushed out.

Our recommendation is to bake this into the NavigationInfo interface while we are working on the draft for Resource Timing.

An alternative option is that we can re-visit these attributes while we are flushing out the design and details for the Resource Timing interface.


Anderson Quach
IE Program Manager

From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Anderson Quach
Sent: Monday, August 30, 2010 5:52 PM
To: Zhiheng Wang; public-web-perf@w3.org
Subject: RE: [NavigationTiming] Updates

Thanks for the updates to the Navigation Timing working draft [1].

There are a couple of attributes that would add value to describing the navigation. We would like to get your feedback on the requestCount and uniqueDomains that was introduced in IE9's PPB3 [2].

Specifically, a count of the number of requests made by the root document and from the number of unique domains. These attributes can be provided under the window.performance.navigation object.

window.msPerformance.navigation.requestCount  -- the number of requests as specified by the root document.

window.msPerformance.navigation.uniqueDomains - the number of unique domain name requests made by the root document.

Best Regards,

[1] http://dev.w3.org/2006/webapi/WebTiming/
[2] http://ie.microsoft.com/testdrive/Performance/msPerformance/Default.html

From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Zhiheng Wang
Sent: Friday, August 27, 2010 3:52 PM
To: public-web-perf
Subject: [NavigationTiming] Updates

    Based on the last conversation, the NavigationTiming has just been updated with the following changes:

   * DOM-related timing, i.e., domLoading, domInteractive, domContentLoad and domComplete, are added.
   * navigationStart now happens immediate after the user agent prompts for unloading the document.

Received on Thursday, 16 September 2010 09:12:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:29 UTC