The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 802 - File: showthread.php PHP 7.2.19-0ubuntu0.18.04.2 (Linux)
File Line Function
/showthread.php 802 errorHandler->error



Current time: 10-15-2019, 06:14 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Fully loaded time is long past document complete
05-02-2012, 07:09 AM (This post was last modified: 05-03-2012 07:25 AM by fuzzymazoid.)
Post: #1
Fully loaded time is long past document complete
Hello there, I have been seeing some odd behavior where "Fully Loaded" time is often long after the Document Complete time, even for sites with no javascript.

My test: http://www.berkshirehathaway.com/ (since it only has 3 objects, it eliminates a lot of external factors)

Results: http://www.webpagetest.org/result/120501_6C_4676S/

In Run 1 ( http://www.webpagetest.org/result/120501...1/details/ ), Document Complete and Fully Loaded are fairly close, and the difference appears to be the nonexistent favicon.

In Run 2, however ( http://www.webpagetest.org/result/120501...2/details/ ) we get a Fully Loaded time of 2.5 seconds.

Run 3 is similar to Run 1.

Why is the result in Run 2 so far off from the other two? It throws the median quite a bit, and I can't figure out what would still be loading in Run 2 that would make it still see network activity.

I have seen this in quite a few different tests, but this is by far the simplest example. Am I just missing something about the way Fully Loaded is calculated?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Fully loaded time is long past document complete - fuzzymazoid - 05-02-2012 07:09 AM

Forum Jump:


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