Enable HTTP 2.0 for loading assets via CDN

In the past months, some PageSpeed metrics (core web vitals) have deteriorated, which has a negative impact on CR & loading times.

Examples (for my community):

• LCP → not passed
• INP → not passed
• FCP → not passed
• SI → not passed

INP “is a metric that assesses a page's overall responsiveness to user interactions by observing the latency of all click, tap, and keyboard interactions.” (source) 

In Gainsight CC, user avatars, page icons, CSS as well as JavaScript Code is being loaded via a CDN which uses HTTP1.0.

HTTP 1.X requires a new connection for each file, i.e. every single asset (avatar, icon etc.) is being loaded one after another. This takes significantly longer than HTTP 2.0.

HTTP 2.0 allows multiple files to be loaded simultaneously over a single connection. This significantly reduces overhead and speeds up the loading of assets such as images, CSS, and JavaScript files.

Another benefit of HTTP 2.0 is “server push”. This feature allows the server to proactively send assets to the client before it even requests them. For example, when an HTML page is loaded, the server can “push” the associated CSS or JavaScript files. This saves valuable time and makes loading assets more efficient.

That’s why I propose that Gainsight implements HTTP 2.0 for Gainsight CC.