The new Director of Product, Growth owns the journey "from first touch", and the LATAM marketing and sales hires will send paid and partner traffic to the site. That first touch is slow for real visitors: on the homepage, Chrome users wait 744 ms at the 75th percentile for the page to respond to a tap (the limit is 200 ms) and 3.1 s for the main content, and site-wide LCP got 28% slower. In the mobile lab test the page ships 3.3 MB of JavaScript, half of it unused, and 10 s of main-thread work, so the "Open your account" button feels stuck on mid-range phones, which are common in Latin America and Asia.
First action
Ship cache lifetimes and deferred ad tags on the homepage this week.
How to measure it
Homepage-to-registration rate
- Now
- –
- Target
- +10%
- By
- 60 days
Steps
Baseline
Real-user INP and LCP by country and device, and registration starts per visit.
Growth Analyst 3 days
Set the budget
INP, LCP, JavaScript weight for entry pages.
Director of Product, Growth 1 day
Fix caching
Long cache lifetimes for static assets.
Web Engineering Lead 2 days
Defer tags
Ads and analytics after interaction or server-side.
Web Engineering Lead 1 week
Trim JavaScript
Remove unused bundles and plugins.
Web Engineering Lead 2 weeks
Stop layout shift
Reserve image and banner space.
Web Engineering Lead 3 days
Measure
Chrome UX Report and registration rate monthly.
Growth Analyst monthly
Why it works
Set a budget for the homepage, pricing and sign-up entry pages (INP under 200 ms, LCP under 2.5 s on real users). Load ad and analytics tags after the first interaction or through a server-side tag manager, drop unused JavaScript, fix cache lifetimes, and reserve space for images to stop layout shift. Measure registration starts per visit by country before and after.
Every paid click and partner referral lands on these pages; a page that answers taps instantly converts more of them without any extra spend, and the work pays back across all 18 languages at once.
Ready to use
ChecklistEntry page speed budget
[ ] INP p75 under 200 ms (real users) [ ] LCP p75 under 2.5 s [ ] CLS under 0.1 [ ] JavaScript under 1 MB on first load [ ] Ad and analytics tags after interaction or server-side [ ] Long cache lifetimes on static files [ ] Image and banner space reserved [ ] Budget checked on every release
Risks and how to handle them
Attribution gaps from deferred tags
Move key conversion tags server-side first.
Plugin changes break pages
Roll out by template with visual checks.
Evidence
- Google PageSpeedReal Chrome users fail Core Web Vitals on the homepage: LCP 3.1 s and INP 744 ms at the 75th percentile (limits 2.5 s and 200 ms); across the whole site INP is 469 ms, CLS 0.14 and LCP 2.6 s, with LCP 28% slower than in the previous period. Mobile lab test: performance 13, LCP 11.6 s, layout shift 0.31, Total Blocking Time 1.9 s, 10.1 s of main-thread work; 5.1 MB in 187 requests, including 3.3 MB of JavaScript (1.6 MB unused), and about 6.8 s of savings available from cache lifetimes alone.Source
- HiringDirector of Product, Growth (Herzliya, posted October 18, 2026): will "own how customers discover, activate and grow with Payoneer across multiple surfaces", "the journey from first touch through onboarding to activation", including "onboarding, verification touchpoints, lifecycle journeys and the experimentation engine that improves them", and new surfaces ("mobile, partner and marketplace integrations, embedded and API-first flows"). "Growth in a regulated business means winning on conversion without giving ground on quality."Source
- HiringLATAM push: a Marketing Manager in Buenos Aires (posted September 24, 2026) to "own and drive growth across our LATAM markets" through demand generation with "our acquisition teams and agencies"; Senior Business Development Managers in Mexico City (September 24) and Sao Paulo (October 1) to enable "millions of SMBs and professional businesses across the LATAM region to get paid globally"; and a Senior Director, Customer Success - LATAM (September 30) to "design, launch, and iterate region-specific programs".Source