ssl negociation

[amsa]

hi everyone.

Working to improve my webperf I'm surprise by some result.
So i made a test with a simple gif 1X1px.
and i got:
Load Time 0.295s
First Byte 0.203s
Start Render 0.300s
Speed Index 0.300s

So when Google has stated 1 that web servers should have a server response time of 200 milliseconds or less. i'm not sure i haven't a problem, and how can i reach this 200ms.
Event with a static html page

And when i check in detail i saw the SSL Negotiation is 91 ms.
So half, of 200ms is already used by ssl negociation.

Does this ssl Negociation duration of 91ms is normal, for you?
Can i improve it?


DNS Lookup: 39 ms
Initial Connection: 30 ms
SSL Negotiation: 91 ms
Time to First Byte: 39 ms
Content Download: 3 ms

[akshayranganath]

At the outset, your webpage's performance seems to be very good. The guidance from Google is just that - it is to ensure that the overall experience is fruitful for the end user. If you see the overall performance, the page seems to be ready in under 300 ms. Even if you reduce it by say, 50ms, I doubt if end users would even notice it.

Having said that, can you elaborate a bit more about your website and how it is hosted? Typically, the TLS connection could take a bit more time based on how the sever is configured, the kind of certificate - single domain vs SAN, number of domains on the SAN certificate, the cipher used for the TLS connection and the current load on the server and WPT testing instance. You can find more resource on tuning TLS on https://istlsfastyet.com/.

If you could run the test 7 to 9 times and check the median, you would see a more reliable number.

[amsa]

Thanks @akshayrangananth for your answer.
"your webpage's performance seems to be very good."
Unfortunatly the graph you saw isn't a webpage but just an image (gif 1px 34Ko)

A webpage would be more something as (see image attached)

Quote:Having said that, can you elaborate a bit more about your website and how it is hosted?

There Is 7 websites (domain) each one with 1 Wordpress + 1 Prestashop
- one VDS Intel® Xeon® CPU E5-2630L v2 @ 2.40GHz Ram 16Go
- apache 2.2
- Php 7.0
- VHOST

Quote:Typically, the TLS connection could take a bit more time based on how the sever is configured, the kind of certificate - single domain vs SAN, number of domains on the SAN certificate,

1 domain by Certificate Let's encrypt with SNI
TLS 1.0, 1.1, 1.2

Quote:the cipher used for the TLS connection

Here is the Cipher List
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA


# TLS 1.1
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA


# TLS 1.0
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA

Quote: and the current load on the server and WPT testing instance.

The average Load is ~0.31