Embeds & web forms
Embedded Typeforms hit three subdomains before paint and routinely tank mobile Core Web Vitals on landing pages.
Ce que les utilisateurs disent vraiment
✕Embedding a Typeform on a mobile landing page is reported to drop page performance scores to around 20% — the embed pulls in a chain of external resources that block rendering.
Source : Typeform Community, mobile embed performance ↗✕The embed requires three separate HTTPS connections — embed.typeform.com, form.typeform.com and renderer-assets.typeform.com — each adding latency before the form is interactive.
Source : Typeform Community, embed loading slowly ↗✕WordPress popup embeds are reported to cross 15 seconds of load time, with the workaround being to delay the embed script by 3-5 seconds so the host page can finish painting first.
Source : Typeform Community, popup embed load times ↗
Forms render as native HTML inside your own Next.js page — no iframe, no third-party JS, no cross-origin handshake. First input is interactive on the same paint as the rest of the page, and Lighthouse stays in the 90s on mobile because there's no embed to optimise around.