<p>Right after enabling cert-manager in <a href="https://github.com/kubernetes/ingress-nginx" rel="nofollow noreferrer">Ingress Controller</a> by TTFB (time to first byte) increased by 200+ms in most of the regions. Without SSL, it was &lt;200ms to 80% of the regions. After enabling SSL only 30% have TTFB &lt;200ms</p>

<p>without SSL
<a href="https://i.stack.imgur.com/RHQhZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/RHQhZ.png" alt="enter image description here"></a></p>

<p>with SSL
<a href="https://i.stack.imgur.com/froJ0.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/froJ0.png" alt="enter image description here"></a></p>

<p>My Ingress definition:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  annotations:
    kubernetes.io/ingress.class: nginx
    certmanager.k8s.io/cluster-issuer: letsencrypt-prod
    kubernetes.io/tls-acme: "true"
spec:
  rules:
    - host: gce.wpspeedmatters.com
      http:
        paths:
          - path: /
            backend:
              serviceName: wordpress
              servicePort: 80
  tls:
    - secretName: tls-prod-cert
      hosts:
        - gce.wpspeedmatters.com
</code></pre>

Gijo Varghese
<p>Switched to TLS 1.3 and I was able to above shave off extra 50-150ms!</p>

<p>I wrote a detailed blog post too: <a href="https://wpspeedmatters.com/tls-1-3-in-wordpress/" rel="nofollow noreferrer">https://wpspeedmatters.com/tls-1-3-in-wordpress/</a></p>

<p>With TLS 1.3:
<a href="https://i.stack.imgur.com/FGitc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/FGitc.png" alt="enter image description here"></a></p>
