Skip to content
NewProduct Q&A: shoppers ask on your product page and get your answers.See how it works
IdukkiIdukki
Troubleshooting

Why Idukki doesn’t hurt your Core Web Vitals

How the widget loads so it keeps layout shift and slow taps down. Plus what to check on your own theme.

5 min read · last updated 2026-11
On this page

Here is how the widget loads, and why it stays out of your page’s way.

Reserved layout

We render an empty container with the right aspect ratio immediately. Images and video lazy-load into it, so the page does not jump.

Lazy mount

Tile interactivity mounts only once the widget enters the viewport. That covers pin to expand, video play and the hotspot drawer.

Right-sized WebP images

Tile images are served as WebP. Each tile offers several widths, and the browser downloads one that fits the tile.

What to check on your theme

  • Reserve space for the widget in your CSS, don’t let it inject into a 0-height container
  • Avoid loading the widget script with `async` after a render-blocking script (defer is fine)
  • Don’t put a third-party tag that mutates the DOM near the widget
Was this page helpful?

Still stuck?

Email us at support@idukki.io or open the in-app chat. We answer within one working day.

Talk to a human

Related guides

Live in minutesDTC + B2B brands79 KB runtimeReal G2 reviews

Stuck?

A real human is faster than a search box.

In-app chat is staffed during EU + US business hours. Status of a ticket? Email support@idukki.io and we’ll surface it.

  • No credit card
  • Cancel anytime
  • GDPR self-certified · SOC 2 (in audit)