Fever is hiring a Technical SEO Lead to own Core Web Vitals on feverup.com. Google's field data says real visitors across the site wait 309 ms after a tap before the page responds (good is 200 ms), so the whole site fails Core Web Vitals on responsiveness, and load times are 22% slower than a year ago. Yet the public pages PageSpeed can test are close to fine: the homepage is at 208 ms, the New York Candlelight page at 171 ms and an event page at 195 ms. The slow taps are most likely in the steps PageSpeed cannot reach: choosing a date and session, picking tickets, and checkout, which is exactly where a slow response loses a sale.
First action
Add INP attribution to the date, ticket and checkout steps today and read a week of data.
How to measure it
Field INP across feverup.com
- Now
- –
- Target
- under 200 ms
- By
- 90 days
Steps
Instrument
Real-user INP with the slowest element and page type.
Frontend engineering lead 3 days
Rank the steps
Slow taps multiplied by bookings, by device and market.
Business Growth Analyst 1 week
Fix the pickers
Break long tasks in date, session and ticket selection.
Frontend engineering lead 2 weeks
Trim tags on booking steps
Load the second tag container and test scripts after the first tap.
SEO Technical Lead 1 week
Give instant feedback
Pressed states and spinners within 100 ms.
Frontend engineering lead 1 week
Test conversion
A/B the faster checkout against the current one.
Business Growth Analyst 3 weeks
Watch Search Console
Core Web Vitals report after 28 days.
SEO Technical Lead 1 month
Why it works
Add real-user INP measurement by page type and by element (the web-vitals library sends the slowest interaction with its target), split by device and market. Rank the steps by slow taps times bookings, then fix the top three: break up long tasks in the session and ticket pickers, defer the second tag-manager container and the A/B testing script on booking steps, and show instant feedback on every tap. Re-check in Search Console's Core Web Vitals report after 28 days.
Google uses Core Web Vitals in ranking, and a ticket buyer on a phone who taps "select" and sees nothing for a third of a second often taps again or leaves. Fixing the few slow steps lifts conversion on every paid and organic visit at once.
Ready to use
ChecklistSlow-tap hunt
[ ] web-vitals INP attribution on every page type [ ] Slowest element logged per step [ ] Steps ranked by slow taps x bookings [ ] Date and session picker long tasks split [ ] Second tag container deferred on booking steps [ ] Pressed state shown within 100 ms [ ] Search Console Core Web Vitals checked after 28 days
Risks and how to handle them
Tags removed that marketing needs
Delay them until after the first interaction rather than removing them.
Fixes only in one market
Track INP by country, since devices differ by market.
Evidence
- PageSpeed testGoogle PageSpeed for feverup.com/en (October 21, 2026). Real Chrome visitors across the whole site (Chrome UX Report, 75th percentile): Interaction to Next Paint 309 ms (good is 200 ms or less), so the site fails Core Web Vitals on responsiveness; the main content appears in 2.0 s and layout is stable, so loading passes; server response (time to first byte) is 1,037 ms. The homepage itself shows 208 ms for taps. Site-wide load time is 22% slower than a year earlier. The mobile lab test scores 56: the main content (the hero video) appears at 15.4 s, 8,171 KB downloaded in 325 requests, 1.36 MB of JavaScript, about 250 KB of it unused; two tag-manager containers together take about half a second of main-thread time. Desktop scores 85.Source
- PageSpeed testGoogle PageSpeed for the New York Candlelight page (October 21, 2026): real visitors respond in 171 ms and see content in 1.4 s, so the page passes Core Web Vitals; the mobile lab test scores 27 with 3,070 ms of blocking time.Source
- PageSpeed testGoogle PageSpeed for an event page (feverup.com/m/587584, October 21, 2026): real visitors respond in 195 ms, but the server answers in 1,128 ms (good is under 800 ms); the mobile lab test scores 43 with 1,890 ms of blocking time and 5.3 MB downloaded.Source
- HiringSEO Technical Lead (Madrid, posted September 22, 2026, also open in seven other cities): owns "the technical health and structural integrity of our massive transactional ecosystems, including feverup.com and our global white-label network"; skills listed include "Core web vitals", "CDN performance" and "Structure data"; the role must "Ensure optimal bot accessibility for the best processing for traditional search engines and LLMs" and know "LLM-powered search ecosystems (RAG, citations, query fan-out)".Source
- Your websiteTechnology on feverup.com (programmable.info scan): Angular, Google Tag Manager, Mixpanel, Optimizely and Permutive; help center on Zendesk; email protected with DMARC "reject".Source