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

The widget and your Core Web Vitals

Why Idukki is built to stay out of CWV, and what to check on your own theme if scores dip.

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

Idukki is designed not to damage Core Web Vitals: it reserves layout space, lazy-loads media and mounts interactivity only when it scrolls into view. If your scores dip after adding a widget, the cause is usually in how it’s placed on the theme.

How the widget protects CWV

  • It renders an empty container at the right aspect ratio first, so it doesn’t shift layout (low CLS).
  • Tile interactivity mounts on scroll-in, not on page load, so first interaction stays responsive (low INP).
  • Images are served as modern formats first, with older formats only as a fallback.

What to check on your theme

  • Reserve space for the widget in CSS; don’t let it inject into a zero-height container.
  • Load the script with defer, not async after a render-blocking script.
  • Don’t place a third-party tag that mutates the DOM right next to 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)