W3C home > Mailing lists > Public > public-web-perf@w3.org > August 2016

Re: NavigationTiming event for initial display

From: Stefan Seifert <nine@detonation.org>
Date: Wed, 10 Aug 2016 20:10:28 +0200
To: Shubhie Panicker <panicker@google.com>
Cc: Ben Maurer <ben.maurer@gmail.com>, Bryan McQuade <bmcquade@google.com>, public-web-perf <public-web-perf@w3.org>, Paul Irish <paulirish@google.com>
Message-ID: <1540212.gFhDhGG5UO@sphinx>
On Mittwoch, 10. August 2016 10:52:56 CEST Shubhie Panicker wrote:

> The timing info is attaching to the window and not to individual DOM nodes.
> As such there is no performance concern for exposing the suggested first
> paint metrics.

That's what's implemented or at least considered now. But attaching the 
information to the window brings the challenge of picking the "right" moment 
to capture as there can be only one number for the "First Meaningful Paint" 
metric.

What I'm suggesting instead is to attach timing information to the individual 
DOM nodes.  As a developer I know that I'm really interested in the time until 
nav#main_nav is first painted and that we may completely ignore #splashscreen's 
appearance.

And like Ben Maurer said, a single number may not cut it anyway, as there may 
be multiple parts of the site loaded incrementally and we would like to have 
timing information for them all.

Kind regards,
Stefan
Received on Wednesday, 10 August 2016 18:10:55 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 18 September 2016 16:33:38 UTC