Skip to main content

How do I determine whether Looksy affects performance?

Compare the same representative product pages before and after enabling Looksy. Repeat the test and use real-user data when enough traffic is available.

Record the test context

  • page and product URL;
  • theme name and version;
  • other enabled apps;
  • device, operating system, and browser;
  • network condition;
  • whether the try-on flow was opened;
  • test date and measurement tool.

Check page loading separately from try-on processing

The initial product-page experience and the interactive try-on flow are different performance surfaces. Measure both:
  • LCP, INP, and CLS;
  • transferred data and request count;
  • JavaScript long tasks and errors;
  • time until the page is usable;
  • time and failure rate through the try-on flow;
  • layout movement or blocked controls.

How do I isolate the cause?

  1. Reproduce the issue several times.
  2. Compare the same page and device with Looksy enabled and disabled in a safe test theme.
  3. Check the browser console and network panel for failed or slow requests.
  4. Test another representative product and device.
  5. Review recent theme, app, image, and analytics changes.
Do not disable an app on a live storefront merely to diagnose it. Use an unpublished or development theme when your workflow allows it.

What should I send to support?

Include the recorded context, before-and-after measurements, screenshots or a recording, console errors, and exact reproduction steps. Avoid conclusions based on a single synthetic score.

Store Performance FAQ

Understand what a reliable comparison requires.

Theme Integration

Verify the current storefront setup.