Current time: 12-19-2017, 12:38 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
First request in repeat view is incorrect (not the requested url)
02-16-2017, 12:30 AM
Post: #1
First request in repeat view is incorrect (not the requested url)
For one of our websites we have a strange repeat view sometimes.
Sometimes the first request of the repeat view is not the test url.

Example test:
https://www.webpagetest.org/results.php?...e1b314f9dc

Repeat view for Run 1, 2, 4, 5, 6, 7, 8 are not correct
   

Repeat view for Run 3, 9 are correct.
   
Find all posts by this user
Quote this message in a reply
02-16-2017, 12:36 AM
Post: #2
RE: First request in repeat view is incorrect (not the requested url)
Is the HTML cacheable? That kind of looks like what I'd expect to see happen if it has a short TTL (like 1 minute). In everything besides 3 and 9 it is loading from cache so it won't show up in the waterfall.
Visit this user's website Find all posts by this user
Quote this message in a reply
02-16-2017, 01:23 AM (This post was last modified: 02-16-2017 01:32 AM by JeroenVdb.)
Post: #3
RE: First request in repeat view is incorrect (not the requested url)
Ah, the HTML has a 1min TTL yes indeed. So that is why I don't see it in the waterfall, I understand.

Why I was posting this: I am plotting all TTFB for this site in a graph for first and repeat view. I was seeing large burst-outs on some repeat view TTFB metric. See attachment for an example.

So the TTFB for repeat views is the TTFB of the first request that is returned from the server not including responses from the browser cache.

Just a thought: Is this then not a wrong representation of TTFB? Should it not be something around almost nothing (a few ms to get it from the cache)?

   
Find all posts by this user
Quote this message in a reply
02-16-2017, 03:07 AM
Post: #4
RE: First request in repeat view is incorrect (not the requested url)
It's probably more of an implementation detail but WPT largely focuses on "things that hit the network" and in some of the browsers it won't even see the things that came from cache and can't time them.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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