Current time: 12-13-2019, 11:18 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
First Byte Time “FBT” findings and research results
01-17-2016, 09:25 AM (This post was last modified: 01-17-2016 11:07 AM by Anton Chigurh.)
Post: #25
RE: First Byte Time “FBT” findings and research results
(09-29-2015 12:57 AM)Gnaser Wrote:  It seems like Anton is suggesting that reducing bloat could improve TTFB but doesn't actually know why, even though he's seen it happen in the past.

No one else thinks it's possible because the server can't possibly know what assets are even going to be called until the HTML requests them which is after FirstByte.

IMO he's right though, If the same resource is serving pages and assets.
And happily, I was finally able to prove this. It's a fact.

Read here. Then read here.

The only thing going on besides the "handshake" during the FBT, is that in request #1 the server is composing the executable page source code and sending it to the browser, which downloads it then executes it. Then the content starts loading.

The more requests you have, the longer it takes to compose this file and the longer it takes to load it.

More requests = more bloat = longer FBT.
Quote:the server can't possibly know what assets are even going to be called until the HTML requests them
It DOES know, it finds out after the handshake. It queries the db and the scripts during FBT, in order to then compose the executable page source code. Which the browser then executes - it's how the BROWSER knows what to look for!
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: First Byte Time “FBT” findings and research results - Anton Chigurh - 01-17-2016 09:25 AM

Forum Jump:


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