Zoom Gallery for E-Commerce: Image Optimization & Conversion

With 5+ years of e-commerce development experience and 50+ successful gallery projects, we deliver high-conversion product galleries. Users leave a page if they cannot inspect product details. A one-second delay in loading the first image reduces conversion by 20% — this is confirmed by research. An image gallery is not just a set of pictures but a complex engineering component: managing large files, zoom without loss of sharpness, touchscreen adaptation, and Core Web Vitals optimization. We develop such solutions for e-commerce, using React 18, Next.js 14, Vue 3, or vanilla HTML/CSS/JS. Our company has 5+ years of experience and has completed 50+ gallery projects for e-commerce stores. Our image processing pipeline reduces content delivery cost by 40% (saving $500/month on average) and increases load speed. Certified developers guarantee compliance with Core Web Vitals. We develop high-conversion product image galleries with hover zoom, pinch-to-zoom, and lightbox, all optimized for Core Web Vitals. Get a consultation on your gallery by contacting us.

Why Zoom Affects Conversion

Users expect to see details: fabric, stitching, texture. Without zoom, they go to competitors. According to Baymard Institute, high-quality images boost conversion by 30%. We implement three types of zoom: hover-zoom for desktop (shows enlarged area on hover), pinch-to-zoom for mobile (two-finger gesture), and lightbox for full-screen view. Each mechanism is adapted to the device and does not conflict with navigation.

Preparing Images for Maximum Performance

The store should store the image at maximum resolution (2000–4000px on the long side) and serve the appropriate size for the context. Serving the original 5MB file on every page is a grave mistake. The processing pipeline on new image upload:

Upload original → S3 (originals/, private)
  ↓ Worker (libvips)
Generate variants:
  - thumbnail: 100×100, JPEG 80%, for thumbnails
  - small: 400×400, JPEG 85%, for product list
  - medium: 800×800, JPEG 90%, for main gallery slot
  - large: 1600×1600, JPEG 95%, for zoom
  - webp: each variant in WebP (typically 30-50% smaller than JPEG)
  ↓
CDN (public bucket or Cloudflare Images)

libvips is 4–8 times faster than ImageMagick and consumes significantly less memory when processing large images. For PHP — intervention/image with libvips driver, for Node.js — sharp.

Modern <picture> with WebP:

<picture>
  <source srcset="product-800.webp" type="image/webp">
  <img src="product-800.jpg" alt="product image gallery — Nike Air Max 90"
       width="800" height="800" loading="lazy">
</picture>

We recommend using WebP for all copies — this reduces traffic by 30–50%.

Gallery Component Structure

Typical product card layout: main slot (large image) + thumbnail strip below or to the left. On desktop — horizontal or vertical strip; on mobile — swipe on the main slot.

function ProductGallery({ images, activeVariantImages }: Props) {
  const [activeIndex, setActiveIndex] = useState(0);
  const [isZoomed, setIsZoomed] = useState(false);

  // On variant change — reset to first variant image
  useEffect(() => {
    setActiveIndex(0);
  }, [activeVariantImages]);

  const allImages = [...activeVariantImages, ...images.filter(
    img => !activeVariantImages.find(v => v.id === img.id)
  )];

  return (
    <div className="gallery">
      <MainSlot
        image={allImages[activeIndex]}
        onZoom={() => setIsZoomed(true)}
        isZoomed={isZoomed}
      />
      <Thumbnails
        images={allImages}
        activeIndex={activeIndex}
        onSelect={setActiveIndex}
      />
      {isZoomed && (
        <LightboxOverlay
          images={allImages}
          startIndex={activeIndex}
          onClose={() => setIsZoomed(false)}
        />
      )}
    </div>
  );
}

Implementing Zoom

Hover Zoom

Classic desktop pattern: when hovering over the image, a magnified area appears next to (or over) the cursor. Implementation technique:

function useHoverZoom(containerRef: RefObject<HTMLDivElement>, scale = 2.5) {
  const [position, setPosition] = useState({ x: 0, y: 0 });
  const [isHovering, setIsHovering] = useState(false);

  const handleMouseMove = (e: MouseEvent) => {
    const rect = containerRef.current!.getBoundingClientRect();
    const x = ((e.clientX - rect.left) / rect.width) * 100;
    const y = ((e.clientY - rect.top) / rect.height) * 100;
    setPosition({ x, y });
  };

  return { position, isHovering, handlers: { onMouseMove: handleMouseMove, ... } };
}

Display zoom via CSS transform: scale() with transform-origin at the cursor point. The zoom image should be 2–3 times larger than the container — otherwise the zoom will be blurry.

Pinch-to-Zoom for Mobile

On touchscreens, hover zoom does not work. Pinch-to-zoom and/or double-tap to zoom are needed.

React-zoom-pan-pinch is a library for this. It supports pinch, double tap, wheel zoom, panning:

import { TransformWrapper, TransformComponent } from 'react-zoom-pan-pinch';

<TransformWrapper
  minScale={1}
  maxScale={4}
  doubleClick={{ mode: 'zoomIn' }}
>
  <TransformComponent>
    <img src={largeImageUrl} alt={alt} />
  </TransformComponent>
</TransformWrapper>

Important: when zoom is active, horizontal swipe to change images must be disabled — otherwise gesture conflicts occur. Switch mode: while scale > 1 — only pan; when scale === 1 — allow swipe.

Lightbox / Full-Screen View

On image click (desktop) or "Full Screen" button — open a modal/lightbox displaying the image full-screen. Requirements:

• Close with Escape and click outside
• Keyboard arrow navigation (Left/Right)
• Swipe on mobile
• Thumbnail bar at the bottom
• URL does not change (or hash: #image-3)

For lightbox we use PhotoSwipe (5kb gzip, excellent mobile support). PhotoSwipe natively works with touch events and has progressive loading (shows thumb while large image loads).

Load Optimization and Content

Sequential Image Loading

Do not load all gallery images at once — it slows down LCP. Strategy:

1. First image — loading="eager", fetchpriority="high", preload in <head>
2. Thumbnails — small files, load all at once (they are tiny)
3. Remaining large images — loading="lazy" or load only when switching to that thumbnail

When navigating to image N — prefetch N+1 and N-1 (neighbor prefetch).

Supporting Video in the Gallery

Many stores add video reviews directly into the gallery — between images. The video thumbnail is a freeze-frame with a play icon on top. On selection, the video loads lazily (<video preload="none">).

Formats: MP4/H.264 (maximum compatibility) + WebM/VP9 (smaller size). Autoplay only muted, otherwise the browser will block it.

Images by Variants

Each product variant (color) has its own set of images. When selecting a variant:

• The gallery switches to that variant's images
• Smooth transition animation (crossfade or slide)
• The selected variant's thumbnail is highlighted

In DB: product_images (id, product_id, variant_id, url, sort_order). When variant_id IS NULL — common images shown for all variants.

What's Included

1. Analysis of current images and recommendations for shooting
2. Development of thumbnail generation pipeline (libvips + S3 + CDN)
3. Creation of gallery component with zoom and lightbox
4. Configuration of lazy load, preload, and Core Web Vitals
5. Integration with CMS (WordPress, Shopify, Laravel) and product variants
6. Testing on real devices (iPhone, Android, different browsers)
7. Documentation and post-launch support

Timelines and Pricing

Pricing starts at $1,500 for a basic gallery and scales with complexity. Contact us for a project assessment — we will prepare a commercial proposal considering your stack and requirements.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.