The new Growth Marketing Manager owns "site-to-signup conversion", but the front door is slow. Google's data for real Chrome visitors shows gamma.app failing Core Web Vitals: the main content appears after 6.9 s and taps respond after 558 ms at the 75th percentile (the targets are 2.5 s and 200 ms). In the phone lab test the homepage downloads 25.5 MB in 206 requests, and the headline "Visual storytelling without limits." is the last thing to paint. A product that sells speed makes its visitors wait before they ever see a prompt box.
First action
Ship the H1 and prompt box as static HTML and lazy-load everything below the fold.
How to measure it
Origin LCP (75th percentile, real users)
- Now
- –
- Target
- Under 2.5 s
- By
- 60 days
Steps
Baseline
Visit-to-signup by device and country, plus field LCP and INP from Search Console.
AI Data Scientist 2 days
Set a budget
Under 2 MB and under 2.5 s LCP on a mid-range phone for the homepage.
Engineering Manager, Growth 1 day
Paint the H1 first
Server-render the headline and prompt box; no animation gate before the first paint.
UI Engineer 3 days
Lazy-load media
Images and video below the fold in AVIF/WebP with explicit sizes.
Software Engineer, Frontend 1 week
Cut JavaScript
Split the bundle and remove the 1.5 MB of unused code from the first load.
Software Engineer, Frontend 1 week
Defer tags
Tag manager, chat and test tools after interaction or idle.
Software Engineer, Frontend 2 days
A/B test
Fast page vs current page on visit-to-signup and first creation.
Software Engineer, Growth 3 weeks
Guard it
A Lighthouse budget in CI that fails builds that exceed it.
Software Engineer, Frontend 2 days
Why it works
Treat the homepage as a growth surface with a performance budget. Render the H1 and the prompt box as server HTML with no client-side wait; lazy-load the 7.2 MB of imagery and any video below the fold in modern formats; split out the 1.5 MB of unused JavaScript; move render-blocking scripts after first paint; and load the tag manager, chat and testing tools after interaction. Then A/B the fast page against the current one on visit-to-signup.
Every second of load time on mobile costs sign-ups, and most of the fixes PageSpeed lists are mechanical. With over 100 million users and heavy organic traffic, a few points of visit-to-signup conversion is a large number of new creators for no extra spend.
Risks and how to handle them
Brand motion lost on the hero
Keep animation, but start it after the first paint.
Lab and field numbers disagree
Judge success on field data and sign-ups, not the lab score.
Evidence
- Google PageSpeedHomepage, mobile lab test (October 22, 2026): performance 30 (desktop 48); Largest Contentful Paint 29.5 s on the H1 "Visual storytelling without limits."; Total Blocking Time 1.5 s; 25.5 MB downloaded in 206 requests (7.2 MB images, 4.1 MB JavaScript). Biggest fixes: about 1.5 MB of unused JavaScript (about 4.4 s), render-blocking requests (about 2.8 s), and 4.8 MB of image savings. Real Chrome visitors fail Core Web Vitals: origin LCP 6.9 s and INP 558 ms at the 75th percentile (homepage alone: LCP 8.2 s, INP 653 ms).Source
- HiringGrowth Marketing Manager (posted July 2, 2026): "Gamma has grown to over 100 million users, and a significant part of that story is organic." The role owns top-of-funnel growth across "SEO, content, social, and emerging channels", paid channels, will scale the "affiliate and creator program from the ground up" and "Drive site-to-signup conversion optimization, turning traffic into activated users".Source
- HiringSoftware Engineer, Growth (posted October 15, 2026): owns "new user onboarding, activation funnels, viral loops, and monetization features including credit systems, paywalls, pricing experiments, and upgrade flows", and key metrics "including sign-ups, activation rates, conversion, and retention". The Engineering Manager, Growth (July 23, 2026) leads monetization (billing, "AI usage tracking and crediting, pricing systems") and self-serve growth ("onboarding, activation, discovery, and lifecycle flows").Source
- Google PageSpeedThird-party code on the homepage in the same test: 16 services and 1.2 MB, led by Google Tag Manager (516 KB, about 310 ms blocking), Intercom (234 KB), the consent manager (201 KB, 13 requests), Optimizely (96 KB, 170 ms blocking) and LaunchDarkly (11 requests), plus fonts from both Adobe Fonts and Google Fonts.Source