Loop Earplugs: the paid click hits a gate before it reaches the offer
A current "Shop Now" ad sends shoppers to a dedicated Loop landing page. Fresh visitors do not see the pitch first. They see a full-screen country question, then face a slow mobile load behind it.
Owner brief
We checked the current paid destination on desktop and mobile, then followed its public path to a featured product and the cart. Two leaks stood out. Both put extra distance between the ad click and the sale.
Five current public ads were found. One routes to the landing page reviewed here. The available ad record confirms the "Shop Now" action and destination, but does not contain enough creative copy to judge a more detailed promise-to-page match.
Funnel depth tested: current public ad, paid landing page, featured product page, and empty cart. We did not add a product, enter checkout, submit personal details, test payment, or check an order email.
Where paid shoppers are leaking
The first paid click leads to another "Shop now" decision
The ad already asks for a click. The landing page then covers the offer with "Are you in the right place?" and asks the shopper to choose a country and language before clicking "Shop now" again.
On a phone, this extra decision fills almost the entire first screen. The product story, social proof, and shopping choices are pushed behind it.
Every extra choice gives cold traffic another place to leave. It also makes a direct-response ad feel less direct.
For campaigns where the shopper's country is already known, send the click to the correct regional store and suppress this gate. If the question must remain, remember the answer and make the confirmation feel like part of checkout rather than a second ad call to action.
FunnelWatch should open each live ad destination as a fresh visitor by country and device. It should flag any new popup that hides the offer or adds a step before shopping begins.
On mobile, the main offer took more than 15 seconds to appear
In our fresh phone check, the page's main opening content took 15.1 seconds to appear. The visit downloaded about 8 MB across 395 requests. Desktop showed the same main content in 1.8 seconds.
A shopper sees the country gate first, then may wait again for the page behind it. That is a rough handoff from paid attention to product interest, especially on a phone connection.
Load the headline, proof, product choices, and first shopping action before optional video, chat, personalization, and other page extras. The initial server response was quick. Most of the delay happened while the browser built the page.
FunnelWatch should time this exact paid page after theme, campaign, tracking, popup, or media changes. The page can remain online while becoming too slow to hold mobile buyers.
The paid page we checked
Once the gate is cleared, the landing page has a broad product story, "Loved by 14M worldwide" proof, a range of use cases, and clear routes into products. The sales material is there. It needs to meet the shopper sooner.
Fix these first
- Route paid clicks to the right regional store and remove the country gate where the campaign already supplies that context.
- Cut the first phone load until the core offer appears within a few seconds.
Paid-funnel leaks return when regional routing, popups, storefront code, tracking, and media change. FunnelWatch keeps checking the real ad destination and the path toward checkout, so those changes do not quietly burn paid traffic.