Webflow is making paid mobile visitors wait for the free assessment
Two current ads send people to Webflow's AEO page. On a fresh phone visit, the main content took about 10 seconds to appear. Then a large cookie notice covered the route to the assessment. That is a rough first impression for attention Webflow has already paid
Owner brief
We checked five current public ads and opened the AEO destination used by two of them. We tested the page on phone and desktop, checked 20 links, and inspected the free assessment form without submitting it. Two problems stood out. Both sit between the paid click and the lead form.
Funnel depth tested: current public ad → AEO landing page → free assessment form displayed. We did not enter contact details, submit the assessment, inspect its results, test an email, start a trial, or contact sales.
Highest-priority revenue leaks
The paid page makes phone visitors wait about 10 seconds
The ad sends people to a focused page with a clear promise: learn how visible their site is in AI-driven search and get a free assessment. The destination matches that intent.
The phone experience is the problem. In our fresh check, the main page content appeared after 10 seconds. Desktop took about 3 seconds. The phone also downloaded roughly 4.5 MB through 175 requests, and the page moved while it was coming together.
A visitor can leave long before the assessment has a chance to earn the lead. Keep the headline and first assessment action light. Delay nonessential scripts, chat, and page extras until the core offer is ready.
FunnelWatch should keep timing this exact paid destination after changes to the page, tracking, chat, and campaign code. Alert when the promise or assessment takes more than a few seconds to appear on a phone.
The cookie notice covers the path to the assessment
On the fresh mobile visit, a cookie notice filled roughly the lower half of the screen. It covered the content below the hero, where the visitor needs to move toward the free assessment.
The notice does offer both "Reject all" and "Accept all." The friction is its size and position. A paid visitor must deal with privacy controls before the page shows the lead action they came for.
Shrink the notice on phones. Keep both choices easy to find, but leave the assessment headline or first field visible above it. Then test the first screen at common phone sizes before each campaign launch.
FunnelWatch should capture the fresh mobile view with consent cleared and uncleared. Alert when the notice hides the assessment or another main action.
What is working
The ads use dedicated destinations rather than sending every visitor to the homepage. The AEO page keeps the promise focused and asks for only a business email and website. All 20 sampled links returned successfully. Campaign details stayed attached to the visit. No block or human-verification screen interrupted the page.
Fix this first
Make the free assessment visible and useful within a few seconds on a fresh phone visit. Start by cutting the initial page work, then reduce the cookie notice so it no longer owns the first screen.
Paid-funnel leaks return when campaign code, tracking, chat, consent tools, or page content changes. FunnelWatch keeps checking the live destination and the path to the lead form, so Webflow can catch the problem before another run of paid clicks hits it.