By platform
Elementor popup close button not working
A reader opens the offer and tries to get rid of it, but the close icon sits off the screen or does nothing. Mimiq sends simulated readers to the page on phones and laptops and shows each exit they tried.
Why can't readers close my Elementor popup?
The close icon fails when it sits outside the visible screen, when another element covers it, or when the setting that lets a tap outside the box close it is off. On a phone there is usually no Esc key, so the icon and the dark area behind the box are the only exits. A simulated test tries each exit in turn on a phone browser and reports which ones worked and where the reader gave up.
What this looks like in a report
“The offer covered my phone screen and I could not find a way to close it. I tapped the dark part and then the top, and the box stayed. I closed the tab.”
The fix. Keep the close icon inside the screen at phone width by letting the popup content scroll within the box, and turn on closing from a tap on the overlay. Check at phone width that the icon sits inside the screen and that a tap on it closes the popup.
An illustration. Run a test to see your own.See a real sample report
A tall popup pushes its close icon above the top of the screen
A popup is laid out on its own, and its height follows whatever it contains. On a laptop the box usually fits, so the icon sits where the owner expects. On a short phone screen the same box can be taller than the visible area, and the icon, which is positioned against the top corner of the box, moves out of reach. A reader then tries the other exits. A tap on the dark area behind the box works only when that option is on, and the Esc key does nothing on a phone. The reader taps, taps again, and leaves.
- The close icon's position at phone width, measured against the visible screen rather than the editor canvas.
- Overlay clicks: whether a tap on the dark area behind the popup closes it.
- Esc handling, which helps keyboard users only, so phone readers need a visible exit.
- Content height: a long headline or a growing form that pushes the box past the screen.
- A second popup or banner that opens over the first and hides the icon under it.
Why the icon ends up off the screen
The close icon belongs to the popup box, so its position depends on the box's size. A box designed in a wide desktop view looks balanced, then grows once its text wraps into more lines on a narrow phone. If the box is taller than the screen and cannot scroll, the top corner, where the icon usually sits, is above the visible area. Shortening the copy helps only for the words you tested, so the layout has to hold the box inside the screen rather than rely on a short headline.
A second cause is layering. A field, an image or a button inside the popup can sit over the icon's corner, and a tap on the icon lands on the field instead. Test the exact corner with a finger-sized tap in a phone browser. If the field takes the tap, the fix belongs in the popup's layout or stacking order, not in its copy. If a sticky bar on the page sits over the top of the box, the page is the cause.
Exits that depend on a setting
A reader can leave a popup in three ways: the close icon, a tap on the dark overlay, and the Esc key. Some popups turn off closing from an overlay tap, so a reader who taps the dark area gets nothing, which is what people do with an unfamiliar box. The Esc key only helps a reader on a keyboard. On a phone, the icon is the exit you can rely on, and the overlay is the backup.
A reader who cannot find an exit usually does not wait for one to appear. They leave the site, and the owner's analytics records a short visit to the article that looks like ordinary bounce. The offer and its copy are not the problem then. The visit only points at the popup when a run records the moment the reader tried to close it and failed.
Trying every exit on a phone, one at a time
A simulated reader arrives at the article, reads down, and reaches the popup the way a reader would. The run tries the close icon, a tap on the overlay and any other control it can see, and records which ones responded. A failed exit comes back with the screenshot at that moment and the step where the reader stopped. Read the report with the exits in that order, so each failure lines up with the setting that controls it.
Rerun the same reader after changing the popup's height, its stacking order or its overlay setting. A fix made for a laptop window can leave the phone icon above the top edge, so keep a phone and a laptop in the same set. The run does not read your analytics, so it cannot show how many readers left after the popup covered the article. Use the analytics for that count and the run for the exact exit that failed.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 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.
- 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.
- 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.
- 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.
- 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 longer offer or a new field can push the icon off screen again
A popup that fits today can break when the copy grows, a field is added for a campaign, or the template changes the width of the box. The icon's position depends on the whole box, not on the button alone, so a small edit inside the popup can move it. Rerun the same phone reader after every change to the popup's content, and check the close path on each popup you publish, not only the first one.
Starter
Try it on one launch
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
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Why does my close button work on my laptop but not on my phone?
A laptop window is wide, so the popup usually fits and its icon sits where you expect. On a phone the same box can be taller than the screen, and that moves the icon. Test the popup in a phone-width view, and confirm the icon sits inside the screen before you change anything else.
Can I remove the close icon and rely on the overlay?
It is a poor trade. Some readers do not know that a tap on the dark area dismisses the box, and a popup with no visible exit sends them off the site. Keep a visible icon, and keep the overlay tap as a second exit.
Does the test show whether the offer was worth closing?
No. It shows whether a reader could close the popup and what happened when they tried. It does not predict how many real readers would act on the offer, and a closed popup does not mean a lost sign-up.
Does this test need my site password?
Only when the page sits behind one. Readers open protected previews with the site password or a bypass secret, which uses paid credits. A public live page needs nothing from you.
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.