Making Try-On Work for Shoppers on Slow Connections

To make try-on work for shoppers on slow connections, make sure the product page loads fully without it, load the try-on script late, and tell shoppers what to expect while a photo uploads. The goal is that a slow connection delays the preview, never the purchase.

A virtual fitting room for a clothing website involves a photo upload and a generated image, so it is heavier than a normal product page. This guide covers what you control as a store owner.

Why does try-on feel slow on a weak connection?

Two things travel over the network. The shopper's photo goes up, and the result image comes back. On a weak mobile connection both can take a while.

The store also loads a script on the page. If that script blocks the page, the whole product page feels slow, not just the try-on.

Phone cameras produce large files, so a photo upload is usually the longest step. That is the part to plan around.

How should you load the try-on script?

Load it so it never holds up the page. The ZeDaq.ai widget script tag uses defer, which tells the browser to fetch it in the background and run it after the page is ready:

<script src="https://www.zedaq.ai/widget/zedaq.js" data-key="…" defer>

Setup details are in the widget documentation. Keep your key locked to your domain in the dashboard.

General habits also help any script:

• Place it once, in the product template only, not on every page.
• Avoid stacking several widgets that all load on the same page.
• Compress your product images, since they are most of the page weight.

What should the shopper see while they wait?

Waiting is easier when the shopper knows what is happening. Plain messages beat spinners alone.

• Say that the upload can take a moment on a slow connection.
• Show that the page is working, for example with a clear "Creating your preview" message.
• Let the shopper keep browsing sizes, photos and the description meanwhile.

Because a try-on image is a preview and not an exact fit guarantee, say so near the button. Our article on showing that try-on results are previews gives wording you can reuse.

How can shoppers help themselves?

You cannot fix a shopper's signal, but a short tip near the button can improve their odds:

1. Use Wi-Fi if you have it.
2. Take one clear, full-length photo and avoid sending many.
3. Stand in good light so the first photo works and no retry is needed.
4. Do not close the page until the result appears.

Retries are the hidden cost on slow networks, because each failed upload starts again. A clear photo guide saves more time than any other tip.

Simple, large instructions also help shoppers who are less used to apps, as covered in designing try-on for older shoppers.

Should the page work without try-on?

Yes. Always. Many shoppers on slow or expensive data will skip the feature, and they still need to buy.

That means a good size chart, clear measurements and honest fit notes next to the button. Size guidance that does not need an upload helps everyone, and our guide to size guides that reduce returns shows how to write one.

Treat try-on as an extra, not a gate. If it fails, the shopper should still be able to choose a size and check out.

What if an upload fails halfway?

Plan for failure, because it will happen on weak signals. The shopper should see a plain message and a clear way to try again, not a blank space.

Good failure messages share three traits:

• They say what happened, such as "The upload did not finish."
• They tell the shopper what to do, such as "Check your connection and try again."
• They never block the rest of the page.

Test this on purpose by switching your phone to airplane mode during an upload. If the product page still works afterward, your fallback is doing its job. Also check that the size chart and add-to-cart button stay in reach while the message is on screen.

How do you test on a slow connection?

Test the way a shopper would, not on your office Wi-Fi.

• Use your browser's developer tools to throttle the network to a slow mobile setting.
• Try a real phone on mobile data in a weak-signal spot.
• Time how long the product page takes to become usable, with and without the script.

Fix the page first, then the upload experience. The live demo lets you see the shopper side before you install anything.

FAQs

Does try-on slow down my product page?

It can if a script blocks loading. Use a deferred script, add it only to product templates and test the page with and without it.

Can shoppers use try-on on 3G?

It may work but take longer, mostly because of the photo upload. Make sure the product page works without it and tell shoppers what to expect.

Should I hide try-on for slow connections?

You do not need to. Keep the button optional, set expectations and let shoppers skip it and buy normally.

What is the biggest cause of failed uploads?

Large photos on weak signals, followed by closing the page too early. A short instruction near the button prevents most of this.