Lighter pages for visitors who turn on data saver
Short answer: Some browsers let people switch on a data saver mode, and when they do, the browser can send a Save-Data: on request header with each request. Your site can read that signal and send a lighter page: smaller images, no autoplaying video, fewer web fonts and no background refreshing. It's an explicit request from the visitor, so treating it seriously is a good customer experience. Because support isn't universal, use it as an extra layer on top of a page that is already reasonably light, and make sure any caching keeps the light and full versions apart.
What the Save-Data hint is
MDN describes Save-Data as a network client hint that signals the visitor's preference for reduced data usage, whether because data is expensive, the connection is slow, or both. A value of on means the person has explicitly opted in to a reduced data mode on their device or browser.
Two details matter for a business site:
- It's a low-entropy hint, so the browser may send it without your server asking for it first.
- MDN says it should be honoured regardless of other hints about network speed. Someone on fast Wi-Fi who has data saver on still wants less data.
MDN marks the header as experimental and not Baseline, because it doesn't work in some of the most widely used browsers. Many visitors on limited plans will never send it, which is why it should never be your only performance plan.
What to change when Save-Data is on
MDN's own list of examples is a good starting point: smaller image and video resources, different markup and styling, and disabling polling and automatic updates. In practice, for a typical small business site that means:
- Images: serve a smaller or more compressed version of large photos, or skip decorative images entirely.
- Video: don't autoplay hero videos. Show the poster image and let people tap to play.
- Web fonts: fall back to system fonts, or load one weight instead of several.
- Third-party extras: delay chat widgets, social embeds and map embeds until the visitor asks for them.
- Background activity: stop polling for live updates, carousel autoplay and prefetching of other pages.
Keep the content the same. A data saver visitor should still see your prices, opening hours, booking button and contact details. The goal is a lighter page, not a lesser one.
Detecting it on the server
On the server, check the incoming request header. If Save-Data is on, choose the lighter template, image sizes or components. This works with any language or framework, because it's just a header.
The important follow-up is caching. If the same URL can return two versions, any cache in between needs to know. MDN's example shows the server responding with Vary: Save-Data, which tells caches that the response depends on that header. Without it, a CDN could store the light version and serve it to everyone, or store the full version and ignore the request.
If your CDN or hosting platform has its own cache key settings, check whether it respects Vary or needs the header added to the cache key explicitly.
Detecting it in the browser
In JavaScript, browsers that support the Network Information API expose navigator.connection.saveData, which is true when the visitor has asked for reduced data. MDN lists it with limited availability, so always check that navigator.connection exists before using it.
Browser-side detection is useful for things your server doesn't control: deciding whether to load a chat widget, whether to start a video, or whether to prefetch the next page. A simple pattern is to check once on page load and set a class on the <html> element, so your CSS and scripts can both respond to it.
Start with a page that's light by default
Because many visitors won't send the hint, the biggest gains come from improvements everyone gets:
- Use responsive images with sensible sizes so phones don't download desktop-width photos.
- Lazy-load images below the first screen.
- Compress images in modern formats where your setup supports them.
- Remove scripts and plugins you no longer use.
- Load third-party widgets only on pages that need them.
Then treat Save-Data as a second, stricter level for people who have asked for it.
Testing your changes
You can test without changing your phone settings:
- Use your browser's developer tools or a command-line tool to send a request with the
Save-Data: onheader. - Compare the total transfer size and the number of requests with and without the header.
- Check the response includes
Vary: Save-Dataif the HTML or images differ. - Load the page through your CDN twice, once with and once without the header, and confirm each gets the right version.
Also check the light version on a real phone. Make sure nothing important is missing, such as a menu that depended on a deferred script.
An illustrative example
A tour operator in Gisborne finds many bookings come from visitors on mobile data, some in areas with patchy coverage. The home page has a large hero video, three web font weights and an embedded map. The developer makes the video tap-to-play for everyone, then adds a Save-Data layer: when the header is on, the server sends smaller gallery images, uses system fonts and replaces the map embed with a "Get directions" link. Responses include Vary: Save-Data, and the CDN is checked to keep both versions separate.
FAQ
Will this affect my search rankings?
The hint is about what visitors receive. Keep the same content and links in both versions so search engines and visitors see the same page.
Should I show a message saying "lite version"?
Optional. A small note with a link to load full images can help people who want to see your gallery.
Can I tell how many visitors use data saver?
You can log the header on your server if your privacy notice covers it. Treat any numbers as your own observations.
Is Save-Data the same as slow connection detection?
No. It's the visitor's stated preference, while speed hints describe the network. Respect the preference even on a fast connection.
If you'd like your site to load lightly for customers on limited data, tell us which pages matter most.