By platform

Wix website does not fit screen: the wide part

A visitor opens the page on a phone and swipes, and the whole page slides sideways with the menu button pushed past the edge. Mimiq sends simulated visitors to the home page in phone browsers and shows the screens they see as they scroll.

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

Why does my Wix website not fit the screen?

A Wix page that does not fit a phone has something wider than the screen, so the whole page slides sideways and parts of it are cut off. The usual causes are a banner or gallery with a fixed width, an embedded map or video, or a box dragged past the right edge of the page in the editor. Check the mobile view for anything that reaches past the edge, then open the live page on a phone and swipe once. A simulated visitor test shows whether the first screen and the menu are cut off, but it cannot tell you which element is at fault.

What this looks like in a report

Who
Ruth, a retiree looking up store hours before a walk to a stationery shop
How they arrived
Tapped a map pin for a stationery shop
Where they stopped
Home page, after the first swipe down to find the hours

“I swiped and the whole page slid sideways. The menu button had gone past the edge, and I could not find the hours anywhere, so I closed the page.”

The fix. In the mobile view of the editor, select the banner and the gallery, set their width to fit the screen, remove any element dragged past the right edge, then confirm in a phone browser that no sideways swipe moves the page.

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

One element past the screen edge makes the whole page slide

A phone screen has a fixed width, and a page is only as narrow as its widest element. If anything on the page is wider than the screen, the phone lets the whole page slide sideways, and every block shifts with it. The wide thing can be a banner with a set pixel width, a gallery, an embedded map, or a text box dragged past the right edge on a laptop. A visitor swipes to read, the page moves, and the menu button or the end of a headline goes off the side. A laptop screen is wide enough to hide all of this.

  • Open the live address on a phone and swipe left. Does the whole page move, or only one block?
  • Check the right edge of the first screen. Is a banner or a button cut off?
  • Open the mobile view in the editor and look for elements that reach past the right edge.
  • Find any embedded map, video or form with a fixed width in pixels.
  • After a sideways swipe, check whether the menu button is still on screen.

Find the element that is wider than the phone

Start in the mobile view of the editor, not the desktop. Check the widest-looking pieces first: the top banner, any full-width strip, a gallery, an embedded map or video. Each one should stop at the screen edge. A banner with a fixed width in pixels can fill a laptop and run past a phone, while a banner that stretches across the page does not. Check each piece by its right edge, because the left edge will always look fine.

Then open the live address on a phone and swipe sideways once on the first screen. If the page moves, the wide element is on that screen. If the page moves only after you scroll down, the wide element is further down, so work down the page one section at a time. Write down the first section where the slide starts, because that is the one to fix first.

Parts you cannot see in the editor still widen the page

A text box or a decorative shape dragged past the right edge on a laptop can sit there out of view, and a phone still counts it. From inside the editor it looks like empty space, so owners rarely find it by looking. Drag each block back inside the page width, then swipe on the live page again to check that the slide has stopped. A shape you cannot see still has to fit on the phone.

The right version brings every element back inside the page width and sets the wide blocks to fit the screen. The wrong version shrinks the whole page to fit, which makes the laptop look cramped and still leaves the element off the edge. Fix the element itself, then test again in a private window, because your own browser may keep an earlier version of the page on screen.

What a sideways slide looks like in a test

Give Mimiq the home page address and one task a buyer would have: open the menu on your phone and find the store hours. Each simulated visitor opens the page in a phone browser, reads the first screen and tries to reach the menu and the hours. The screenshots after each step show a page cut at the right edge when it has slid, which is how a sideways slide looks in a still picture.

The test cannot list every element that is too wide, and it does not show the feel of a slide on one particular phone. It shows whether the first screen is cut off and whether the menu and the hours can still be reached. Use it to confirm the page sits inside the screen after each fix, then check once more on your own phone.

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 banner, map or chat widget can push the page wide again

Rerun the phone task after you add a banner, an embedded map, a video, a chat widget or a pop-up. Any one of them can be wider than the screen, and the page slides again without a change to the text. The same task from the same first screen shows the slide the first time it appears.

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

Will the test find every element that is too wide?

No. It shows the pages it visits in phone browsers, and whether the first screen and the menu are cut off. It cannot list every element on the page or check every phone width. Use it to find the slide, then fix the element and check the screen on your own phone.

Why does the page fit on my laptop but slide on a phone?

A laptop screen is wide enough to hide an element that runs past the edge, so the overflow never shows. A phone is narrower, and the same element pushes the page sideways. Compare the mobile view in the editor with the live page on a phone to find the element.

Can a chat widget or pop-up cause the sideways slide?

It can, when its box is wider than the screen or sits past the edge. Turn the widget off in the editor, then open the live page on a phone again. If the slide stops, the widget is the cause, and its width setting is the fix.

Do I need to test every phone size?

Not every size, but include a narrow phone. A page that fits a narrow screen usually fits a wider one, so a slide on a small phone is the one to catch. Run the task on a smaller phone you own, and use the test for the rest of the check.

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 .