By platform
WooCommerce cart not showing on mobile: the icon
The shopper adds a phone case, the count changes, and there is no cart to tap, or the cart opens past the edge of the screen. Mimiq sends simulated visitors through a phone browser from the product page to the cart and shows where they lose it.
Why is my WooCommerce cart not showing on mobile?
On a phone, a WooCommerce cart can exist and still be out of reach. The count may change after Add to cart while the cart icon is missing from the header, hidden in a menu that does not list it, or covered by a bar. Check the header, then the cart panel, then the cart page, in that order, on a real phone at phone width. A simulated visitor test shows which of those a phone shopper hits, but it cannot tell you how your theme looks on every phone model.
What this looks like in a report
“The button changed, but I could not find a cart anywhere on the screen. The menu only had shop and about, so I gave up and closed the page.”
The fix. Add a cart link to the mobile header and the mobile menu, and make the cart table scroll inside its own box so the checkout button stays on screen at phone width.
An illustration. Run a test to see your own.See a real sample report
On a phone, the cart can exist and still be out of reach
A theme usually draws one header for the desktop and rebuilds it for a phone. The rebuilt header is where the cart icon goes missing: it is hidden at a set width, moved into a menu that does not list it, or drawn under a bar that covers it. The panel that opens from the icon can slide out past the screen edge, so the count changes and nothing visible happens. On the cart page, a table with price and quantity columns is wider than a phone, and the checkout button can sit off to the right. Each case looks like a missing cart, but the cart works.
- Open the store on a phone and look at the header. Is there a cart icon with a count next to it?
- Tap the icon. Does a cart panel open on screen, or does nothing happen at all?
- Open the menu. Does it list the cart, and does that link go to the cart page?
- On the cart page, scroll sideways. Is the table wider than the screen?
- Find the checkout button. Is it covered by a bar fixed to the bottom of the screen?
The header is drawn again for a phone, and the cart can drop out
On a laptop the cart icon sits at the top right, next to the search and account links. On a phone, the theme rebuilds the header, and each link has to earn its place again. A common result is that the icon disappears below a set width, while the menu still opens and shows shop, collections and contact. The count may still change, so the store seems to work.
Check the header first, because it is the fastest test. Open the store at phone width, and find the icon without scrolling. If the icon is missing from the header and from the menu, the shopper has no route to the cart from the top of the page. Add a cart link in both places before you touch the cart page, since a working cart page does not help a shopper who cannot find it.
A cart panel that opens off the screen looks like a dead tap
Many themes open a small cart panel from the icon rather than sending the shopper to the cart page. That panel is positioned to slide in from the right edge. On a phone, if the panel is sized for a wider screen, its close button and its checkout button can sit past the edge, and the shopper sees a dark overlay with no way out. The tap looks dead, but the panel opened and got stuck off screen.
The right version is a panel that fits the phone width and has a visible close button and a checkout button inside the screen. The wrong version is a panel with a fixed width in pixels, which works on the owner's own large phone and fails on a smaller one. Test the panel on a phone whose width is smaller than yours, because the layout you approve on a laptop is not the one a shopper sees.
Running the phone path from the product page to checkout
Give Mimiq the product address and one task a phone shopper would have: add a phone case from your phone, then find the cart and open it. Simulated visitors use phone browsers, so each run shows the header as a phone draws it. The report gives you the screenshot of each step, whether the count changed, whether a cart panel or cart page opened, and whether the checkout button was reachable without sideways scrolling.
The test shows what one phone size and one browser draw, and the screenshots are the proof. It does not replace a check on your own phone with a finger, because a bar that covers a button depends on the device and the browser. Use both: the test to catch the layout fault quickly, and your own phone to confirm the button is tappable where you expect it.
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 theme update or a new menu item can drop the cart from the phone menu
Rerun the same phone task after every theme update, menu change or header plugin change. A rebuilt mobile menu can quietly lose the cart link when someone adds a page, and the cart icon can move behind a new bar with no warning. The same task each time shows whether the path to the cart still exists, before a campaign sends phone traffic to the product page.
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
Will the test show a cart icon that is hidden only on tablets?
The test uses phone browsers, so a cart hidden at phone width shows up in its screenshots. A tablet layout is a separate question, and it needs its own task. The test cannot show how your store looks on every phone model.
Why does the count go up but I cannot see the cart?
The count lives in the header, but the link that opens the cart can be hidden, covered or pushed off screen. Tap the count itself and scroll the page. If the count is there and no panel opens, the cart works and only its display is broken, so the fix is in the header or the panel.
Is a cart panel that opens blank the same fault as a missing cart?
No. A missing cart means there is no way to reach the cart from the page. A blank panel means the link works and the panel draws nothing, which points at a script or a request.
Should I rebuild the mobile menu to bring the cart back?
Not first. Add a cart link to the menu and the header, run the phone task, and leave the rest of the menu alone. A full rebuild changes every other page on a phone and gives you more to check each time you test.
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.