Current time: 12-14-2019, 12:21 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Why more than 500ms time difference between DOM Content Loaded and Onload
09-22-2015, 08:37 PM
Post: #1
Why more than 500ms time difference between DOM Content Loaded and Onload
Hello,

Thanks for the nice testing tool and site.

I am testing using default settings and getting DOM Content Loaded load time of around 1s to 1.5s and getting OnLoad Time of 1.5 to 1.9s

I would like to know the following -

1. Why is there more than 500ms time difference between DOM Content Loaded and
OnLoad Time ?

2. Why is there so much final load time variation even though I am using the same test settings (default) ?
Find all posts by this user
Quote this message in a reply
09-25-2015, 08:40 AM
Post: #2
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
Post a link to your test results for more informed responses.

Like help speeding up your site? Skype me @ ID davidfavor for a quote. Be sure to include your site name in your Skype Add Contact request.
Find all posts by this user
Quote this message in a reply
09-25-2015, 09:28 PM (This post was last modified: 09-25-2015 09:28 PM by kmoksha.)
Post: #3
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
(09-25-2015 08:40 AM)dfavor Wrote:  Post a link to your test results for more informed responses.

Thanks for responding.

Here is the link of the test results - http://www.webpagetest.org/result/150925_6A_N2W/
Find all posts by this user
Quote this message in a reply
09-27-2015, 11:27 AM
Post: #4
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
No reply whatsover ? Is this forum active ?
Find all posts by this user
Quote this message in a reply
09-29-2015, 01:34 AM
Post: #5
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
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).
Visit this user's website Find all posts by this user
Quote this message in a reply
09-30-2015, 10:20 PM
Post: #6
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
(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 ?
Find all posts by this user
Quote this message in a reply
09-30-2015, 11:08 PM
Post: #7
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
Do you have a link to the test result with the timeline capture?

All browsers will behave differently. You can test Firefox or IE to see if either of them behave differently. The CPU just indicates that code is running doing something in the gap and the timeline would help you understand what it is.

Measuring the time without the browser yielding won't necessarily give you better data. The measurement might be faster but the page may also be blank. If you want the user to actually see content then you have to do layout and paint the screen.

If you want the actual measurement to be faster you can use the Dulles Thinkpad locating which has faster CPU so the processing will be shorter - but that doesn't really do anything but make the measurement faster for CPU-constrained operations.
Visit this user's website Find all posts by this user
Quote this message in a reply
10-07-2015, 12:36 AM
Post: #8
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
(09-30-2015 11:08 PM)pmeenan Wrote:  Do you have a link to the test result with the timeline capture?

All browsers will behave differently. You can test Firefox or IE to see if either of them behave differently. The CPU just indicates that code is running doing something in the gap and the timeline would help you understand what it is.

Measuring the time without the browser yielding won't necessarily give you better data. The measurement might be faster but the page may also be blank. If you want the user to actually see content then you have to do layout and paint the screen.

If you want the actual measurement to be faster you can use the Dulles Thinkpad locating which has faster CPU so the processing will be shorter - but that doesn't really do anything but make the measurement faster for CPU-constrained operations.

Patrick,

I do not know how to give link of the time line capture. I am posting here the screenshot of the same.

Testing with Dulles Think pad is also giving similar results - http://www.webpagetest.org/result/151006...1/details/


Attached File(s) Image(s)
   
Find all posts by this user
Quote this message in a reply
10-07-2015, 12:49 AM
Post: #9
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
If you go to the chrome tab in the advanced settings there is a "capture devtools" checkbox. Here is a test example: http://www.webpagetest.org/result/151006...c723a8646/

On the left of the waterfalls will be links to download or view the timeline.

It does look like it is the layout/paint (at least in the capture that I did) that is causing the delay between DCL and onload.

If you need to know exactly why it is taking so long to do the layout/paint then you will need to collect a trace (also in the chrome tab or in about:tracing locally) but you'll be deep in the guts of Chrome's internal code at that point.
Visit this user's website Find all posts by this user
Quote this message in a reply
10-10-2015, 07:17 AM
Post: #10
RE: Why more than 500ms time difference between DOM Content Loaded and Onload
(10-07-2015 12:49 AM)pmeenan Wrote:  If you go to the chrome tab in the advanced settings there is a "capture devtools" checkbox. Here is a test example: http://www.webpagetest.org/result/151006...c723a8646/

On the left of the waterfalls will be links to download or view the timeline.

It does look like it is the layout/paint (at least in the capture that I did) that is causing the delay between DCL and onload.

If you need to know exactly why it is taking so long to do the layout/paint then you will need to collect a trace (also in the chrome tab or in about:tracing locally) but you'll be deep in the guts of Chrome's internal code at that point.

The capture option is enabled but I am not getting link how you are getting. And have no idea of how to collect a trace.

Can you please help in finding out what the reason fo the delay between DCL and onload time is. The results obtained with webpagetest have a huge variation in time even when done with the same settings. What could be the reason for that ?

Here is link of another test which I did - http://www.webpagetest.org/result/151009_5W_151Y/
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)