Re: Understanding Navigation Timing Metrics

Could it be that the DOM Interactive is triggered when closing </html>
is parsed but that for some pages:
1. there are additional bytes in the HTTP response after the closing </html>
2. the time it takes to reach the last byte on the network is after
the time the closing </html> is parsed by the renderer?

I have not read the spec in detail so this may not actually be a
possibility but I wanted to put it out there.

I do also wonder how last response byte timing is handled for
responses that don't have a content-length or use chunked encoding and
for whom the connection is not immediately closed when the last byte
of HTML is received.

On Wed, Sep 5, 2012 at 9:30 AM, Reitbauer, Alois
<> wrote:
> Looking at some real world Web performance data, I found an interesting
> issue.
> According to the specification DOM Interactive is triggered when the whole
> document is parsed. ResponseEnd is triggered when the last byte of the
> response is received. Looking at our real world data I saw numerous cases
> where the DOM Interactive events happens before the Response End event. Any
> thoughts on this?
> // Alois

Received on Thursday, 6 September 2012 12:43:32 UTC