Signed Exchanges (SXG) is a delivery mechanism that can help speed up your site and improve Largest Contentful Paint (LCP) by enabling privacy-preserving cross-origin prefetch. At I/O 2022, the SXG working group at Google previewed plans to add new SXG features and support site navigations on additional surfaces. Today, we are announcing the first set of these features, with more to come over the next few months:
- Support for desktop site navigations
- Google Search support for SXG from Top Stories and News
- Support for server side personalization
Read on to learn more about these features and how you can leverage them to improve the user experience on your site.
Support for desktop navigations
With this release, Signed Exchanges will now be available for desktop cross-origin navigations on Chromium browsers. This builds on the existing support for Android mobile and means that now you can use SXG to also cache and prefetch the desktop version of your site.
We estimate1 that this release will, on average, double SXG’s coverage of your site’s visits, enabling improved loading and performance for more users. Today on mobile, this speed improvement is between 300 and 400 ms of LCP reduction on average for navigations from Google Search.
How you can leverage this feature
Enabling Signed Exchanges for the desktop version of your site does not require any additional work on your part. This feature is already supported on both Cloudflare’s easy-to-use Automatic Signed Exchanges tool and the open source SXG toolkit.
You can opt out of this if you want using the supported-media meta tag. Learn more here.
Learn more about the impact of Signed Exchanges**
Several global brands and sites have already benefited from Signed Exchanges. Let’s look at a few case studies for current SXG adopters on Android mobile:
Cloudflare, a leading Content Distribution Network (CDNs), ran an experiment to measure the impact of Signed Exchanges for its customers of the 500 sites they tested:
- 85% saw an improvement in LCP.
- 98% observed reduced Time to First Byte (TTFB).
- Median 20% improvement across these metrics.
RebelMouse, a prominent Content Management System (CMS), recorded an improvement in business and performance metrics for their customers including:
- 41% LCP improvement for Narcity.
- 27% increase in sessions per user for Paper Magazine.
- 21% decrease in loading time for MLT blog.
Google Search support for Top Stories and News
Google Search is an early adopter of Signed Exchanges’ privacy-preserving cross-origin prefetch, which to-date has been available for site navigations from Search’s Web Page Results. Starting in July 2022, Search is expanding this support to also include navigations from Top Stories and News. Note that while SXG does not impact ranking or selection criteria on Google Search, it does have the ability to improve your site’s Core Web Vitals, LCP in specific.
This feature requires no additional work on your part to enable and will be available automatically to both existing and new adopters.
Support for server-side personalization
Signed Exchanges uses a cache to prefetch and serve content that has been cryptographically signed by the origin. Cached content can be sent to multiple different users or to the same user multiple times. In the past, this has meant that SXG has not been compatible with sites that use server side personalization—that is, different HTML for logged in users.
Today, we’re adding Dynamic SXG—a new feature that allows you to selectively enable SXG for visits from cookieless users only on Chromium. Logged in navigations, with server-side personalization, will continue to serve non-SXG versions of your site.
This is especially impactful for sites that dynamically compute a unique web page for each logged-in user and hence often tend to have higher TTFB and LCP stemming from database lookups. Dynamic SXG gives you the option and flexibility to leverage SXG to speed up visits to your site for certain users without impacting your ability to provide a personalized experience to others.
How to enable this feature
Enabling Dynamic SXG requires you to add a Vary: Cookie annotation to the HTTP header of pages that contain server-side personalization. Here are some examples of how to do this, based on your server:
Note that Signed Exchanges continues to be compatible with any client-side personalization you use to load elements such as a login widget, shopping cart, or personalized news feed.
What’s next
The SXG working group at Google is continuing to invest in adding new features, capabilities and surfaces to Signed Exchanges, based on the community’s interest and feedback. We have some exciting upcoming features planned over the next few months—keep a lookout on the Chrome Developers blog to learn more.
Footnotes
: This is an estimate based on historical data for Signed Exchanges visits on Chromium browsers on mobile. Actual numbers will likely vary by site.
This post is also available in:
English