Skip to main content

Image optimizer

How to use it​

  1. Run the optimizer across your existing product images. (Products → Image optimizer)
  2. It compresses, converts to WebP, and adds mobile srcset automatically.
  3. Revert within 30 days if anything looks off.

⏱ One pass · 💳 Starter+ · 🎯 Faster pages, lower mobile bounce

Why this matters for your business​

Image weight is the #1 cause of slow Shopify storefronts. The average product page has 5-15 images, often unoptimized (uploaded straight from camera or designer at 4-8MB each). Result: 3-10 second page loads on mobile, 30-50% mobile bounce rate, lost conversions.

The image optimizer fixes this in bulk. Existing product images compressed (preserving visual quality), converted to WebP (50%+ smaller than JPEG), responsive srcset generated (mobile gets smaller variants). Page-load time drops; bounce rate drops; conversion rises.

What this typically unlocks​

OutcomeResult
Page-load time−30 to −60% typical
Image weight per page−65 to −80%
Mobile bounce rate−10 to −20%
Mobile Lighthouse score+20-40 points
Time to optimize 1000 images30 min vs. weeks

What you actually get​

CapabilityDescription
Bulk compressionLossy or lossless; configurable quality
WebP conversionAuto-served to supporting browsers; JPEG fallback
Responsive srcsetAuto-generate 320/640/1024/2048 variants
Format optimizationPNG → WebP, JPEG → WebP, AVIF for newer browsers
Lazy-loading hintsBelow-fold images deferred
30-day revertUndo any optimization within 30 days

How it works​

Real merchant scenarios​

Scenario A — Brand drops mobile load time 4.2s​

Setup. Brand had 2,400 images averaging 1.8MB each. Mobile PDP load: 5.2s. Mobile bounce rate: 47%.

With optimizer: Bulk-optimize all images. Done in 35 min.

60-day result:

  • Mobile PDP load: 1.0s (−4.2s)
  • Mobile bounce rate: 47% → 28%
  • Mobile conversion: +24%
  • Lighthouse score: 38 → 78

Scenario B — Page weight massively reduced​

Setup. Average PDP was 12MB total (mostly images).

Post-optimization: Average 2.8MB (−77%).

For mobile users on 4G, that's the difference between page loading instantly vs. 6-second wait.

Scenario C — Revert saves a wrong-format issue​

Setup. Brand optimized; later discovered some images had been over-compressed (visible quality loss on hero shots).

With revert: Selected affected images → revert. Originals restored within seconds.

Without revert: Would have required re-uploading from backups (or designer's original files if accessible).

Best practices​

✅ Use lossy with quality 85 as default. Imperceptible loss, significant size reduction.

✅ Keep WebP enabled. Browsers that support it (95%+) get smaller files; others get JPEG fallback.

✅ Use responsive srcset. Mobile customers don't need 2048px images; serving them is wasted bandwidth.

❌ Don't compress hero images aggressively. Visible quality matters more than KB saved.

❌ Don't skip the 30-day revert window. Free safety net.

Plan tiers​

CapabilityFreeStarterProAgencyEnterprise
Bulk compression✓ (50/mo)✓✓✓✓
WebP conversion✓✓✓✓✓
Responsive srcset✓✓✓✓✓
AVIF (newer format)——✓✓✓
Lazy-loading hints✓✓✓✓✓
30-day revert✓✓✓✓✓
Custom quality settings——✓✓✓
Multi-shop optimization———✓✓

See also​