2

What could be the reason that the total time of a request is higher than the Connection Setup time + Request/Response time?

enter image description here

357.32ms > (19.04 + 0.56 + 8.56 + 23.46 + 0.41)ms

Am I missing something?

Improve this question
7
  • Maybe Explanation measures time passed since the page started loading? Can you show more of the waterfall?
    – woxxom
    Commented Jan 18, 2017 at 15:22
  • You may be right, I will check it out, Explanation is a link to Google explanations. EDIT: Checked, the next request has lower total time, so it may not be it
    – Ofiris
    Commented Jan 18, 2017 at 15:24
  • @Ofiris Are you able to reproduce this mismatch/provide a link to a page that causes it?
    – Gideon Pyzer
    Commented Jan 18, 2017 at 15:54
  • @Gideon After several tests, I couldn't reproduce this issue
    – Ofiris
    Commented Jan 26, 2017 at 11:10
  • I have exactly the same issue. @Ofiris did you manage to find a solution?
    – Michele
    Commented Aug 2, 2017 at 13:47

1 Answer 1

Reset to default
1

I had a similar problem. In my case I noticed that the "gap" was always after the "DNS lookup" as shown below. Somehow Chrome couldn't measure the time taken to translate localhost into127.0.0.1`

I solved the problem by replacing localhost to 127.0.0.1 in the URL bar. This removed 80%~90% of the overall load time

enter image description here

Improve this answer

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