Products / Content & Delivery / Pixel
Pixel optimizes your product images, prepares 12 variants, and delivers the right version for each device and browser through the ZAZ CDN.
| Image | Resolution | Delivered | Status |
|---|---|---|---|
| urun-01-siyah-ayakkabi.jpg | 2400 × 2400 | 236 KB · AVIF | Healthy |
| urun-02-mavi-elbise.jpg | 1800 × 2400 | 198 KB · AVIF | Healthy |
| kategori-banner.png | 640 × 320 | 41 KB · WebP | Low resolution |
| urun-04-canta.jpg | 2000 × 2000 | 174 KB · AVIF | Healthy |
Don’t estimate the gain, see it: savings and traffic served from the network are measured per site in the panel.
Every visitor receives a smaller image that fits their screen, so product pages open faster.
Most traffic now comes from mobile. Phones don’t receive desktop-sized images, so mobile data isn’t wasted.
Images are served from the ZAZ network, taking most of your image traffic off your origin server.
Smaller files delivered from the ZAZ network reduce your bandwidth consumption.
Pixel automatically selects the right version for the visitor’s screen and browser.
Version sent to the visitor
Illustrative examplePixel connects to your site, optimizes and hosts your product images, and delivers the right version to each visitor.
Pixel integrates with your site without requiring you to rebuild each product template.
Pixel prepares 12 versions of each image in multiple sizes and formats and stores them on ZAZ.
Pixel picks the image by the size it is displayed at, screen density (DPR) and browser support, and delivers it through the ZAZ CDN.
If an image is unavailable through Pixel, visitors keep receiving it from your original source.
Test Pixel on your live site before enabling it for visitors. In tester mode Pixel runs only in your own browser session, while regular visitors keep the existing experience.
Pixel test mode
Pixel active
Visible only in this browser session
Pixel surfaces low-resolution images, broken assets, traffic savings and site-level CrUX data in one dashboard.
Find undersized images together with their product links.
See image URLs returning 404 responses and retry them.
Track real-user Chrome data (CrUX) for LCP, CLS and INP across your whole site.
See traffic savings, optimization results and an estimated CO₂ reduction in a monthly report.
The Pixel Test Tool analyzes your site and highlights mobile image usage, modern format adoption, and potential optimization opportunities.
| Modern format usage | 48% |
| Image data sent to mobile | 3.1 MB → 1.3 MB |
| Image saving potential | 1.8 MB |
The standard setup needs no DNS change, and your origin always stays in place.
Enable Pixel through script-based integration without changing your existing DNS configuration.
Pixel works across commerce platforms through its standard integration model, with deeper platform-specific integrations for Ticimax, IdeaSoft and T-Soft.
If an image isn’t available through Pixel, the original source remains available.
Each ZAZ product can be used on its own.
No. In the standard setup Pixel works with a single script added to your site. A DNS-based integration option is also available.
If a version can’t be loaded from ZAZ, the browser falls back to the image on your origin. Your source images stay on your origin.
Yes. Pixel works with every commerce platform through its standard integration model, with deeper platform-specific integrations for Ticimax, IdeaSoft and T-Soft.
Yes. Add ?zaz=on to a page URL to use Pixel in your own browser session while regular visitors keep the existing experience.
Pixel’s script checks whether the visitor’s browser can load AVIF and WebP, and combines this with the displayed image size and screen density (DPR) to request the matching version.
The Site speed page in the panel shows Chrome field data (CrUX) for LCP, CLS and INP at the site level. It reflects your whole site, not Pixel alone.
Pixel stores the optimized versions on ZAZ, in storage separated per domain, and delivers them through the ZAZ CDN. Your origin stays in place.