The product page promises "No effect on page speed or Core Web Vitals", and the homepage asks prospects "Which image is slowing load time on mobile?". But Google's data shows shuttlebase.com itself fails Core Web Vitals: real visitors wait 3.2s for the main content (the target is 2.5s), the phone test scores 36/100 with 6.1 MB downloaded, and the site's own snippet adds about half a second of blocking. Every technical buyer who runs PageSpeed on the vendor before a demo sees this first.
First action
Run PageSpeed on the homepage and list the first five assets that load before the hero text.
How to measure it
Chrome UX Report LCP
- Now
- –
- Target
- under 2.5s
- By
- 60 days
Steps
Baseline
PageSpeed and Chrome UX Report numbers for homepage, product and case studies.
Senior Software Engineer 1 hour
Find the heavy assets
Which of the 56 Webflow requests load before the hero paragraph.
Senior Software Engineer 1 day
Defer the animation
Load the scroll animation and video after the hero renders.
Senior Software Engineer 2 days
Fix render blocking
Inline critical CSS, preload the hero font, defer chat and consent scripts.
Senior Software Engineer 2 days
Load the snippet as advised
Async, with the same settings customers get.
Staff Software Engineer 1 day
Retest
Lab and field numbers after 28 days of traffic.
Senior Software Engineer 4 weeks
Publish the proof page
Before and after, method and the snippet's own cost.
Co-founder 2 days
Use it in sales
Link from the product page claim and AE follow-ups.
VP Sales ongoing
Why it works
Cut the homepage to what the hero needs: stop the 5.3 MB of Webflow animation and image assets loading before the hero text, defer the scroll animation and chat, load the snippet the way customers are told to, and preload the font the hero paragraph uses. Then publish a short page, "What our script costs your Core Web Vitals", with PageSpeed and Chrome UX Report numbers before and after, and link it from the "Zero performance impact" claim and from AE follow-up emails.
Shuttlebase sells measured improvement to people who will measure the vendor. A passing site turns the most likely objection ("will your script slow my store?") into proof, and the page gives the sales team something to send instead of an assurance.
Ready to use
ChecklistHomepage speed fix list
[ ] Baseline PageSpeed + CrUX for /, /product, /case-studies [ ] Hero text renders before any animation asset [ ] Scroll animation and video lazy-loaded [ ] Hero font preloaded, critical CSS inlined [ ] Chat, consent and HubSpot deferred [ ] Snippet loaded async, as in customer docs [ ] Proof page with before/after numbers [ ] Link from "Zero performance impact"
Risks and how to handle them
Field data takes 28 days to move
Publish lab numbers first and update with field data.
Design team wants the animation
Keep it, but load it after the hero text.
Evidence
- Google PageSpeedHomepage on mobile (tested October 20, 2026): performance score 36/100; the main content (the hero paragraph "Shuttlebase is an autonomous AI platform trained on millions of real conversions...") appears after 6.7s in the lab, against a 2.5s target; total blocking time 3.3s; 6.1 MB over 99 requests, 5.3 MB of it from 56 Webflow asset requests; render-blocking requests cost about 1.3s; the site's own snippet adds about 0.5s of blocking. Real Chrome visitors: LCP 3.2s at the 75th percentile, so the page fails Core Web Vitals on LCP (INP 181 ms passes).Source
- Your websiteProduct page, "Secure by design": "Zero performance impact. Lightweight script. No effect on page speed or Core Web Vitals." Also "60 second integration. Any platform." and "Experiments are built from your guidelines and policies".Source
- Your websiteHomepage: H1 "Growth, not guesswork"; the problem section asks "Which image is slowing load time on mobile?"; a "See what's broken on your site" box takes a website address for "an analysis of your website", and the confirmation says "We'll be in touch to set up a demo". Results shown: Larroude "$1.5M", DefenAge +30% revenue per visitor, Yaneken +30% conversion.Source
- Your websiteContent hub post "Everything You Need to Know About Page Speed While A/B Testing" (July 22, 2026): LCP of "2.5 seconds or faster" is "good"; bounce probability rises 32% as load time goes from one to three seconds and 90% at five seconds; Core Web Vitals have been part of Google ranking since June 2021.Source