05-02-2012, 07:09 AM
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?
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?