By platform

HubSpot form not showing up on your page

The page has a heading where the form belongs and nothing under it. Mimiq sends simulated visitors to the same page and shows whether the form appears for them, and the step where it does not.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why is my HubSpot form not showing up on my page?

An embedded HubSpot form is drawn by a script that runs on your page and writes the form into a container element. The form does not appear when that script is blocked, when the page builder strips it or drops the container, when the script runs before the container is on the page, or when a consent setting holds the script back. A simulated visitor opens the page the way a stranger does and shows whether the form draws, with the step, a screenshot and any console error when it does not.

What this looks like in a report

Who
Callum, a procurement lead comparing three warehouse software tools
How they arrived
Clicked a link to the demo page from a professional network post
Where they stopped
Demo request section, below the product screenshots

“There is a heading that says Request a demo, and then nothing under it. Either the page is broken, or they only take demos from big companies. I will go to the next vendor.”

The fix. Place the embed code in a plain part of the page, not inside a tab, accordion or slide. Then open the page in a private window and confirm the form draws without a refresh.

An illustration. Run a test to see your own.See a real sample report

The script finishes before its container is on the page

The embed script looks for a container element with the id you gave it, and writes the form into that element. Some page builders assemble a page in stages, so the script can run before the container exists. When it does, the script has nothing to fill, and the page shows an empty heading. A container inside a closed tab or accordion can also have no height until a visitor opens it. The editor may show no error, because it is not the live page.

  • View the page source and confirm the container element with your embed's id is on the page.
  • Open the console after the page loads and look for a blocked script or an error that names the form.
  • Check the network list for a request to the form script. If none appears, the script was never added.
  • Find the form inside any tab, accordion or slide, and check it appears once the visitor opens it.
  • Decline the consent banner in a private window and see whether the form appears, then accept and compare.

What a buyer sees above an empty space

A buyer who has come for a demo reads the heading and looks for the form. On a laptop the gap is wide and obvious. On a phone it sits between the product screenshots and the footer, and the buyer may not connect the heading with anything. A buyer seldom writes in to say a page is broken. They assume the vendor does not take demo requests from a company their size, or that the form is down, and they move on.

Four places the script and the container drift apart

The first is timing. Builders that load sections as the visitor scrolls, or that assemble the page after the first paint, can place the container after the script has already run. The second is placement. A form inside a tab, a slide or a collapsed accordion can be written into a box with no height until someone opens it. The third is removal. Some builders strip script tags from pasted code, so the container stays and the script is gone.

Consent is the fourth, and easy to miss. A banner that holds third-party scripts until a visitor accepts leaves the same gap for anyone who declines. Test once declined and once accepted, in private windows. If the gap appears only for the declined run, the cause is the banner, not the form, and the fix belongs in how the banner loads scripts.

How the simulated visit finds the form

The simulated visitor loads the page, waits, and scrolls to the spot where the form belongs. If a tab, accordion or slide hides that spot, the visitor opens it, as a stranger would. The report records whether the form appeared, the step where it did not, a screenshot, and any blocked script or console error on that step. It does not read your HubSpot account, so it cannot tell you whether the form is set up to send contacts to your CRM.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A new page layout can move the form into a hidden tab

Page edits move things. A new section, a tab added to the design, or a different page template can place the form container inside a tab, accordion or slide, or leave it off the page. Load the page cold, open every tab, and run the simulated visitors again after each layout change, before the next campaign sends buyers there.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Why does the form show in the editor but not on the live page?

The editor is not the live page. A form can look right there and still fail on the public address, because the page around it loads differently for a visitor. Check the live address in a private window instead.

Will a refresh bring the form back?

Sometimes, and that is a clue. If a refresh shows the form, the script may have run before its container existed, or the page loaded slowly. Fix the placement, then open the page cold to confirm the form shows without a refresh.

Does the test show the form on every device?

No. It does not predict every browser, country or extension your visitors use. It shows whether the form appeared for the simulated visitors, on the browsers the run uses, and the step where it did not.

Could a consent banner be the cause?

Yes. A banner that holds the form's script until a visitor accepts shows an empty space to anyone who declines. Test in two private windows, one declined and one accepted, and compare what each one sees.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .