If Lighthouse or an audit tool says your embed failed but the page works when you open it, the tool was probably blocked, not the embed. Speed tools and test scripts run headless Chrome, and bot protection such as Cloudflare in front of the third-party service can answer them with a 403. Check the status code before you change anything.
I found this one on my own site. My tests reported a broken booking calendar with total confidence. The calendar disagreed.
What actually happened?
The "Book a call" page on zolodigital.com embeds my Cal.com calendar. It's a plain iframe, no Cal.com script, so nothing third-party loads on any other page of the site:
<iframe src={calSrc} title={book.heading} loading="lazy" className="h-[720px] w-full rounded-2xl border" />
My page checks, a script that opens the site's pages in headless Chromium and lists failed requests, flagged the calendar. Lighthouse reported the same failed request.
Then I opened the page in a normal browser, at desktop width and at phone width. The calendar was there both times. On the phone it took its time to paint, but it painted.
The reason: Cal.com sits behind Cloudflare, and Cloudflare answers headless Chromium and curl with a 403. Lighthouse runs headless Chrome. My script runs headless Chromium. So the bot was turned away at the door, and then the bot wrote the report.
How do you tell a blocked bot from a broken embed?
Look at the status code, not the word "failed".
- 403 Forbidden on the embed's own URL usually means "I don't serve robots". The embed is very likely fine for people.
- 404 or 5xx means something is actually wrong: a wrong URL, a deleted widget, the service is down.
- Blocked by CORS or a Content Security Policy error in the console is a configuration problem on your side.
From a terminal you can see who answered:
curl -sI "https://cal.com/your-name/30min" | grep -iE "^HTTP|^server|^cf-ray"
A 403 with server: cloudflare and a cf-ray header is Cloudflare's bot protection talking, not the service being broken.
Then do the test that matters: open the page in a regular browser on a laptop, and on a real phone, and use the embed. Book the slot, submit the review, open the chat.
Which Shopify embeds does this happen to?
Any third-party widget can sit behind bot protection: booking calendars, review widgets, chat, quizzes, size finders. And the tools that check your store, speed reports and audit apps, are bots too. So any of those widgets can turn them away.
That's why a "failed request" line in a report is a question, not a verdict. Before you remove a widget or pay for a "fix", check it as a person.
What should you do about it?
Usually nothing to the embed. A few things help, though:
- Note it next to your tests. I wrote the Cal.com 403 into the project notes, so nobody chases it again next month.
- Lazy-load the iframe.
loading="lazy"keeps a heavy embed from competing with the rest of the page for the first paint. - Give people another way in. Under my calendar there's "Prefer to write?" with a WhatsApp link, because a calendar that's slow on a phone loses people who'd happily send a message.
If your store has a report full of red lines and you're not sure which ones are real, that's exactly what a Shopify audit sorts out: what's broken, what's a bot being bounced, and what to fix first.
My calendar is fine, by the way. It just doesn't take meetings with robots.






