6

I have been studying the performance of a website I am building, and notice a curious thing that I can't find the answer to: two requests (always the same two) mysteriously have prolonged stalled times adding drastically to the overall page load.

Network analyzing in Chrome F12 tools

As you can see, the /css and /js pages are stalling for seemingly no apparent reason. Would anyone know what's going on (please say so if you need more information)?

closed as off-topic by womble Dec 1 '15 at 1:08

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – womble
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Answer is as simple as <it's server or network side> :) You must provide too many details, or specify one to get an answer. – GioMac Nov 20 '15 at 16:12
  • What does the grey in the timeline mean? If you hoover on it with your mouse pointer, what does it tell? Other things, how are you loading the css and js files? Via a javascript or normal <script> ecc tags? – Fredi Nov 20 '15 at 16:25
  • @Fredi The gray means stalled. I was asking why the requests are stalling. I am generating the /css and /js files through PHP (perhaps that has something to do with it). – Krii Nov 20 '15 at 16:34
  • @Krii, ok from here: developer.chrome.com/devtools/docs/network (I suppose is what you're using) seems that it's time spent in your browser. As to why or how, as for the link, maybe you've reached the 6 parallel connections that chrome uses. If this is the case, can you remove, let's say, an image from your page and retry? – Fredi Nov 20 '15 at 16:39
  • 1
    Like you said, Krii, my instinct tells me this is related to PHP performance. IIRC, the gray bar means that the connection was initiated and the green bar means receiving data. Therefore the time from request to first-byte is large which points to PHP. – Eric Wendelin Nov 20 '15 at 17:51
1
+50

ok from here: http://developer.chrome.com/devtools/docs/network (I suppose is what you're using) seems that it's time spent in your browser. As to why or how, as for the link, maybe you've reached the 6 parallel connections that chrome uses. If this is the case, can you remove, let's say, an image from your page and retry?

1

it seems that the first start bit is taking so much time.You can test your performance on Pingdom or Gtmetrix you will get a clear idea where you need work exactly. For loading time of first bit you need to contact your hosting provider.

Not the answer you're looking for? Browse other questions tagged or ask your own question.