Current time: 11-26-2020, 08:49 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Late Start Render Time - What is blocking?
08-12-2014, 12:22 AM (This post was last modified: 08-12-2014 12:26 AM by BITS.)
Post: #7
RE: Late Start Render Time - What is blocking?
(08-08-2014 01:45 AM)pmeenan Wrote:  FWIW, Chrome does a pretty good job at rendering it as soon as it can: http://www.webpagetest.org/video/compare...G3-r:1-c:0

I think you're into browser-specific pipelines at this point (though figuring out what blocked the text from rendering right away in Chrome would be good).

I tried a few things to get closer to a solution but without success:

1) Disabled all plugins in WordPress
2) Found that the genericons.css loads an inlined font via @font-face, so I kicked the complete file out (it's still available but empty)
3) Removed all inlined images from the css-file to exclude the inline images as the route of failure

A few more tests in Firefox:
Just HTML + CSS: http://www.webpagetest.org/result/140811...1/details/
HTML + CSS + 2 Pictures: http://www.webpagetest.org/result/140811...1/details/

As soon as I add pictures the StartRender Time is shifted backwards.

I also did the tests in Chrome:
Just HTML + CSS: http://www.webpagetest.org/result/140811...1/details/
HTML + CSS + 2 Pictures: http://www.webpagetest.org/result/140811...1/details/

Is there any possibility in Chrome to dive into the generation of the CSSOM (or after that) to find out where the time is "lost"? Does the "DOM Content Loaded" event also include the CSSOM?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Late Start Render Time - What is blocking? - BITS - 08-12-2014 12:22 AM

Forum Jump:


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