Configure Speed Settings for an eCDN Zone
Optimize zone performance by enabling speed settings such as Early Hints, HTTP/3, and image compression via the Configure Zones interface in Business Manager.
Required Editions
| Available in: B2C Commerce |
Speed settings improve site performance for shoppers. Each setting can have different effects depending on your site's configuration. Test settings individually to measure their impact before enabling them on zones with production traffic. For conceptual background on each feature, see Enhance Site Speed.
- In Business Manager, click the App Launcher, and then select Administration | Sites | Embedded CDN Settings.
- Locate the zone you want to configure and select Configure Zone from the dropdown menu.
-
Select the Speed tab.
Speed tab — Optimization settings and Polish Level
-
(Optional) In the Optimization section, select any of the following settings to improve
site performance:
Speed Setting Action Early Hints Early Hints makes the most of the time while the server prepares a response. With this approach, instructions are sent to the browser to start loading resources while the origin server is busy. By sending these hints before the full response is ready, the browser can figure out how to load the webpage faster for the end user.
To take advantage of 103 Early Hints, enable the
LinkHTTP header in theaddHttpHeadermethod within thedw.system.Response class. Typicallyrel=preloadandrel=preconnectare used with the primary need to supportrel=preload (with as=... values image, style, script) and rel=preconnectLink headers.response.addHttpHeader("Link", "</path/to/resource>; rel=preload; as=image"); response.addHttpHeader("Link", "<https://example.com>; rel=preconnect");For reference see MDN Web Docs - Link.
HTTP/3 HTTP/3 uses QUIC, which is a secure-by-default transport protocol. HTTP/3 improves page load times in a similar way to HTTP/2. However, the QUIC transport protocol solves TCP's head-of-line blocking problem, meaning that performance over lossy networks can be better. HTTP/2 Origin Leverages HTTP/2 protocol between eCDN and the origin, meaning performance can be better between the two. This setting takes effect only when your origin supports HTTP/2. Brotli Using Brotli for serving static text-based web assets (HTML, CSS, JS, JSON) provides better performance, smaller payloads and faster delivery times. This enhancement allows for easier and more intuitive management of compression settings. These speed settings usually improve site performance, but the degree to which they do depends on various unique aspects of the site's configuration. Test each speed setting one at a time to accurately measure the performance improvement of each feature.
-
(Optional) In the Polish Level section, select one of the following options:
Polish Level Option Action Polish Level Off No image modification occurs. Polish Level Basic Image file size is reduced without impacting visual quality. This option removes metadata for PNG, GIF, and JPEG files. It also results in lossless compression of PNG and GIF files. Polish Level Basic+JPEG In addition to the actions for the basic level, file size of JPEG images is reduced using lossy compression, which can reduce visual quality. Large JPEG images are converted to progressive images (site visitors see an increasingly detailed image as the file is downloaded). This functionality is applied only to images served through the eCDN. Images retrieved from third-party sites are not modified. The Polish Level applies to all images served from hostnames within the zone. It isn't possible to use different Polish Levels for different images or a device type-specific Polish Level. Test a new Polish Level with a zone without production traffic before enabling it for a zone with production traffic.
-
(Optional) In the Polish Level section, select WebP to enable
WebP image support.
The eCDN supports the
WebPimage format for added performance benefits with supported clients.If you choose Polish Level Basic (GIF, PNG):
- WebP is rarely beneficial in this mode because WebP is only adequate for PNG images and can't improve compression for JPEG images.
If you choose Polish Level Basic + JPEG:
- Although WebP compresses better than JPEG on average, there are exceptions. eCDN detects these cases and retains the JPEG format when JPEG compresses better.
- eCDN does not convert from JPEG to WebP when the conversion makes the file bigger or reduces image quality by more than it saves in file size.
- Large JPEG images are converted to progressive images. Shoppers see an increasingly detailed image as the file is downloaded.
Note WebP requires Polish Level set to Basic or Basic+JPEG.
- Enhance Site Speed
Want your customers to love their online shopping experience? Speed up your web store. These speed optimization features help your storefront load faster, so customers spend less time waiting and more time browsing.

