By platform

Wix form not showing up on mobile: fix it

The form is in your desktop editor, but a phone visitor sees an empty gap where it should be, or no form at all. Mimiq sends simulated visitors through the live page on phone browsers and shows the step where the form disappears.

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

Why is my Wix form not showing up on mobile?

On a phone, the form is usually still on the page, but the phone layout hides it, crops it, covers it or fails to load it. Check the mobile view in the editor, then load the live address on a real phone to see which one it is. A simulated test shows the step where a phone visitor stopped.

What this looks like in a report

Who
Hana, a freelance nurse who needs a bookkeeper for her tax year
How they arrived
Opened the site from a search result on her phone
Where they stopped
Contact section, after the hero and two service blocks

“The heading says 'Ask us anything', and under it there is only blank white space. No box, no button. I tapped Contact in the menu and it scrolled me to the same empty space, so I left.”

The fix. In the mobile view of the editor, show the contact form in this section and make the section tall enough for all of it. Then open the live address on a phone in a private tab and confirm the fields and the button both show.

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

A phone gets its own layout, and the form may not be in it

A Wix page is built on a desktop layout, and a phone gets a separate layout that starts from it. An element can be hidden on that layout, sized for a wider screen, or placed under something else, and none of this shows up as an error. The visitor sees the heading, then empty space, a box with its bottom cut off, or a button that opens nothing. Pop-ups, cookie banners, chat buttons and embedded forms each add their own way to hide the form on a phone. Each one needs a different fix, so find which one before you rebuild anything.

  • Open the live address on a phone in a private tab and scroll to the form.
  • Switch the editor to its mobile view and open the same section. Is the form missing or hidden there?
  • Look for the button that opens the form. Does it still show on the phone, or is it missing from the mobile view?
  • If the form is an embed, open the form provider's own link on the phone. Does it load there?
  • Scroll the phone past the form. Does a cookie banner, chat button or sticky bar sit over the submit button?

The order a phone visitor meets it

A visitor on a phone opens the page from a search result or a link. A cookie banner or chat button may cover the bottom of the screen before they scroll. They move toward the section the heading promised, and the form is either there or it is not. If it is missing, the usual next move is the Contact link in the menu. If that link points at the same section, it lands on the same empty space, and the visitor decides the site has no way to reach you and leaves. Nothing on the page says the form is broken.

Five causes, and what each one looks like on a phone

Two causes are about layout. A form hidden on the mobile view is missing from the phone entirely, and the mobile view in the editor shows the same gap. A form sized on desktop can be cropped: a fixed box height pushes the button below the section edge, and a box wider than the screen pushes the right side of the fields off the edge, so the phone scrolls sideways.

The other three look different. A pop-up opens from a button, and on a phone that button can be missing or sit under the menu, so the form never opens. An embedded form from another provider can show as a blank box or an error. A cookie banner, chat button or sticky bar can sit over the submit button, so the form is there but the button cannot be reached.

How to tell the five apart

Start with the phone, then open the editor. If the space is empty on the phone and the form is also missing from the mobile view, the element is hidden on mobile. If the form is in the mobile view but the phone shows nothing, check the pop-up button, then the embed: an embed that is blank on desktop too needs its own fix, and one that works on desktop points at the phone layout. A cut edge means the box is sized wrong. A whole form with its button under a bar means the bar is the cause.

What the editor shows, and what the test shows

The editor shows the layout you set, which is easy to trust. It does not show the live page on a phone, with its banners, chat button and embeds loading, and a phone may keep an older copy in its cache. A simulated test sees the live page the way a visitor does. The report gives the step where a phone visitor stopped, a screenshot of what they saw and a fix for each problem. It does not predict how many real visitors would send the form, so rates still come from your analytics or a live experiment.

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.

The next mobile layout edit can hide the form again

Each mobile fix can move the form somewhere else on the phone, so run the same visitors through the live page again after every change. If the form sits behind a members login, give the visitors a test account. Send visitors from your mobile ad or social link too, since they may land on a different part of the page than search visitors do.

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 my Wix form work on my computer but not on my phone?

Your computer shows the desktop layout, and a phone shows the mobile layout. A form can be hidden on the mobile view, sized for a wider screen, or covered by a banner on a phone, and none of that appears on desktop. Open the live address in a private tab on a phone to see what a stranger sees.

Can I see what a phone visitor sees inside the editor?

Partly. The mobile view shows the layout you set, so it is the fastest way to find a hidden form or a cut edge. It does not show the live page on a phone, with its banners and embeds loading, or the older copy a phone may cache.

Will a simulated test show whether more people will sign up?

No. The test shows where a simulated phone visitor stopped and what the screen showed them then. It does not predict how many real visitors would fill in the form. Get rates from your analytics or a live experiment, and use the test to find the blank step first.

The form shows on my phone but the bottom is cut off. Is that the same cause?

It is the box cause. Check whether the form has a fixed height, or whether the phone scrolls sideways, which means a field is wider than the screen. Fix the size in the mobile view, then load the page again in a private tab.

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 .