HTTP/2 and HTTP/3 are newer versions of the protocol browsers use to fetch pages. They load many files over one connection, so pages with lots of images, styles and scripts load faster.
Do they affect rankings?
Not directly. They improve speed, and speed affects user experience and Core Web Vitals.
How to get them
- HTTP/2 needs HTTPS and is supported by almost every modern host and CDN.
- HTTP/3 runs over QUIC and is offered by many CDNs and newer servers.
What changes for your site
With HTTP/1.1, browsers open several connections and fetch files a few at a time. HTTP/2 sends many files over one connection at once, so old tricks like combining all images into one sprite matter less. HTTP/3 adds faster connection setup and copes better with unreliable mobile networks.
Crawlers
Search engine crawlers can use HTTP/2 when your server supports it, which can make crawling more efficient for the server. It does not change how pages are ranked.
Before you switch
- Make sure HTTPS is set up correctly; HTTP/2 needs it in browsers.
- Test the site after switching, especially older integrations and payment pages.
- Keep HTTP/1.1 available for old clients; servers fall back automatically.
Measure the effect
Compare page load times before and after with the page speed checker. Pages with many small files benefit the most.
Check your site
The HTTP/2 checker and HTTP/3 checker show what your server supports. If it only speaks HTTP/1.1, ask your host or put a CDN in front of the site.
0 comments