WebPagetest Forums
Document Complete Metric - Printable Version

+- WebPagetest Forums (https://www.webpagetest.org/forums)
+-- Forum: WebPagetest (/forumdisplay.php?fid=7)
+--- Forum: General Discussion (/forumdisplay.php?fid=25)
+--- Thread: Document Complete Metric (/showthread.php?tid=13266)



Document Complete Metric - satishtamilan - 10-01-2014 03:15 AM

As per the definition of Document Complete

Document complete is point where the browser onLoad event fires and is generally when all of the static page content has loaded.

As per the below process flow is it till the load event end?

https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html#process

Can we define the document complete as the below?

This is an approximation for when the page becomes fully interactive for the user. This corresponds to when the browser finishes processing the onload event.This is the loadEventEnd attribute of the Navigation Timing specification.


RE: Document Complete Metric - pmeenan - 10-01-2014 10:36 PM

(10-01-2014 03:15 AM)satishtamilan Wrote:  As per the definition of Document Complete

Document complete is point where the browser onLoad event fires and is generally when all of the static page content has loaded.

As per the below process flow is it till the load event end?

https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html#process

The equivalent Navigation Timing event is loadEventStart. That said, in the case of something like a javascript redirect (changing window.location), WebPagetest's time will include both navigations while Navigation Timing will only include time from the second page.

Quote:Can we define the document complete as the below?

This is an approximation for when the page becomes fully interactive for the user. This corresponds to when the browser finishes processing the onload event.This is the loadEventEnd attribute of the Navigation Timing specification.

No. What it means depends highly on what the page actually does. For example, in the case of Twitter from a year or so ago, the page was completely blank at onload and the content was all rendered afterward in javascript (they have since moved to server-side rendering so that is no longer the case).

It's also not unusual to have things that are not visible to the user push out the onload time (images below the fold, tracking beacons, etc).

As long as you get rid of "fully interactive for the user" and change it to loadEventStart then it is technically correct.


RE: Document Complete Metric - satishtamilan - 10-02-2014 06:20 PM

Thanks ALL and Patrik and which metric from the Webpage Test which will define the load event end?


RE: Document Complete Metric - pmeenan - 10-03-2014 01:51 AM

For browsers that support Navigation Timing, the Navigation Timing values are reported directly as loadEventStart and loadEventEnd


RE: Document Complete Metric - satishtamilan - 10-03-2014 12:38 PM

SO Document complete is loadEventstart attribute of the Navigation Timing specification?


RE: Document Complete Metric - pmeenan - 10-04-2014 01:24 AM

In most cases they will be the same (the definition of the metric is the same but it is measured differently) - like in the Javascript redirct case - the event will happen at the same time but the reported times will be different because Navigation timing is relative to the most recent navigation.


RE: Document Complete Metric - satishtamilan - 10-06-2014 10:48 PM

Thanks Patrik.. Understand that Document complete is Load event start of the Navigation Timing.. From the Below Test Result

http://www.webpagetest.org/result/141006_KF_K67/1/details/

Which Metric I can take as Load Event End since my requirement is to monitor load event end.

ie document complete(Load Event start) + ????? = (Load Event End)

Pls let us know what is the component from the above test result we can use to get load event end time..


RE: Document Complete Metric - pmeenan - 10-07-2014 12:53 AM

You can use loadEventEnd if the navigation timing data is good enough for your needs (and if all of the browsers you care about support it).

If you want to include the redirects you can use Document Complete + (loadEventEnd - loadEventStart) but that still only works for browsers that report navigation timing.