Skip to main content
Open

SEO Improvement: HTTP/2 push

Related products:CC Analytics & Reporting
  • December 10, 2021
  • 4 replies
  • 85 views
A
  • Annina
  • Contributor ⭐️⭐️

We’ve had an SEO audit done on our community. There are a number of improvements we’ll present here as ideas. 

While the Insided platform of Insided is running on HTTP/2, it supports only the passive features of HTTP/2 - such as multiplexing and prioritization. Several other key features such as server push go unutilized.

Server push essentially allows the domain to create associations between requests. For example, if we know that every page on the domain will have to load the JS framework and a CSS bundle, it'd be possible to create a link header referencing those resources. This'll inform browsers to expect the files. We would not have to wait for the HTML to be loaded and interpreted before fetching the files.

In some services, like Cloudflare, this can be extrapolated from the rel="preload" tags. Otherwise, this might have to be set up manually.

Integration of server push could have some considerable performance effects, specifically in the direction of lowering LCP and CLS.

Introduction to HTTP/2: https://developers.google.com/web/fundamentals/performance/http2 

Elisa OmaYhteisö https://yhteiso.elisa.fi

4 replies

I

Hi @Annina, thanks for your idea. The expectation is clear. 

I'd still put this idea to 'open' to collect more votes and feedback.

I
Updated idea statusNew→Open
dilekgencer
  • dilekgencer
  • Gainsight Employee ⭐️
  • December 17, 2021
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
A
  • Annina
  • Author
  • Contributor ⭐️⭐️
  • January 25, 2023

Here’s additional and updated information to this idea. We wanted to share a use case and potential solution. 

In order to further optimize delivery of content, and to keep web vital scores in check, we want to fundamentally update the way assets are handled by the browser. Rather than wait for a browser to request the files it needs, we push the required files to them ahead of time. There's two techniques that are suited for this job: HTTP/2 Server Push and 103 Early Hints. It would improve the structural performance of InSided's platform beyond that of its competitors.

A use case is for example when customer is visiting one of InSided's community, he/she requests the frontpage of the site. InSided's software already knows exactly what files the user needs, and rather than waiting for the user to request them, it pushes the data towards the user. This results in the user receiving the data before the page has even started rendering, resulting in a much faster, smoother user experience. This in turn translates to improved web vitals, which mean a better ranking in search engines.

Potential solution is to integrate HTTP/2 Server Push or 103 Early Hints as a core part of InSided's software. 

Elisa OmaYhteisö https://yhteiso.elisa.fi
Suvi Lehtovaara
Terms & ConditionsCookie settingsAccessibility statement