How do I optimise product images for a fast D2C store?
How D2C brands can make product images load fast without losing quality: formats, sizes, lazy loading, CDN delivery and an image workflow your team can follow.
Anadoris Digital · · 4 min read

Product images sell D2C products, and they are usually the heaviest thing on a page. Large, uncompressed photos are one of the most common reasons a store feels slow on a phone, particularly on mobile data outside big cities. Slow pages cost conversions and can weaken your search performance through Core Web Vitals.
Fixing images is one of the most rewarding speed improvements, because it is mostly about process: how photos are exported, uploaded and served. It does not require a redesign or a new platform, and the gains apply to every page, email and ad that uses the same files.
What Shopify already does
Shopify's CDN can automatically serve images in modern formats and at requested sizes, provided your theme asks for appropriate sizes. Modern themes use responsive image tags that request different widths for different screens. If your theme is older or heavily customised, check whether it requests full-size images everywhere. A quick way is to open a collection page on your phone's browser, or use the network panel in a desktop browser, and look at the size of the image files being downloaded. Apps and custom sections sometimes bypass the theme's image handling and load originals.
Set rules for the original files
- Export product photos at a sensible maximum width for zoom, not straight from the camera.
- Use JPEG or WebP for photos and PNG or SVG only for graphics that need transparency or sharp lines.
- Compress before upload with a tool such as Squoosh, ImageOptim or your design software's export settings.
- Name files descriptively, such as rose-face-serum-30ml.jpg, for search and accessibility.
- Write alt text that describes the product for screen readers and search engines.
- Keep a master folder of full-resolution originals outside the store.
Serving images from your own AWS setup
If you run a headless storefront or serve images from S3, you need to handle resizing yourself. Store originals in a private S3 bucket, put CloudFront in front, and use an image processing layer to create sizes and formats on request, caching the results. AWS publishes a Dynamic Image Transformation solution for this pattern. Alternatively, frameworks such as Next.js include image optimisation, and services such as Cloudinary or imgix offer it as a product.
- Serve several widths and let the browser pick with srcset and sizes attributes.
- Prefer WebP or AVIF with a fallback for older browsers.
- Cache processed images at the CDN for a long time.
- Set width and height attributes so the layout does not jump as images load.
Load images in the right order
The first large image a shopper sees, usually the hero banner or the main product photo, should load as early as possible, without lazy loading, and can be preloaded. Images further down the page, such as related products, reviews with photos and lifestyle galleries, should be lazy loaded so they download only as the shopper scrolls. Getting this order right often improves Largest Contentful Paint, one of Google's Core Web Vitals. Keep an eye on Cumulative Layout Shift too: images without set dimensions make text jump as they load, which frustrates shoppers who are trying to tap a button and is another signal Google measures.
Video and banners
Autoplay hero videos and large animated banners are heavy. Use a poster image, compress video properly, and consider showing a static image on mobile. Animated GIFs are especially large; a short muted video file is usually much smaller for the same effect. For banners, avoid text baked into images where you can. Real text in HTML loads faster, stays sharp on every screen, can be translated and is readable by search engines and screen readers. It also lets you change an offer without re-exporting artwork.
A simple image workflow for your team
Image quality problems usually start with process rather than technology. Write a one-page guide for whoever shoots, edits or uploads photos: the export size, format and compression level, the file naming pattern, alt text rules and where originals are stored. Share it with agencies and freelancers too, so every new product launch follows the same standard.
Then check a few new uploads each month. It takes minutes and catches the occasional huge file before it spreads across collection pages, emails and ads. If you use a digital asset management tool or a shared drive, keep originals and web-ready versions in clearly separate folders so the wrong file is not uploaded by mistake.
Where to start
Run your home page and best-selling product page through Google PageSpeed Insights on mobile and note what it says about images. Then agree an export standard with whoever produces your photos and re-upload the worst offenders. If you host images yourself, put CloudFront and an image resizing layer in front of them. Recheck the same pages afterwards to confirm the improvement, and repeat the check after every major theme or app change.
Related service: AWS & Cloud Management · More on this topic: AWS & Cloud Management articles
