From the far left to the far right is the time of the total loading experience (1.03s).
The second item "?" didn't start loading until about 75% into the entire loading process.
jerebear
2009-04-09 07:28:48
A:
but my question is WHY the second item didn't load until then... shouldn't it start immediately?
swalkner
2009-04-09 07:37:34
Can you show what items where being loaded on those first few lines? That would help us determine the lag.
jerebear
2009-04-09 08:15:09
@Swalkner : I'm guessing that the second item is dependent on the first (e.g. the html is the first item and an img tag is the second). In that case, the gap is the time taken by the browser to parse the HTML and figure out that there's an img tag, after which it starts requesting for the img (the second item)
talonx
2010-09-02 11:36:46
A:
the blue and red lines mark when the javascript events (DOMContentLoaded and load) are fired.
mozdev-documentation for DOMContentLoaded and load:
Fired on a Window object when a document's DOM content is finished loading, but unlike "load", does not wait until all images are loaded.
Schnalle
2009-04-09 07:41:41
+1
A:
but my question is WHY the second item didn't load until then... shouldn't it start immediately? – swalkner
On my machine, it is nearly sequential. I would contribute the lag to cpu time required to process and render the data.
I would guess the blue line is when the browser starts displaying and the red line is when the layout finished.
Unknown
2009-04-09 07:41:53
A:
I am having a similar problem loading pages off my own local server, IE is lightning quick, and firefox takes ages because of these gaps in loading.
Spencer
2010-01-13 17:13:34