Wellhub is hiring a Website Experience Sr. Director to own conversion and move the site to AI-assembled pages. Today real Chrome visitors wait 543 ms for the homepage to respond to a tap or click, and 470 ms across the site, more than twice Google's 200 ms "good" limit. On mobile the lab shows an 11.4 s largest paint and a second of blocking scripts, and the 590 KB homepage HTML repeats most headings and paragraphs two to four times. HR buyers and employees click "Contact sales" or "Find your plan" on a page that feels stuck.
First action
Find which scripts run during the first tap with a performance trace.
How to measure it
Homepage INP (real users)
- Now
- –
- Target
- under 200 ms
- By
- 90 days
Steps
Trace
Long tasks on first tap.
Website Experience Sr. Director 2 days
Remove duplicates
One copy of each section.
Frontend Engineer 1 week
Defer tools
Chat and recording after interaction.
Frontend Engineer 3 days
Split bundles
Load per section.
Frontend Engineer 2 weeks
Set a budget
INP and LCP limits in CI.
Website Experience Sr. Director 1 week
Watch field data
Chrome UX Report monthly.
Website Experience Sr. Director monthly
Why it works
Render each section once instead of several hidden copies, load chat, session-recording and enrichment scripts only after the first interaction, split the homepage bundle by section, and give the new website team a speed budget (INP under 200 ms, LCP under 2.5 s) that every new or AI-assembled section must pass.
Slow responses lose form starts on the pages that create MQLs and sign-ups, and a budget set now stops agent-built content from making it worse.
Ready to use
ChecklistHomepage speed checklist
[ ] Performance trace of the first tap on mobile [ ] Each section rendered once (no hidden duplicates) [ ] Chat, recording and enrichment scripts after first interaction [ ] Homepage bundle split by section [ ] Hero image sized and preloaded [ ] Budget in CI: INP < 200 ms, LCP < 2.5 s [ ] Monthly Chrome UX Report check [ ] Form-start rate tracked before and after
Risks and how to handle them
Tools lose data
Load them later rather than removing them.
Duplicated sections serve mobile and desktop layouts
Use one responsive section instead of separate copies.
Evidence
- Google PageSpeedUS homepage on mobile: performance 42 (desktop 66), largest contentful paint 11.4 s and total blocking time 1,006 ms in the lab. Real Chrome visitors: interaction to next paint 543 ms for the page and 470 ms across the site at the 75th percentile (Google's "good" limit is 200 ms), LCP 1.9 s and getting 10% slower. Accessibility flags: low colour contrast and "<html> element does not have a [lang] attribute". The homepage HTML is about 590 KB, and most headings and paragraphs appear two to four times in it.Source
- HiringWebsite Experience Sr. Director (posted September 9, 2026, Brazil or US): owns the website's move to "an Agentic Website Experience and Operations model, where AI agents increasingly handle content assembly, personalization, identity resolution, and optimization"; owns "conversion rate optimization end-to-end" and "website performance measurement and automated reporting (traffic, MQLs, sign-ups, conversions)".Source
- Your websiteThe list of script sources the site allows names five chat or chatbot tools (Zendesk, Drift, Qualified, Blip, Inbenta), two session-recording tools (Hotjar, Microsoft Clarity), two account-enrichment tools (6sense, Clearbit), HubSpot, Segment, Optimizely and more.Source