QAlaunch

Website not working on iPhone Safari but works in Chrome

When a site fails on iPhone Safari but works in Chrome on desktop and Android, the most common cause is JavaScript that uses a feature older Safari versions do not support, which throws an error and stops every script on the page. Other causes are Safari’s tracking prevention blocking third-party scripts or cookies, an invisible layer over buttons on iOS, and menus that rely on hover. Connect an iPhone to a Mac and use Safari’s Web Inspector to read the first error.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

On iPhones a button does nothing, a form will not submit, a menu will not open, or the page loads forever. The same page works in desktop Chrome and on Android phones. It may affect only some iPhones, typically those that have not updated iOS in a while.

Why it happens

1. Code older Safari cannot parse

Safari often adopts new JavaScript features later than Chrome. Regex lookbehind, for example, was only supported from Safari 16.4. A script using such a feature fails to parse on older iPhones and everything in that file stops.

2. Tracking prevention blocks a dependency

Safari limits third-party cookies and storage. Embedded checkouts, chat widgets, login iframes or scripts that expect those cookies can fail silently on iPhones only.

3. An invisible layer on iOS

Differences in how iOS treats 100vh, fixed positioning and the address bar can leave an overlay or fixed footer covering buttons on iPhone screen sizes.

4. Hover-only or non-button controls

Menus that open on hover, and click handlers attached to plain divs or spans, can fail to respond to taps on iOS. Real button and link elements behave far more reliably.

How to fix it

  1. Test in real Safari. On an iPhone, enable Settings > Safari > Advanced > Web Inspector, connect it to a Mac and open Safari’s Develop menu to see the page’s console. Without an iPhone, Safari on a Mac with Responsive Design Mode catches many, but not all, issues.
  2. Find the first SyntaxError or TypeError in the console. Look up the feature it mentions on caniuse.com and compare it with the iOS versions your visitors use.
  3. If you control the build, set your browser targets to include older Safari versions so the code is transpiled or polyfilled. If the error comes from a theme or plugin, report it to the vendor with the console message.
  4. For third-party widgets, test with Settings > Safari > Prevent Cross-Site Tracking on and off to see whether tracking prevention is involved, then use the vendor’s first-party or Safari-compatible option.
  5. Replace clickable divs with real button and a elements, and make menus open on tap rather than hover.
  6. Inspect the page at iPhone sizes for fixed or full-height layers that cover the content you are tapping.

How to check it's fixed

  • On an iPhone on the current iOS and, ideally, one a version or two behind, tap every main button, open the menu and submit each form.
  • Keep Web Inspector connected and confirm the console stays clear of errors while you do.

What a QAlaunch scan shows for this

  • QAlaunch’s scan runs in Chromium at phone width, so it catches layout, overlap, console and link problems that also affect iPhones, but not bugs that exist only in Safari’s WebKit engine.
  • Phone-width screenshots with a visual review for overlapping elements and cramped tap targets.
  • JavaScript errors and failed requests that occur in Chromium too.
  • Safari-only failures need hands-on testing on a real iPhone, which is what the $299 manual test is for.

See exactly what a full report contains in the sample report.

Frequently asked questions

Why does Chrome on my iPhone fail too?

Every browser on iOS has historically used Apple’s WebKit engine underneath, so Chrome on an iPhone usually behaves like Safari. That is a quick way to confirm the problem is the engine, not the browser.

Can I test Safari without an iPhone?

Safari on a Mac shares the same engine and catches many problems. Cloud device services can also run real iPhones remotely. Chrome’s device mode only changes the size, not the engine.

Do I need to support old iOS versions?

Check your analytics for the iOS versions visitors actually use. Many people keep older iPhones that cannot update to the latest iOS, so one or two versions back is a reasonable baseline.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Any website: all Any website fixes · why sites break on mobile · why contact forms fail silently

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Meteor forums: site works in Chrome and Edge but fails in Safari · Shufflehound support: WooCommerce checkout button not working on iPhones · Bubble forum: buttons work on desktop but not mobile