Why more than 500ms time difference between DOM Content Loaded and Onload

[kmoksha]

(09-29-2015 01:34 AM)pmeenan Wrote:  Your best bet to see what is happening during that time is to enable timeline capture in the chrome tab of the advanced settings which will capture a dev tools timeline.

My guess since there are no images or external resources is that the browser doesn't yield to do the layout/paint until between DCL and onload and it's that operation that is consuming the time (you can see the CPU is pegged between the two).

Thanks Patrick for the reply.

I did enable the timeline capture. It is giving around 500 to 600 ms complete load time and DSL also same time. Other than that, I am not able to analyse.

Which browser / CPU does not yield to do the paint between DCL and onload ? The CPU and browser used by webpagetest.org ?