I am experiencing a complicated technical issue on my Culver menu website where Typeform is used for collecting user input, feedback, and custom menu-related selections, and I am hoping someone in the Typeform community can provide guidance. The website itself is designed to display a complete Culver-style menu with multiple categories such as burgers, sides, drinks, and desserts, along with dynamic pricing, images, and availability indicators. Typeforms are embedded at several points on the site, including feedback popups, special order requests, and contact forms, but their behavior has become inconsistent and unreliable across different devices and traffic sources.
One of the main problems I am encountering is that embedded Typeforms do not always load or render correctly. In some cases, the form container appears but remains blank or stuck on a loading spinner, while in other cases the form loads partially but buttons are unresponsive or questions fail to advance. This issue seems to occur more frequently when users navigate quickly between menu categories or when the form is triggered dynamically (for example, clicking “Request Custom Order” from a menu item). Refreshing the page sometimes resolves the issue, but that is not a practical solution for real users.
Another serious concern is inconsistent form submission and data capture. Some users report that they complete and submit the Typeform successfully, but the responses never appear in the Typeform dashboard or connected integrations. In other situations, duplicate or incomplete submissions are recorded, which makes it difficult to trust the collected data. Since these forms are tied to menu-related actions and customer inquiries, missing or corrupted submissions directly impact user experience and business operations.
From a technical perspective, the Culver menu website relies heavily on JavaScript for dynamic rendering, lazy loading of menu items, and modal-based UI interactions. Typeform is embedded using both standard embed scripts and popover/slider embeds, depending on the use case. I suspect there may be conflicts between the site’s JavaScript lifecycle and Typeform’s embed initialization, especially when DOM elements are created or destroyed dynamically. Additionally, content security policies (CSP), iframe restrictions, or ad/script blockers could be interfering with how Typeform loads within the menu pages.
I am also questioning whether performance optimizations on the site are contributing to the issue. The website uses caching, deferred script loading, and performance plugins to improve load times, but these optimizations may be delaying or blocking Typeform scripts under certain conditions. On slower connections or mobile devices, the timing differences become more noticeable, and Typeform failures appear more frequently. Unfortunately, browser console errors are inconsistent and hard to reproduce reliably.
I would really appreciate any insights from the Typeform community on best practices for embedding forms in dynamic, JavaScript-heavy websites like this Culver menu site. Has anyone faced similar issues with forms failing to load, submit, or record data correctly? Any recommendations on embed methods, script loading order, performance settings, or debugging steps to ensure reliable Typeform behavior would be extremely helpful in resolving these problems. Very sorry for long post!
