What could be the reason for the "A problem repeatedly occurred on..." message appearing when trying to open a recently published website on certain iPhones (iPhone 11 pro and iPhone 12)?

When you see the "A problem repeatedly occurred on..." message on certain iPhones when accessing a published Webflow site, it usually points to serious browser-rendering or script execution issues.

Here’s how to systematically troubleshoot it:

1. Heavy Animations and Page Load Crashes

• Too many complex animations, interactions, or page load animations can overwhelm mobile Safari (especially on older devices like iPhone 11 Pro).
• Excessive use of lottie animations, complex GSAP integrations, or multiple scroll-triggered interactions often causes crashes.

2. Incorrect Video Embeds or Media Handling

• Embedding large background videos, auto-playing videos, or iframes without mobile optimization can trigger Safari crashes.
• Optimize all videos by enabling attributes like playsinline and ensuring files are compressed.

3. Oversized DOM (Too Many Elements)

• If your page has too many nested divs, sections, CMS items, buttons, etc., the DOM size can get extremely large, exhausting memory limits on mobile Safari.
• Simplify your page structure and remove unnecessary elements.

4. GDPR Scripts or Third-Party Code Issues

• Third-party scripts like cookie banners, chatbot embeds, live chat widgets, or analytics tools could be injecting buggy code on load.
• Temporarily disable external scripts in the Webflow Custom Code settings to check if the problem goes away.

5. CSS or JS Errors

• If you have custom CSS/JavaScript inside Before or Inside in Webflow, syntax errors (like missing braces, typo in scripts) can crash mobile Safari silently.
• Validate your custom code with online validators.

6. Memory Management in Safari

• Sometimes, large background images or heavy fonts (loading many weights/variants) can trip memory limits.
• Compress images, use only essential font weights, and leverage Webflow’s responsive images automatically.

7. iOS-Specific Bugs

• Certain iOS versions have known rendering bugs, especially iOS 14 and early iOS 15 builds.
• Ask users to update Safari/iOS (if possible) and see if it resolves — but you should still fix root causes on your website.

Summary

The "A problem repeatedly occurred on..." message usually happens when heavy animations, scripts, large DOMs, or third-party embeds break mobile Safari’s memory or rendering capabilities. To solve it, audit the page structure, disable external scripts temporarily, optimize assets, and clean up complex animations. Always check the Console tab in Safari’s DevTools for hidden errors causing the issue.