Skip to main content

​
How the widget loads

The Molin AI widget is designed to load after all other content on your page has finished loading. This is intentional — your product pages, images, and core shopping experience always take priority.
The widget waits for the browser’s load event, then starts initializing after a short extra delay. This means it will not appear until all images, stylesheets, fonts, and other resources have finished downloading.

​
Why it works this way

  • Your store comes first. Customers are there to browse and buy — the chat widget should never slow that down.
  • Better Core Web Vitals. By deferring widget initialization, your Largest Contentful Paint (LCP) and other performance metrics stay unaffected.
  • No layout shifts. The widget appears smoothly after the page is fully rendered, avoiding unexpected jumps in your layout.

​
What this means in practice

On fast websites, the widget appears almost instantly after the page loads. On websites with many large images or slow third-party scripts, the widget may take longer to appear because it waits for everything else to finish first.
If your website has resources that take a long time to load (large unoptimized images, slow third-party scripts, etc.), the widget will also be delayed. Optimizing your site’s overall load time will make the widget appear faster too.

​
Troubleshooting

If the widget takes too long to appear:
  1. Check your page load time. Open your browser’s DevTools, go to the Network tab, and look at the total load time. The widget will not initialize until this completes.
  2. Look for slow resources. Sort network requests by duration to find bottlenecks — large images and slow third-party scripts are common culprits.
  3. Optimize slow assets. Compress images, lazy-load below-the-fold content, and defer non-essential scripts to speed up the overall page load.