Tested with Chrome 60 and Firefox 51 … I’m getting pretty much exactly the same loading times in both browsers.
But I’ve only tested an appliance with a self-signed certificate where you need to confirm the browser exception.
If this is happening for properly signed certificates, could be dependent on the ciphers used, etc. (out of my depth here, sorry :)).
Alternatively, the browser could be lying and spending time elsewhere.
@xian Do you have any details about the certificate?
(Chrome inspector has a Security tab, with all the info)
The certificate I tried was…
ECDHE_RSA with P-256,
signature algorithm PKCS #1 SHA-1 With RSA Encryption
subject public key algorithm PKCS #1 RSA Encryption