Miro is hiding its free-start button on mobile
Two mobile leaks can slow or stop a visitor before they reach a Miro board. One sits directly on top of the signup action. The other makes a loaded page feel less ready than it looks.
Owner brief
We checked Miro's public homepage on desktop and mobile, followed the free-start path to the first signup screen, and tested the first 20 on-site links. Two issues stood out because both affect the moment a visitor is deciding whether to start.
Current paid creative or a paid destination could not be verified, so ad-to-page message match was not assessed. The findings below apply to homepage traffic.
Highest-Priority Revenue Leaks
1. The cookie panel covers the mobile signup button
The mobile page puts "Get started free" under a consent panel that takes up roughly half of the first screen. Only the top edge of the blue button remains visible. A visitor who came ready to start must deal with three privacy choices before they can use the page's main action.
That interruption lands at the worst possible moment. It can turn a clear signup path into a pause, a scroll, or an exit.
Fix the mobile layout first. Keep the privacy choices easy to use, but shrink the panel or move it so the full signup button stays visible. Then watch the overlap on common phone sizes whenever the homepage or consent tool changes.
2. The mobile page looks ready before it can respond cleanly
The main promise appeared in just under two seconds in our mobile check. But the page loaded more than 9 MB across 262 requests and was too busy to respond for about 1.1 seconds. Desktop did not show the same delay.
That gap matters because the page can look tappable while the phone is still working through scripts. A visitor may tap, see nothing happen, and assume the signup is broken.
Start with the code and outside services loaded before the first signup action. Delay anything the visitor does not need yet. Keep watching mobile response time and page weight after homepage, tracking, or consent changes.
What we checked
Funnel depth tested: public homepage on desktop and mobile, the first 20 on-site links, and the first signup screen at /signup/. The signup screen asked for a work email and offered Google, Office365, and Slack options.
We did not enter an email, submit a form, create an account, test onboarding, reach billing, attempt payment, check a confirmation, or review a follow-up email.
The first fix
Uncover the mobile signup button. It is the clearest, most immediate leak and the simplest one to verify across phone sizes. Then reduce the work the page does before that button is ready to respond.
Keep the signup path from drifting
These leaks can return when the homepage, consent settings, tracking tags, or signup flow changes. FunnelWatch can keep checking the path and flag the moment a mobile visitor loses a clear, responsive route to a board.