2.3 sec in total
202 ms
1.4 sec
619 ms
Visit calend.ly now to see the best up-to-date Calend content and also check out these interesting facts you probably never knew about calend.ly
Calendly is the modern scheduling platform that makes “finding time” a breeze. When connecting is easy, your teams can get more done.
Visit calend.lyWe analyzed Calend.ly page load time and found that the first response time was 202 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
calend.ly performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value25.4 s
0/100
25%
Value10.4 s
8/100
10%
Value4,040 ms
1/100
30%
Value0
100/100
15%
Value25.4 s
0/100
10%
202 ms
392 ms
60 ms
132 ms
90 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Calend.ly, 49% (39 requests) were made to Marketing-assets.calendly.com and 45% (36 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (493 ms) relates to the external source Marketing-assets.calendly.com.
Page size can be reduced by 774.7 kB (22%)
3.6 MB
2.8 MB
In fact, the total size of Calend.ly main page is 3.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 747.1 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 747.1 kB or 87% of the original size.
Potential reduce by 27.3 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Calend images are well optimized though.
Potential reduce by 328 B
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 10 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Calend.ly has all CSS files already compressed.
Number of requests can be reduced by 15 (20%)
74
59
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Calend. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
calend.ly
202 ms
calendly.com
392 ms
19947277778.js
60 ms
cbaf864379a71ae3.css
132 ms
fd9d1056-f17f06b5f49b17ab.js
90 ms
7023-2410d52f83a3e77a.js
95 ms
main-app-43c9c641be3b9874.js
95 ms
2291-40e20221e91c10cb.js
96 ms
8039-b8d4e02b2e9d2fba.js
369 ms
7224-8e43cbf0b7172faf.js
164 ms
layout-233e2beb85d22667.js
121 ms
layout-cd8615e510890522.js
368 ms
7a49ec60-5bbd31bb082c0efc.js
142 ms
0cc268aa-8660e9872589529e.js
157 ms
9678-ea9e9732d91b6396.js
388 ms
page-aec04ddb33ff7659.js
383 ms
polyfills-78c92fac7aa8fdd8.js
185 ms
webpack-05ba48bed726e5cc.js
358 ms
Calendly-Sales-new.png
177 ms
help.svg
268 ms
logo.svg
219 ms
hero-bkg-half-no-margin.png
175 ms
share-booking-page.8c823995.png
203 ms
reduce-no-shows.82b92664.png
179 ms
smith-ai-logo.svg
269 ms
hackerone-logo.svg
266 ms
airtable-logo.svg
203 ms
ci-assante-logo.svg
295 ms
texas-logo.svg
390 ms
bitly-logo.svg
343 ms
connect-your-calendars.png
323 ms
add-your-availability.png
362 ms
connect-conferencing-tools.png
488 ms
customize-event-types.png
317 ms
share-scheduling-link.png
396 ms
browser-extensions.png
425 ms
automated-workflows.png
373 ms
routing-forms.png
493 ms
round-robin-event-type.png
402 ms
admin-management.png
417 ms
Calendly-Demand-Gen.png
139 ms
Calendly-Customer-Success.png
122 ms
Calendly-Recruiting.png
124 ms
Calendly-IT.png
122 ms
Calendly-Education.png
126 ms
Zoom.svg
120 ms
google-calendar.svg
122 ms
Frame_29927.svg
129 ms
outlook.svg
125 ms
gmail-icon.svg
127 ms
Chrome.svg
128 ms
saleforce.svg
136 ms
hubspot.svg
136 ms
slack-logo-icon.svg
138 ms
activecampaign-logo-icon.svg
139 ms
webex-logomark-01.svg
146 ms
zapier-icon.svg
139 ms
Logomark.svg
143 ms
linkedin.svg
140 ms
stripe-logo.svg
143 ms
Logomark.svg
142 ms
Typeform-Icon.svg
151 ms
intercom.svg
151 ms
Calendly-Email-Embed-Recruiting.png
152 ms
Calendly-Round-Robin.png
167 ms
Calendly-Graph.png
153 ms
Security-SOC.svg
160 ms
Security-DSS.svg
152 ms
Security-GDPR.svg
155 ms
Security-CCPA.svg
158 ms
Security-Star.svg
164 ms
Sercurity-ISO-27001__1_.png
167 ms
smith-ai-customer-logo.svg
167 ms
clickup-customer-logo.svg
169 ms
hackerone-customer-logo.svg
168 ms
c961240f6e0cb057-s.p.woff
416 ms
7538d40b3ee19e6c-s.p.woff
342 ms
4409add9d9dd8f67-s.p.woff
431 ms
2d784c2a010765ed-s.p.woff
431 ms
main.js
86 ms
calend.ly accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
calend.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
calend.ly SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Calend.ly can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Calend.ly main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
calend.ly
Open Graph data is detected on the main page of Calend. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: