By industry
Dropshipping landing page: ad clicks, no orders
A shopper taps a product ad on a phone, sees a different color, and cannot tell why the buy button is gray. Mimiq sends simulated shoppers from the page to the payment step and shows where each one stopped.
Why does a dropshipping landing page get ad clicks but almost no orders?
The ad promised one product, so the landing page has to show that product at once, with a variant, a total and a delivery line a shopper can read before they tap buy. When one of those is missing or wrong, the shopper leaves for a store that answers the question. Check the page against the ad on a phone, one element at a time. A simulated test sends shoppers through the same steps and shows the one where each of them stopped.
What this looks like in a report
“The ad showed a gray hoodie, but this page opens on black. I picked medium and the button still will not go. There is no message, so the store may be broken.”
The fix. Preselect the size the ad shows, or put a line next to the gray button that names the missing choice, such as 'Pick a size'. Then reload the page on a phone and confirm the ad's color is the first one a shopper sees.
An illustration. Run a test to see your own.See a real sample report
A gray buy button with no reason shown looks broken to a shopper
Dropshipping stores often send paid traffic to one product page that was set up quickly. The ad shows the item in one color and size, and the page opens on the first variant, or on none at all. If no variant is chosen, the buy button can stay gray and do nothing, and no line of text says what is missing. A shopper who taps twice assumes the button is broken and goes back to the ad. The delivery estimate and the shipping charge often appear only at the last step, so the shopper meets the real total after they have already decided to buy.
- Does the product, color and size in the ad match the first screen?
- Is a size or color selected by default, or must the shopper pick one?
- When the buy button is gray, does a line of text say what is missing?
- Does the delivery estimate appear before the cart, not only at checkout?
- Does the country on the page match the country the shopper is in?
How it works
- 01
Match the ad to the first screen
Open the ad's link on a phone in a private window. Before you tap anything, write down the product, color and price the ad showed, then compare them with what the first screen shows.
- 02
Choose every option the way a shopper would
Pick each color and size in turn. After each choice, check that the buy button changes state and that the image, the price and the variant name all update. A button that stays gray with no message is a failure, even if the store works on a laptop.
- 03
Find the first place the total appears
Look for the earliest point where the delivery estimate and the shipping charge are shown. If they only appear after the cart opens, move them up to the product page, so the shopper can decide before they have put anything in a cart.
- 04
Continue to the payment step and stop
Keep going until the page asks for a card. A test visitor can reach that step but cannot pay with a real card, so the run ends there.
The ad's promise has to be on the first screen
A shopper who taps an ad has already decided something. They chose a product from a picture, and they expect the page to show the same product in the same color. A landing page that opens on a bundle, a different color or a general category makes them search for the item they tapped, and many leave at that point. Ad creative changes faster than product pages do, so a new ad for a new color can point at a page that still shows last month's photo. Check this by listing the ad's words and the first screen's words side by side, then circle anything the shopper would have to hunt for.
Variants, a gray button and the missing message
Most products come in more than one variant, and the page often makes the shopper pick one before the button works. That rule is reasonable. The failure is the silence. A disabled button with no line of text tells the shopper nothing, so they try a second size, reload and then leave. The same silence happens when a size is sold out: the option still shows, the button grays out, and no note says the size is unavailable. Test each variant on its own. If one of them fails with no message, the fix is a line of text next to the button, not a new photo.
Shipping and the total, and why the cart is too late
Dropshipped items ship from a supplier, so the delivery estimate depends on the supplier's location and stock. A shopper who learns the estimate and the shipping charge at the last step has already spent time choosing a product. Look for the first place the total is written down. If the first figure a shopper sees is the item price, and the real total appears only after the cart opens, the page is hiding the cost. Mark that step in your run, then decide where the estimate belongs.
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 new supplier can change the delivery line while the ad keeps running
Dropshipping pages change when a supplier changes, a color sells out, or a new ad goes live with a different photo. Each change can move the variant, the total or the delivery estimate. Run the same shopper through the page after each supplier or ad change, and again before you raise the budget on a campaign.
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 this tell me my conversion rate for the ads?
No. It does not predict how many shoppers will buy, and it cannot tell you what the ads return. It shows the step where a simulated shopper stopped, what the page did not show and which choice made the button fail. Take rates from your store's reports and your ad account, then use the run to explain a drop.
Can a simulated shopper complete a purchase?
No, not with a real card. A shopper can choose options, fill in an address and reach the payment step, and the run ends there. Visitors cannot pay with a real card, so a checkout that needs one for every test order cannot be finished.
Should I give the test a real discount code or a real customer address?
No. Point the run at a live or preview address and use the product the ad shows. If the page needs a code to show the price, create a test code in your store and use that. Keep real discount codes and customer addresses out of any test.
Does this work for any store that sells online?
It works on any store that loads in a normal browser at a public address, because the run uses the page the way a shopper would. It cannot open an installed app, and it cannot get past a login the visitor does not have.
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.