6.9 sec in total
241 ms
6.1 sec
557 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 241 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
calend.ly performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value16.7 s
0/100
25%
Value45.5 s
0/100
10%
Value56,800 ms
0/100
30%
Value0.01
100/100
15%
Value85.8 s
0/100
10%
241 ms
252 ms
263 ms
393 ms
395 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Calend.ly, 26% (12 requests) were made to Assets-marketing-site.calendly.com and 6% (3 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Ws.zoominfo.com.
Page size can be reduced by 283.6 kB (81%)
351.3 kB
67.7 kB
In fact, the total size of Calend.ly main page is 351.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 331.5 kB which makes up the majority of the site volume.
Potential reduce by 281.9 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 281.9 kB or 85% of the original size.
Potential reduce by 0 B
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 1.7 kB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.7 kB or 16% of the original size.
Number of requests can be reduced by 13 (33%)
40
27
The browser has sent 40 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 14 to 1 for JavaScripts and as a result speed up the page load time.
calendly.com
241 ms
de706f7d0eb81ea8.js
252 ms
19947277778.js
263 ms
polyfill-c734fa5adaf166bb7646.js
393 ms
app-4c12208f014159f55656.js
395 ms
framework-43e73185bb9ffc078b46.js
393 ms
webpack-runtime-36c55e66ba05b0f34067.js
392 ms
gtm.js
219 ms
EBay_logo.svg
218 ms
Vector.svg
218 ms
Compass__2_.svg
301 ms
Twilio-logo-red.svg
343 ms
Company_logo.svg
352 ms
dollar-sign.svg
356 ms
refresh-ccw.svg
349 ms
Agreement-Icon.svg
353 ms
users.svg
351 ms
clock.svg
342 ms
trending-up.svg
361 ms
smile.svg
358 ms
Positive-Review-1.svg
361 ms
Search-Person-Icon.svg
353 ms
Timed-Meeting-Icon.svg
356 ms
Job-Icon__2_.svg
355 ms
Security-Icon.svg
364 ms
Happy-Laptop-Icon.svg
366 ms
Marketing_Solution_Icon.svg
364 ms
Meeting-Time-Icon.svg
365 ms
Education_Solution_Icon.svg
404 ms
VonageLogo.svg
400 ms
check.svg
401 ms
AppStore-15f01eefb2013206cc7e26d98fbe95fb.svg
139 ms
Gilroy-Medium-a46ff9656a37256d62e8a086e4b2f766.woff
245 ms
Gilroy-Regular-e0879529bc261e7247c6e4a4b6f670c7.woff
204 ms
Gilroy-SemiBold-07559043612d8f26cd8b4e62c5de57ca.woff
319 ms
Gilroy-Bold-20091a5334cb2a0c9f97fa58bfbdcd22.woff
204 ms
Gilroy-ExtraBold-991e2eae044b7eb5e1b6ed1e6e521ed8.woff
245 ms
Gilroy-Black-a7017ba231ab8dc770e0534ccd330e2a.woff
252 ms
c8re6amimz
5117 ms
c8re6amimz
5133 ms
62d762a3bfe14c008f0eec2d
5152 ms
Banner_-_Split__3_.png
16 ms
otSDKStub.js
74 ms
a838c8e4-e3ce-442e-8f96-c88d0af98990.json
8 ms
location
67 ms
otBannerSdk.js
12 ms
clarity.js
39 ms
calend.ly accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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
Image elements do not have [alt] attributes
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: