On this page
- Check whether phones are the problem
- Watch phone replays with the screen in mind
- Taps that miss their target
- Sticky bars that eat the screen
- Pop-ups on phones
- Elements that overlap on the live site
- Pages that load slowly on a phone signal
- Keyboards that cover fields
- Menus that hide the way forward
- Where to start
- Frequently asked questions
- Try it on your site
- Sources
Seven problems tend to slip past a quick check of a Wix store on your own phone and show up in phone replays: taps that miss small targets, sticky bars that squeeze the product, pop-ups that are hard to close, elements that overlap on the live site, pages that load slowly on a phone signal, keyboards that cover form fields and menus that hide the way forward. Each section below shows what the problem looks like in a replay and what to change on Wix.
Your store probably looks fine on your own phone. You know where everything is, you're on Wi-Fi, and you're not in a hurry. A shopper who has never seen it is trying to buy with one thumb, on a weaker signal, in between other things.
This guide is about pages that work but are hard to shop on a phone. If your site looks broken on phones or tablets, with parts cut off, missing or out of place, start with why a Wix site doesn't display properly on mobile.
Key takeaways
- Use Store Analytics' mobile and desktop switch to see whether phones convert worse before you watch any replays.
- Make buttons shoppers tap often 44 to 48 pixels square with space around them, and keep Remove links away from Add to Cart and quantity buttons.
- If you turn on Make button sticky for Add to Cart, set the mobile header to Disappears so two bars don't squeeze the product.
- Wix already resizes images and converts them to modern formats such as AVIF, so for speed, check Site Speed's mobile view, keep videos out of the first screen and remove apps you don't use.
Check whether phones are the problem
Before you watch anything, open Store Analytics in your site's dashboard. Wix lists it in the Analytics section, under Sales. Its conversion funnel has a switch at the top for desktop, mobile or all. Compare the rates for the two.
Say your desktop visitors add to cart in 9% of the sessions where they viewed a product, and phone visitors in 4%. Phones add to cart at less than half the desktop rate (4 ÷ 9 is about 0.44), so your product page has a phone problem. If the rates are close, look elsewhere first.
Watch phone replays with the screen in mind
Phone visits play back in the phone's own shape, with each tap shown. You see the narrow view the shopper had and where their thumb landed. Replays marks each visit Mobile or Desktop, and setting the Device filter to Mobile lists only phone visits, tablets included.
Three habits help.
- Watch where each tap lands compared with what it was aimed at. A tap just beside a button says the button is too small.
- Treat scrolling as the main way phone shoppers move, and watch its speed and direction.
- Notice what fits on the screen at each moment. A button below the fold doesn't exist until someone scrolls to it.
Taps that miss their target
In the replay. Taps land near a small link or icon and miss. The visitor taps two or three times before it works, or hits the wrong thing, like a Remove link sitting next to the quantity buttons in the cart.
How big is big enough. Google's web.dev guidance recommends tap targets of around 48 pixels on a mobile site, spaced about 8 pixels apart. Apple's design guidelines use 44 by 44 points as the default size for controls on iPhone, and Android's guidance sets a 48 dp minimum, in line with Material Design. WCAG 2.2, the web accessibility standard, sets 24 by 24 CSS pixels as the minimum at its AA level. Treat 24 as the floor and 44 to 48 as the goal for anything shoppers tap often.
The fix.
- In the mobile editor, make small buttons and links bigger, with about 8 pixels of space around them.
- Keep actions that undo work, such as Remove, well away from buttons shoppers tap all the time.
- Repeated taps on one spot can also mean something is covering the button. The guide to rage clicks on Wix shows how to find what's on top.
Sticky bars that eat the screen
In the replay. A frozen header, an announcement bar, a cookie banner and a chat button all stay on screen at once. The product sits in a narrow strip between them. A tap meant for Add to Cart opens the chat, and the visitor has to find a way to close it.
The fix on Wix.
- Let the header get out of the way. In the mobile editor, click the header, then Change Header Scroll, and choose Disappears. The header hides as visitors scroll down and comes back when they scroll up. If a header set to Freezes holds too much, Wix switches freezing off on the live mobile site, because a frozen header that big would cover the screen. On Wix Studio, select the header, open the Inspector and pick a Scroll effect under Header settings.
- Decide on a sticky Add to Cart. On the product page element's Settings tab, under Add to Cart button, the Make button sticky toggle keeps the button on screen on phones. It helps on long product pages. Count it as your one sticky bar, and pair it with a header that disappears.
- Check the Quick Action Bar. If you use one, it sits at the bottom of your mobile site. Wix's advice when it covers part of your footer is to make the footer 50 pixels taller.
- Move the chat button so it never sits on top of Add to Cart or the cart icon.
Pop-ups on phones
In the replay. A pop-up opens. The visitor taps around its edges, tries to scroll the page behind it, taps the dark area outside it, and leaves.
The fix on Wix. Popups you made in the Wix Editor are hidden on your mobile site by default, so if one shows on phones, someone chose to show it. In the mobile editor you can turn on closing the popup by tapping outside it, and you can hide its X or Close button on mobile, so check that you haven't. Keep a way to close it on screen, and keep popups off your cart page.
Elements that overlap on the live site
In the replay. A button sits half under a block of text, or a heading runs into a photo. Taps on the covered part do nothing.
The fix on Wix. Wix's help center explains that a large amount of text in a single text box can overlap other elements on the live mobile site. Break it into one text box per paragraph and put the other elements between them, with some space. For elements arranged side by side that shift on mobile, group them and attach them to a transparent container box. Then check the page on a real phone, not just the mobile editor. When whole sections shift, vanish or get cut off rather than a single button being covered, it's a layout problem; the guide to Wix display problems on mobile goes through those.
Watch shoppers from product page to cart
See where shoppers stop on product and cart pages, with each click listed beside the replay and typing masked. Free forever: 2,000 recordings a month.

Pages that load slowly on a phone signal
In the replay. Slowness shows up as behavior. A visitor taps a link and the screen doesn't change for several seconds, so they tap again or give up. Or they scroll a category page, stop while the photos fill in, and leave. Visitors who give up before touching anything aren't recorded at all, so for slow first loads, Site Speed below is the better measure.
The fix on Wix. Resizing photos by hand gains little: Wix resizes images so only the pixels needed are downloaded, converts them to modern formats such as AVIF wherever it can and loads them lazily. Wix does still suggest compressing very large files before you upload them. After that, spend your time here:
- Check Site Speed in your site's dashboard. Its Real visitor experience section shows Core Web Vitals from your actual visitors, with a separate mobile view. It needs at least 10 site sessions in the last 7 days to show data.
- Keep the first screen light. Wix recommends against videos above the fold, and notes that iFrames, animations and third-party apps load last, so use them sparingly.
- Remove apps and widgets you don't use. Wix's own advice is to keep only the essential ones.
For the other causes Wix lists, from fonts and lightboxes to pages it can't cache, see why a Wix site is slow.
Keyboards that cover fields
In the replay. A visitor taps a field near the bottom of the screen and the page jumps. They scroll up and down, tap outside the field, then tap it again. With a sticky bar at the bottom, the next field or the Send button stays hidden behind it.
The fix.
- Keep phone forms short, one field per line.
- Put the submit button right below the last field.
- Fill in every form on your own phone, start to finish, with the keyboard open. The guide to unfinished contact forms goes further.
Menus that hide the way forward
In the replay. The visitor opens the menu, opens a section, closes it, opens another, then gives up and searches instead. Or the menu runs longer than the screen and they never scroll inside it.
The fix.
- Keep top-level items few, with names a stranger would understand.
- Put your best-selling categories first.
- Make it obvious the menu scrolls, for example by letting the last item peek out at the bottom.
If the menu won't open at all, see why a Wix menu stops working on phones.
Where to start
Start with the step the mobile funnel says is weakest. If phones fall behind at Added to cart, open visits whose Activity list starts with a Page view of a product page (Wix product addresses begin with /product-page/ unless you've changed the prefix) and keep going until you've watched ten that play back in a phone's shape. Note the first thing that goes wrong in each, then count which problem came up most.
After you change a header, a popup or a button, watch the next visits live to see the change in use. For option pickers and size guides, see how to improve a product page, and for payment steps, the checkout friction checklist.
Frequently asked questions
How big should tap targets be on mobile?
Aim for 44 to 48 pixels square for buttons shoppers use often, such as Add to Cart and quantity controls, with about 8 pixels between targets. Google's web.dev guidance recommends around 48 pixels with that spacing, Apple's guidelines use 44 by 44 points as the default control size on iPhone, and Android's guidance sets a 48 dp minimum. WCAG 2.2's AA level sets 24 by 24 CSS pixels as the minimum, which is a floor rather than a target.
Should I turn on Make button sticky on my Wix product page?
Yes, if your product pages are long: Add to Cart stays within reach while shoppers scroll. The toggle is on the product page element's Settings tab, under Add to Cart button, and it applies only on phones. Treat it as your one sticky bar: set the mobile header to Disappears, keep the chat button clear of it, and watch phone replays for taps that hit it by mistake.
Why is my Wix site slow on mobile?
Look at what you've added to your pages before you look at your photos. Wix already resizes images, converts them to modern formats such as AVIF and loads them lazily (compressing very large files before upload still helps), but it recommends against videos above the fold and says iFrames, animations and third-party apps load last. Check Site Speed in your dashboard for real-visitor Core Web Vitals on mobile, then move videos out of the first screen, use those elements sparingly and remove apps and widgets you don't need.
Why is my Wix popup not showing on mobile?
Popups made in the Wix Editor are hidden on your mobile site by default. To show one, open the mobile editor, go to Menus & Pages, then Popups, select the popup, click its Settings icon and choose to display it automatically. Then test it on a real phone: check that the close button is visible and big enough, and that the popup doesn't cover your cart. If it still doesn't appear, Spin Wheel's checklist for a Wix popup that isn't showing covers the other causes, from publishing and triggers to schedules and a cached copy.
Try it on your site
To see your own phone visits, add Session Recordings and open the first few that play back in a phone's shape. More on recording phone visits on Wix.
Sources
- Wix Stores: About Your Store Analytics
- web.dev: Accessible tap targets
- Apple Human Interface Guidelines: Accessibility
- Android Developers: Accessibility API defaults (minimum touch target size)
- W3C: Understanding WCAG 2.2 Success Criterion 2.5.8, Target Size (Minimum)
- Wix Editor: Customizing the Header and Footer on Your Mobile Site
- Studio Editor: Adding Header Scroll Effects
- Wix Stores: Customizing Your Product Page
- Wix Editor: Adding and Setting Up the Quick Action Bar on Your Mobile Site
- Wix Editor: Showing and Customizing Popups on Your Mobile Site
- Wix Editor: Resolving Alignment Issues on Your Live Mobile Site
- Wix: Understanding Your Site Speed Dashboard
- Wix: Site Performance: Designing a Performance-Focused Website
- Wix: Site Performance: Best Practices (image formats checked October 6, 2026)
- Wix: Performance
- Wix: Customizing Your Page's URL Structure in SEO Settings



