Getting Ready for HTTP/2

For general web development questions that are not specifically related to CSS HTML Validator. This includes (but is not limited to) general HTML, CSS, Accessibility, JavaScript, and SEO questions.
User avatar
RSteinwand
Rank VI - Professional
Posts: 596
Joined: Mon Jun 09, 2008 2:12 pm
Location: Fargo, ND
Contact:

Re: Getting Ready for HTTP/2

Post by RSteinwand »

Every CDN has an associated DNS lookup and https negotiation penalties. Best to keep with what you have unless you're going to adopt a bunch of bloat now.
Rick
User avatar
Albert Wiersch
Site Admin
Posts: 3783
Joined: Sat Dec 11, 2004 9:23 am
Location: Near Dallas, TX
Contact:

Re: Getting Ready for HTTP/2

Post by Albert Wiersch »

RSteinwand wrote:Every CDN has an associated DNS lookup and https negotiation penalties. Best to keep with what you have unless you're going to adopt a bunch of bloat now.
Yep, that's what I was thinking. It's faster to put it all on one server especially with HTTP/2... unless it's a bloated site with megabytes of junk. I certainly don't plan to bloat up my website even though that seems to be the "modern" thing to do these days. :)
Albert Wiersch, CSS HTML Validator Developer • Download CSS HTML Validator FREE Trial
User avatar
Albert Wiersch
Site Admin
Posts: 3783
Joined: Sat Dec 11, 2004 9:23 am
Location: Near Dallas, TX
Contact:

Re: Getting Ready for HTTP/2

Post by Albert Wiersch »

MikeGale wrote:As HTTP2 gets more real, there's another way to check for it. Browser independent. Run Wireshark.
I have not used Wireshark but here is another site that can be used to see if it's enabled:
https://tools.keycdn.com/http2-test

I enabled HTTP/2 on some of my other domains but couldn't figure out why it wasn't working on one of my domains. It does work when the protocol is https, then I remembered something about HTTP/2 only being enabled (supported) with TLS/HTTPS in most browsers. The link above says this:
This test can check HTTP and HTTPS but most browsers only support HTTP/2 for HTTPS, which means you must migrate to HTTPS if you want to take advantage of the performance benefits.
Albert Wiersch, CSS HTML Validator Developer • Download CSS HTML Validator FREE Trial
User avatar
RSteinwand
Rank VI - Professional
Posts: 596
Joined: Mon Jun 09, 2008 2:12 pm
Location: Fargo, ND
Contact:

Re: Getting Ready for HTTP/2

Post by RSteinwand »

Albert, if you check the waterfall for your home page, there's only 22 requests (scripts, images, stylesheets), and 5 are other domains (mostly Google), so your pages are lightweight like mine. My home page only has 20 requests and it's my heaviest page, but I also don't see the need for Google fonts and have lots of sprite images and use linear gradients whenever possible.

You could reduce the number of requests by spriting your quote images and social media icons and using a linear gradient for your menu.

You also could do a dns prefetch for your external domains.

Code: Select all

<link rel=dns-prefetch href="//www.google-analytics.com">
Rick
User avatar
Albert Wiersch
Site Admin
Posts: 3783
Joined: Sat Dec 11, 2004 9:23 am
Location: Near Dallas, TX
Contact:

Re: Getting Ready for HTTP/2

Post by Albert Wiersch »

Hi Rick,

Thanks. I could tweak my page a little but I don't think there's anything that I could easily do that would speed it up significantly (enough for someone to notice). The dns-prefetch idea is interesting but I suspect that is a very common lookup and would already be in the DNS cache.

I suppose I could get rid of the Google font though... but I do like the look of that "clean" font and I think it makes the site look a little different than many others. I'll keep it for now.
Albert Wiersch, CSS HTML Validator Developer • Download CSS HTML Validator FREE Trial
User avatar
RSteinwand
Rank VI - Professional
Posts: 596
Joined: Mon Jun 09, 2008 2:12 pm
Location: Fargo, ND
Contact:

Re: Getting Ready for HTTP/2

Post by RSteinwand »

Google Groups is QUIC enabled: https://groups.google.com
Rick
User avatar
RSteinwand
Rank VI - Professional
Posts: 596
Joined: Mon Jun 09, 2008 2:12 pm
Location: Fargo, ND
Contact:

Re: Getting Ready for HTTP/2

Post by RSteinwand »

We're testing a VM version of load balancing that supports HTTP/2. If it works, we'll probably go for the appliance type with an ETA of about a month. Since that involves SSL on the public side (we already have it on the secure side), and we use session cookies, I'll probably try to incorporate a cookieless domain at the same time.
Rick
Post Reply