The new Fan Experience lead is hired because "the first few seconds after they land" decide whether fans buy, and paid social alone spends eight figures a year sending them in. Google's data for real visitors shows SeatGeek fails Core Web Vitals on exactly that moment: responsiveness (INP 216 ms site-wide, over the 200 ms limit), while loading and layout pass. On a phone the homepage carries 3.8 MB of JavaScript, 1.4s of blocking time and 52 third-party hosts sending 4.7 MB, mostly ad and measurement tags, so the first tap on a date or a seat filter waits behind them.
First action
Pull INP by landing template and traffic source from your real-user monitoring.
How to measure it
Share of paid-social landings under 200 ms INP
- Now
- –
- Target
- 90%
- By
- 60 days
Steps
Measure by page
INP and conversion per landing template and channel.
Marketing Analytics lead 3 days
Inventory tags
Every third-party host on landing templates, with an owner and purpose.
Lead Product Manager, Fan Experience 1 week
Remove or defer
Unused tags off; ad and measurement tags after first interaction or server-side.
Senior Software Engineer, Platform 2 weeks
Reserve space
Fixed height for the Spotify module and other late widgets.
Senior UX Designer 2 days
Trim JavaScript
Split code on performer, venue and event pages.
Senior Software Engineer, Platform 2 weeks
Set a budget
INP and tag-count checks in releases.
Lead Product Manager, Fan Experience 1 week
Read the lift
Conversion before and after, by channel.
Marketing Analytics lead 1 month
Why it works
Measure INP by landing page and channel (performer, venue and event pages from Meta, TikTok, Reddit and Snapchat first). Then load only the tags each page needs, defer ad and measurement tags until after the first interaction or move them server-side, reserve space for the Spotify module, and cut the 1.2 MB of unused JavaScript on landing templates. Add an INP budget to the release checks the role is asked to set up.
Faster first interactions lift conversion on every paid click, so the saving compounds across the whole media budget; and the incrementality team gets a cleaner read because fewer fans bounce before the page responds.
Ready to use
ChecklistLanding-page speed checklist
[ ] INP by template and channel in a dashboard [ ] Owner and purpose for every third-party host [ ] Ad and measurement tags deferred or server-side [ ] Fraud tools only where payment happens [ ] Fixed space for the Spotify module [ ] Unused JavaScript removed on landing templates [ ] INP budget in release checks
Risks and how to handle them
Attribution gaps from deferred tags
Move key conversion events server-side before deferring.
Fraud tools need early load
Keep fraud checks on checkout, not on landing pages.
Evidence
- HiringLead Product Manager, Fan Experience (posted October 14, 2026): "Most fans don't start their ticket search on SeatGeek. They start with a conversation with ChatGPT, a Google search, an Instagram ad, a team's website, an email, or a link from a friend. What happens in the first few seconds after they land decides whether they find their tickets with us or go back to searching." The role owns the journey from paid search, paid social, SEO, affiliates, partner links, email and push through landing and checkout, makes landing pages match "the ad, email or search that brought them", owns price display and fee transparency, credits and incentives, notifications, saved and followed events and trust signals, and sets up "automated quality checks" including "AI agents that continuously walk key fan journeys".Source
- HiringPaid Social & Programmatic Analyst (posted September 4, 2026): a channel that "spends eight figures annually across Meta, TikTok, Reddit and Snapchat"; per-performer campaigns "for artists, teams and tours against a constant onsale calendar"; "dynamic and catalog-driven campaigns" that "keep thousands of live events served accurately"; A/B tests across "targeting, creative, copy and landing pages"; and "real incrementality studies rather than taking platform-reported numbers at face value".Source
- Google PageSpeedHomepage, tested October 21, 2026: real visitors fail Core Web Vitals on responsiveness (INP 213 ms for the page and 216 ms for the whole site at the 75th percentile; the limit is 200 ms), while loading (LCP 2.1s) and layout (CLS 0.04) pass. In the phone lab test: score 32/100, 5.6 MB, 387 requests, 3.8 MB of JavaScript, 1.4s of blocking time, 8.8s of main-thread work, 1.2 MB of unused JavaScript and 4,614 page elements; 52 third-party hosts send 4.7 MB, mostly ad, measurement and fraud tools (Meta, TikTok, Snapchat, Bing Ads, The Trade Desk, StackAdapt, Impact, Forter, Riskified and several ad exchanges). The element that shifts is the "Connect to Spotify - Be the first to know when your favorite artists play nearby" module.Source