Re: NavigationTiming event for initial display from Stefan Seifert on 2016-08-09 (public-web-perf@w3.org from August 2016)

From: Stefan Seifert <nine@detonation.org>
Date: Tue, 09 Aug 2016 21:32:57 +0200
To: Ben Maurer <ben.maurer@gmail.com>
Cc: Shubhie Panicker <panicker@google.com>, Bryan McQuade <bmcquade@google.com>, public-web-perf <public-web-perf@w3.org>, Paul Irish <paulirish@google.com>
Message-ID: <3361187.TIuJCSytMU@sphinx>

Hi,

On Donnerstag, 23. Juni 2016 08:41:33 CEST Ben Maurer wrote:

> Just wanted to share some thoughts here based on our measurement experience
> at Facebook. While the FirstPaint and FirstContentfulPaint events are
> interesting I don't think these reflect the actual loading times of
> non-trivial applications. Many sites load their content incrementally and
> these statistics are unlikely to capture just the right subset of content.

I guess attaching timing information to DOM nodes like time from start of page 
load until this node was first (partially) painted would by itself create 
performance issues? If not, that could leave the choice of the "right" subset 
of the content to the developer.

Stefan

Received on Tuesday, 9 August 2016 19:33:30 UTC