Current time: 09-16-2019, 04:34 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Using LetsEncrypt Certificates Properly doubles First Byte Time
04-18-2019, 12:09 AM
Post: #4
RE: Using LetsEncrypt Certificates Properly doubles First Byte Time
Hi / Servus,

The first thing I noticed is that the site appears to be hosted in Germany but you used a US test location. Due to the unavoidable latency between these locations - ssl negotiation will take a bit longer. It does based on the numbers below - add about 90ms in total. Like peeman said - due to the larger certificate - you probably have an additional round trips during the negotiation process.
The TTFB is also a bit different - but that's somewhat normal to have a bit of variation.

I would personally always load the intermediate, without it it's possible some clients may not be able to connect since they cannot verify the entire chain.

All other metrics are very similar.

If your trying to optimize for users that are so far away - then look at either cloudflare or cloudfront style CDN - which will terminate your sites connection as close as possible to the client.


Test 1 (with intermediate)
----------
DNS Lookup: 27 ms
Initial Connection: 138 ms
SSL Negotiation: 261 ms
Time to First Byte: 501 ms
Content Download: 201 ms

Test 2 (Without)
-----------
DNS Lookup: 26 ms
Initial Connection: 140 ms
SSL Negotiation: 171 ms
Time to First Byte: 438 ms
Content Download: 199 ms
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Using LetsEncrypt Certificates Properly doubles First Byte Time - dreamwerx - 04-18-2019 12:09 AM

Forum Jump:


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