3xvoice sells "never miss another call", but its own front door is slow to answer. In Google's phone test the hero paragraph appears after 37.4 seconds (the target is 2.5), the page is interactive after 67 seconds and it weighs 13.1 MB. Of that, 12.3 MB is third-party, and the largest single piece is the embedded Calendly scheduler: 6.6 MB, 25 requests and 2.8 seconds of blocked main thread, loaded for every visitor whether or not they ever book. Payment, analytics and survey scripts load before anyone has asked for a slot. There is no real-visitor data for the site yet, so these are lab numbers, but the booking widget is the only way to buy.
First action
Open the PageSpeed report on a phone profile and confirm the Calendly and YouTube rows, then swap the inline embed for a button.
How to measure it
Mobile LCP in the lab test; visit-to-booking rate
- Now
- –
- Target
- Main text under 2.5 seconds; booking rate tracked weekly against the current baseline
- By
- 30 days
Steps
Record the baseline
Save today's phone and desktop PageSpeed results and the last 30 days of Calendly bookings.
Founder 1 hour
Swap the embed for a button
Replace the inline Calendly widget with a button that opens the scheduler only on click.
Web developer half a day
Make the video click-to-play
Show a thumbnail and load the YouTube player only when it is pressed.
Web developer 2 hours
Check what still loads
Confirm the payment, analytics and survey scripts no longer load on first paint.
Web developer 1 hour
Re-test on a phone
Run PageSpeed three times and keep the median; test booking end to end on a real handset.
Founder 1 hour
Track bookings
Add an event for button clicks and completed bookings, and compare four weeks before and after.
Founder 4 weeks
Why it works
Replace the inline scheduler with a plain "Book a 30-minute demo" button that loads Calendly only when it is clicked (a popup, or a link to the booking page). Do the same for the YouTube player with a thumbnail that loads the player on click. Then re-run the phone test and record the before and after: page weight, time to main text and blocking time. Nothing about the offer changes; the visitor simply sees the pitch in a couple of seconds instead of waiting on a calendar they have not asked for.
Most service-business owners will open the page on a phone, often from an ad or a message. A page whose text arrives late loses them before the pitch starts, and a slow page is a poor advertisement for a product whose promise is instant response. Loading the scheduler on intent removes about half the page weight without removing the booking step.
Ready to use
ChecklistHomepage speed checklist
[ ] Baseline saved: 30/100 phone, 37.4 s to main text, 13.1 MB [ ] Inline scheduler replaced by a button that loads Calendly on click [ ] YouTube player replaced by a thumbnail that loads on click [ ] Payment, analytics and survey scripts absent on first load [ ] Booking tested end to end on a phone [ ] Phone test re-run three times, median recorded [ ] Click and booking events tracked
Risks and how to handle them
A click adds a step before the calendar appears
Keep the button above the fold and repeat it after each section; measure clicks and completions.
Lab numbers differ from real visits
Treat the lab test as a direction and watch real-visitor data once Google has enough traffic to report it.
Evidence
- PageSpeedGoogle PageSpeed lab test of the homepage (November 15, 2026): performance 30/100 on a phone and 36/100 on desktop. In the phone test the main text (the hero paragraph beginning "We build AI receptionists and automations that answer every call 24/7") appears after 37.4 seconds against a 2.5-second target (4.8 seconds on desktop), and the page is interactive after 67 seconds. The page weighs 13.1 MB over 101 requests. There is no real-visitor (field) data for the site yet, so these are lab numbers, not measured visits.Source
- PageSpeedWhere the weight is (same PageSpeed test): 12.3 MB of the 13.1 MB comes from third parties. The Calendly scheduler is 6.6 MB over 25 requests and blocks the main thread for 2.8 seconds; one Cloudinary file is 2.1 MB; the YouTube player is 1.0 MB over 10 requests. Payment, analytics, survey and messaging scripts (Stripe 570 KB, Segment 249 KB, plus Braze, Sprig, Survicate and reCAPTCHA) also load before a visitor has asked to book. Google estimates 4.0 MB of unused JavaScript (about 3.5 seconds) and about 1.1 seconds lost to short cache lifetimes.Source
- Your websiteHomepage (checked November 16, 2026): title "3xvoice — AI Receptionists & Automation for Growing Businesses"; description "Never miss another call. 3xvoice AI receptionists answer every call 24/7, book appointments directly into your calendar, and automate follow-ups. Built for service businesses of every kind." The routes to a conversation are an embedded Calendly scheduler (a 30-minute demo) and [email protected]; the research crawl found no phone number, live chat, newsletter or intake form on the page.Source