Speechmatics sells "real-time speech-to-text in 350ms", but its homepage scores 45/100 on mobile. In Google's phone test the main element takes 11.8 seconds to appear, and that element is the cookie-consent text. Real visitors fail Google's responsiveness test (375 ms, the limit is 200 ms). The page loads 1.76 MB of JavaScript, a third of it unused, and 16 third-party services, including tags from X, Reddit, Bing and Spotify. The new Growth Engineer is hired to own exactly this: site speed and self-serve conversion.
First action
List which of the 16 third-party tools anyone reports on, and remove the rest.
How to measure it
Mobile homepage sign-up rate
- Now
- –
- Target
- +15%
- By
- 60 days
Steps
Audit tags
Owner and use for each of the 16 services.
Growth Engineer 1 day
Remove unused tags
Drop the ones with no owner.
Growth Engineer 1 day
Light cookie banner
Static HTML first, consent tool after.
Growth Engineer 3 days
Defer pixels
After consent and interaction.
Growth Engineer 2 days
Split the demo
Load the live demo on click.
Senior Software Engineer - Front-End 1 week
Budget in CI
Fail deploys over the JavaScript budget.
Growth Engineer 2 days
Measure
Field INP and sign-ups weekly.
Growth Engineer weekly
Why it works
Render the cookie banner as light HTML before Cookiebot loads, load marketing pixels only after consent and after the page is interactive, remove the tags no one reports on, split the homepage JavaScript so the live transcription demo loads on click, and set a performance budget checked on every Vercel deploy.
Developers judge an API company by its site, and the self-serve funnel starts on this page; a faster page lifts sign-ups and stops the site from contradicting the latency pitch.
Ready to use
ChecklistHomepage speed list
[ ] Owner named for each third-party service [ ] Unused tags removed [ ] Cookie banner rendered as static HTML [ ] Ad and social pixels after consent and interaction [ ] Live demo JavaScript loaded on click [ ] JavaScript budget enforced on deploy [ ] Field INP under 200 ms
Risks and how to handle them
Losing attribution data
Keep the tags that feed reports, loaded after consent.
Consent compliance
Have legal review the banner change.
Evidence
- Google PageSpeedHomepage, tested October 22, 2026: mobile performance 45/100 (desktop 57); in the phone lab test the largest element takes 11.8 seconds to appear and it is the cookie-consent text; total blocking time 692 ms. Real Chrome visitors fail Core Web Vitals on responsiveness (INP 375 ms; the "good" limit is 200 ms), while their load time passes (LCP 2.15 s). The page makes 163 requests with 1.76 MB of JavaScript, about 637 KB of it unused, and loads 16 third-party services (about 1 MB), including Google Tag Manager (545 KB), Cookiebot (204 KB), X/Twitter (132 KB), Clarity, Reddit, Bing Ads and a Spotify pixel.Source
- HiringGrowth Engineer (Belgrade, posted October 1, 2026): owns "the backend development and ongoing health of the Speechmatics website and self-serve portal", Vercel deployments, Python queries on the self-serve portal, "opportunities to improve conversion across the self-serve funnel", and "the ongoing improvement of site performance, loading speed, and technical reliability".Source
- Your websiteHomepage: "Speech APIs powering Voice AI"; "Multilingual speech-to-text built for regulated industries"; "Real-time speech-to-text in 350ms"; "55+ languages, one model"; HIPAA, GDPR, SOC 2 Type II and ISO 27001; on-device, on-prem or cloud; "We don't log your data as standard". Case studies: AI-Media ("Delivering 120X more"), LiveKit ("Enabling 100,000+ developers"), Adobe (on-device in Premiere), NCI ("99% increase in usage of automated captioning"), Media Track ("20% leap in accuracy"), Prosodica and Stenograph. A banner introduces "Oak, our new medical model built for multilingual consultations".Source