Does Calendly slow down your landing page? An inline embed can. A button that opens it on click is gentler.

What the data shows for Calendly

The numbers here come from third-party-web, an open dataset by Patrick Hulce. It is built from HTTP Archive, which tests millions of pages with Google Lighthouse on mobile settings. Lighthouse records how long each script keeps the browser's main thread busy. The dataset adds that up for each company and divides by the number of pages that use it.

We used third-party-web version 0.30.0, published in September 2026, with the HTTP Archive crawl from March 1, 2026. For Calendly it reports:

• Average script execution time: 4,305 ms per page.
• Usage: 13,872 pages in the crawl.

That is one of the higher numbers in the data, closer to video players than to tracking tools. For comparison, the same crawl shows Google Tag Manager at 1,066 ms and CallRail at 255 ms. The dataset does not split it by embed style, so we can't tell you how inline compares to pop-up from this data. See the full list in third-party scripts and landing page speed.

What script execution time means for a phone visitor

A phone browser does most of its work in one lane, called the main thread. That lane builds the page, runs scripts, and answers taps. Only one job runs there at a time.

Google's Lighthouse docs say that when the main thread is busy, the page can't respond to user input. Lighthouse also warns when JavaScript on a page takes longer than 2 seconds to run. Google's Interaction to Next Paint (INP), a Core Web Vital, rates a tap's wait as good at 200 ms or less and poor above 500 ms.

An inline scheduler loads the whole calendar for every visitor, including the many who will just call. That work happens right when they are trying to find your phone number.

How to add Calendly the smart way

Online booking is a good thing to offer. Some homeowners would rather pick a time than talk. The goal is to offer it without making everyone pay for it.

1. Pick a lighter embed style

Calendly's help center lists three embed options:

• Inline embed: shows your scheduling page right on your website.
• Pop-up text: opens your scheduling page in a pop-up when a visitor clicks a link.
• Pop-up widget: a floating button on your page that opens a pop-up when selected.

With pop-up text, the scheduler opens on the visitor's click. On an ad page, a "Book a time" button that opens the pop-up keeps the calendar out of the way until someone asks for it. Scan before and after to see what it does on your page.

2. Or just link to it

Calendly also mentions adding a link to your scheduling page instead of an embed. A big button that opens your Calendly page is simple and works on any phone. The visitor leaves your page, but only when they have already chosen to book.

If you use the pop-up widget, check it on a phone. A floating button sits on top of the page. Make sure it does not cover your call button, your form, or the cookie banner's close button.

3. Keep the phone first

• Phone number at the top, tap-to-call on mobile.
• Short form for people who want a callback.
• Booking button as a third option, not the whole page.

For trade pages where urgent calls matter most, see HVAC landing pages and Google Ads for contractors.

Check the page before and after

The dataset shows averages across many sites. Your page is its own case. Scan with the inline embed, switch to a pop-up or link, then scan again.

ClickMend checks the page your Google Ad sends people to. It gives a 0 to 100 score that blends Google PageSpeed Insights performance (40%), Core Web Vitals (25%), SEO basics (20%), best practices (10%), and accessibility (5%). It names unused JavaScript and other slow parts. It also checks that your Google Ads conversion tag is on the page and loaded. If bookings happen on Calendly's page, make sure that conversion is tracked somewhere.

Scan the landing page free, 2 scans a week, no card. Paid plans show the fixes and add weekly monitoring with alerts when a page gets worse.

Frequently asked questions