Tools & Wizards About Us
myschedule.is screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

myschedule.is

MySchedule.Is - availability calendar for businesses and sales teams

Page Load Speed

5.9 sec in total

First Response

141 ms

Resources Loaded

1.4 sec

Page Rendered

4.3 sec

myschedule.is screenshot

About Website

Visit myschedule.is now to see the best up-to-date My Schedule content and also check out these interesting facts you probably never knew about myschedule.is

MySchedule Is an availability calendar for businesses and sales teams. Our free online scheduling tool lets users schedule appointments easily and simply.

Visit myschedule.is

Key Findings

We analyzed Myschedule.is page load time and found that the first response time was 141 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

myschedule.is performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value9,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

myschedule.is

141 ms

40 ms

myschedule.is

23 ms

css

111 ms

bootstrap.css

45 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 89% of them (41 requests) were addressed to the original Myschedule.is, 7% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (672 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.4 kB (26%)

Content Size

1.1 MB

After Optimization

849.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myschedule.is main page is 1.1 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. 70% of websites need less resources to load. Images take 953.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 41.2 kB

  • Original 47.9 kB
  • After minification 26.9 kB
  • After compression 6.7 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. This page needs HTML code to be minified as it can gain 21.0 kB, which is 44% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.2 kB or 86% of the original size.

Image Optimization

-24%

Potential reduce by 229.9 kB

  • Original 953.1 kB
  • After minification 723.2 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. Obviously, My Schedule needs image optimization as it can save up to 229.9 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 13.9 kB

  • Original 83.4 kB
  • After minification 83.4 kB
  • After compression 69.5 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 13.9 kB or 17% of the original size.

CSS Optimization

-11%

Potential reduce by 6.5 kB

  • Original 56.9 kB
  • After minification 56.9 kB
  • After compression 50.4 kB

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. Myschedule.is needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Schedule. 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 from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

myschedule.is

myschedule.is

141 ms

40 ms

myschedule.is

myschedule.is

23 ms

css

css

111 ms

bootstrap.css

bootstrap.css

45 ms

fontawesome-all.css

fontawesome-all.css

83 ms

swiper.css

swiper.css

81 ms

magnific-popup.css

magnific-popup.css

80 ms

styles.css

styles.css

98 ms

wizard-style.css

wizard-style.css

94 ms

modernizr.js

modernizr.js

100 ms

jquery.min.js

jquery.min.js

99 ms

popper.min.js

popper.min.js

95 ms

bootstrap.min.js

bootstrap.min.js

510 ms

jquery.easing.min.js

jquery.easing.min.js

106 ms

swiper.min.js

swiper.min.js

388 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

103 ms

validator.min.js

validator.min.js

387 ms

scripts.js

scripts.js

102 ms

common_scripts.js

common_scripts.js

491 ms

velocity.min.js

velocity.min.js

475 ms

functions.js

functions.js

473 ms

survey_func.js

survey_func.js

473 ms

gtm.js

gtm.js

672 ms

logo05.png

logo05.png

355 ms

feature01.png

feature01.png

399 ms

Gmailvisual.png

Gmailvisual.png

400 ms

feature02.png

feature02.png

400 ms

feature03.png

feature03.png

398 ms

feature05.png

feature05.png

357 ms

feature06.png

feature06.png

356 ms

feature07.png

feature07.png

412 ms

feature08.png

feature08.png

411 ms

feature09.png

feature09.png

410 ms

testimonial-1.jpg

testimonial-1.jpg

411 ms

testimonial-2.jpg

testimonial-2.jpg

407 ms

testimonial-3.jpg

testimonial-3.jpg

594 ms

testimonial-4.jpg

testimonial-4.jpg

427 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

402 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

570 ms

fa-solid-900.woff

fa-solid-900.woff

408 ms

fa-regular-400.woff

fa-regular-400.woff

403 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

572 ms

fa-brands-400.woff

fa-brands-400.woff

407 ms

up-arrow.png

up-arrow.png

105 ms

csrf_token

csrf_token

262 ms

Accessibility Review

myschedule.is accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA progressbar elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

myschedule.is best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

myschedule.is SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myschedule.is 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 Myschedule.is 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.

Social Sharing Optimization

myschedule.is

Open Graph description is not detected on the main page of My Schedule. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: