New Http2 implementation

Web Performance Optimization Discussions
1

Our site has had H2 running for only 48 hours.
We also moved to a h2 cdn which is Cdn77.
Take a look at the waterfall and this test and tell me if this seems right.
Are we missing something?
thank you
Brian
http://www.webpagetest.org/result/160505_3C_19AZ/1/details/

2

looks about right. Not sure where the first line comes from - I use the same services and don’t see it on my site for example… the relevant part of my nginx config for stapling ( using a local caching DNS server ) is:

    # OCSP Stapling
    ssl_stapling on;
    ssl_stapling_verify on;
    resolver 192.168.122.1 8.8.8.8 8.8.4.4 valid=300s;
    resolver_timeout 5s;

What in particular are you worried about?

EDIT: I think it’s a moot point not supporting TLS 1.0 at this point…

3

I am just wondering if the waterfall is correct for an http2 site.
Since this is so new just checking to make sure we are not missing anything.

4

You may want to double-check either your CDN configuration or the HTML links on your site.

With HTTP/2, all requests to your site should go to https://shopbakersnook.com, even though they’re being served by the CDN. The waterfall shows that this happens for most of your requests, but not for others, especially any of the images.

If you look at the Connection View, there is one connection to your site’s domain, but there’s also another connection to https://1671625845.rsc.cdn77.org.

So you effectively, your website is serving it’s data from two HTTP/2 domains.

This will reduce the effectiveness of HTTP. This is kind of like domain sharding, which used to be something to improve performance with HTTP/1.1, but not with HTTP/2.

So I would check to see where this is happening. Is it a CDN config issue or are your HTML links pointing directly to those image assets at CDN77? Based on a couple HTTP responses I looked at, the latter doesn’t seem to be the case, but I’d double-check anyway.

Also, you may want to check that your certificate (or whoever owns it) hasn’t expired. OCSP requests mean that the browser is checking the status of that certificate. That’s the reason for the first line. You shouldn’t see this if the certificate is valid.

5

Thank you we are checking today…