Looks like they also experiment with the QUIC protocol on their sites (on YouTube too) because there is a HTTP header called: Alternate-Protocol 443:quic in th

Looks like they also experiment with the QUIC protocol on their sites (on YouTube too) because there is a HTTP header called: Alternate-Protocol 443:quic in their requests. QUIC isn't enabled by default in Chrome but you can enable it in chrome://flags and then you can also check chrome://net-internals/#events to see if there are any "QUIC SESSION" when you load a page. Benchmark shows they still have to work on it: http://www.connectify.me/taking-google-quic-for-a-test-drive/ http://www.connectify.me/taking-google-quic-for-a-test-drive...