Website optimised for HTTP 2.0, not 1.1 - Bad idea?

Reado

• October 05, 2018 04:22

With HTTP/1.1, our website had a separate sub-domain that handled all requests for images, CSS and JavaScript. This configuration also meant that no cookies were used on that sub-domain, which was the recommendations given by YSlow at the time. As things have moved on, we have implemented HTTP/2.0 and scrapped the sub-domain, so now everything is served from one domain. For clients using HTTP/2.0, our website is faster than ever, but would it be fair to say that clients that still use the HTTP/1.1 method would see poorer performance? Looking at our Google Webmaster Tools, our page load time is higher compared to what it is in Google Chrome or Firefox. I'm guessing this is because Googlebot still uses HTTP/1.1 and therefore will not see the benefits of HTTP/2.0. So instead of just optimising the website for HTTP/2.0 and removing the optimisations for HTTP/1.1, should I be optimising the website for both, which would cater for Googlebot too? If I re-add these optimisations for HTTP/1.1, is it likely our Google Webmaster Tools will start to report better load times?

• 

  Reado

  • October 05, 2018 09:26

  I think I just answered my own question!

  0
• 

  cPanelLauren

  • October 09, 2018 13:46

  Hi @Reado I'm glad to hear that you were able to resolve your issue - we don't allow links to 3rd party sites, let us know how you answered the question if you have time! Thanks!

  0

Please sign in to leave a comment.