Coinbase is hiring to run "hundreds of millions in ad spend" across Meta, TikTok, Snap and Reddit and to test "app store/landing experiences". Those ads are mostly seen on phones. Yet Chrome's real-visitor data for www.coinbase.com shows the main content taking 4.8 seconds to appear on phones at the 75th percentile, with 31% of mobile page loads over 4 seconds, and 6.3 seconds on desktop. The origin fails Core Web Vitals on both devices, so a share of every paid click waits on a blank or shifting page before it ever reaches Sign up.
First action
Pull the 20 URLs with the most paid-social sessions and run each through PageSpeed.
How to measure it
Phone LCP at the 75th percentile
- Now
- –
- Target
- Under 2.5 seconds
- By
- 90 days
Steps
List landing URLs
Top 20 by paid-social and app-install-fallback traffic.
Senior Performance Marketing Manager, Global Paid Social & Mobile UA 2 days
Measure
PageSpeed lab plus Chrome field data per URL.
Web Platform Engineering 2 days
Find the LCP element
Hero image, ticker or font on each page.
Web Platform Engineering 3 days
Fix the top causes
Preload the hero, defer non-critical scripts, size the price widgets.
Web Platform Engineering 3 weeks
Run a holdout
Split one market's paid-social traffic between old and fast pages.
Senior Performance Marketing Manager, Global Paid Social & Mobile UA 3 weeks
Measure downstream
Signup, verification and first purchase by page version.
Data Science 2 weeks
Set a budget
An LCP limit every new landing page must meet.
Web Platform Engineering 1 week
Report
Speed next to cost per acquired user on the paid dashboard.
Senior Performance Marketing Manager, Global Paid Social & Mobile UA monthly
Why it works
Treat page speed as part of the paid-social test plan. List the 20 web URLs that receive paid and social traffic (signup, offer, price and Predict pages), measure each in PageSpeed and in field data, and fix the biggest causes of slow LCP first: the hero image or animated price ticker, render-blocking scripts and late-loading fonts. Reserve space for the price widgets that shift the layout. Then run a holdout: half of one market's paid-social traffic to the faster page, half to the current one, and compare signup and first-purchase rates.
Every second of delay on mobile loses visitors before they act, and the loss scales with the ad budget. A speed fix improves every campaign at once, which no single creative test can do.
Ready to use
ChecklistFast landing page check
[ ] LCP element identified per page [ ] Hero image preloaded and sized for phones [ ] Price ticker renders a static first value [ ] Non-critical scripts deferred [ ] Fonts preloaded or system fallback [ ] Space reserved for every widget (no layout shift) [ ] PageSpeed mobile run saved before and after [ ] Holdout set up in one market
Risks and how to handle them
Field data moves slowly
Use the holdout for the decision and field data to confirm.
Price widgets are dynamic
Reserve their space and render a static first value.
Evidence
- Google PageSpeed (Chrome UX Report)Real Chrome visitors to www.coinbase.com over the 28 days to October 19, 2026: on phones the 75th-percentile Largest Contentful Paint is 4.8 seconds and 31% of page loads take longer than 4 seconds (poor); layout shift is 0.12 and interaction delay 278 ms. On desktop LCP is 6.3 seconds with 42% of loads poor and layout shift 0.16. Google's "good" thresholds are 2.5 seconds, 0.1 and 200 ms, so the origin fails Core Web Vitals on both devices.Source
- HiringSenior Performance Marketing Manager, Global Paid Social & Mobile UA (posted September 15, 2026): owns "hundreds of millions in ad spend across paid social and mobile channels" (Meta, TikTok, Snap, Reddit and mobile display) "to drive new user acquisition at or above ROI targets", with a testing agenda "across creatives, audiences, bidding strategies, and app store/landing experiences" and measurement through MMM, SKAN, MMPs and "incrementality tests".Source
- Your websiteThe homepage offers "Earn up to $2,000 when you buy $50 in crypto" next to Sign up, and links to Base developer pages www.base.org/build/onchainkit ("OnchainKit") and www.base.org/build/base-account ("Base Accounts (Smart Wallets)"), both of which return 404 (checked October 21, 2026).Source