Jotform form not loading: check the embed

A form embed tells the visitor's browser to fetch the form before anything appears. The browser has to allow that request, and your page has to let the embed script run. Three things stop it. A consent banner can hold third-party scripts until the visitor accepts, so a visitor who declines sees an empty box. A page builder can strip script tags from pasted code and keep only the placeholder. And a request can be refused when the page loads over a secure connection but the embed asks for an insecure address. The box stays empty while the rest of the page looks finished.

• Open the page in a private window, open the console, and reload. Look for a blocked or refused request to the form host.
• Check the network list for a request to the form's address. No request means the script never ran.
• Decline the consent banner in a second window and see whether the form appears. Then accept and compare.
• Open the embed code in your page editor. If it is cut off or shows as plain text, the page builder changed it.
• Confirm the form is published and open, and that the address in the embed matches the form you edit.

The stranger sees the heading and the text around the form, then a gap. Sometimes a loading circle turns and stops, and sometimes nothing moves at all. On a phone the gap sits between the class times and the footer, so it looks like a section the studio forgot to fill. A visitor who does not see a form assumes the business has stopped taking bookings, and leaves. The owner who checks the form in the editor may see it working, since the editor is not the live page.

A consent banner is easy to overlook as a cause. Some banners hold third-party scripts until the visitor accepts, and the embed is a third-party script. A visitor who declines sees the same empty gap you would see if the code were broken. Test once with the banner declined and once accepted, in private windows, and compare. If only the declined run is empty, the banner is holding the form back, and the fix belongs in how the banner loads scripts.

A page builder causes the other break. Some builders strip script tags from pasted code, or keep the placeholder while dropping the script. The console and the network list tell the two apart: a stripped script leaves no request at all, while a blocked one shows a request the browser refused. Check the network list on a fresh load, not after a refresh that may reuse what the browser already holds.

The simulated visitor opens the page as a stranger, waits for the form to appear, and scrolls to the place it should sit. If the form draws, the run records that and moves on. If it does not, the report gives the step, a screenshot of the empty gap, and any console error or refused request recorded on that step. The run records whatever banner state the visitor's browser meets, so an empty result can point at the banner as well as the code.

A form that loads today can go blank after a theme update, a new consent tool or a change in how the page builder stores pasted code. After each of those changes, load the page in a private window with the banner declined, and run the simulated visitors again before a campaign sends traffic to the page.