Tools & Wizards About Us
mychart.rush.edu screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

mychart.rush.edu

MyChart - Application Error Page

Page Load Speed

25.5 sec in total

First Response

363 ms

Resources Loaded

15.4 sec

Page Rendered

9.8 sec

mychart.rush.edu screenshot

About Website

Visit mychart.rush.edu now to see the best up-to-date My Chart Rush content for United States and also check out these interesting facts you probably never knew about mychart.rush.edu

Visit mychart.rush.edu

Key Findings

We analyzed Mychart.rush.edu page load time and found that the first response time was 363 ms and then it took 25.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

mychart.rush.edu performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

363 ms

common.css

256 ms

prelogin.css

359 ms

component.css

721 ms

colors.css

661 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 93% of them (89 requests) were addressed to the original Mychart.rush.edu, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Mychart.rush.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (44%)

Content Size

2.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mychart.rush.edu main page is 2.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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 13.4 kB

  • Original 17.4 kB
  • After minification 17.3 kB
  • After compression 4.0 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 13.4 kB or 77% of the original size.

Image Optimization

-13%

Potential reduce by 152.4 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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 Chart Rush needs image optimization as it can save up to 152.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 701.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 334.2 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 701.9 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 302.9 kB

  • Original 366.2 kB
  • After minification 273.8 kB
  • After compression 63.3 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. Mychart.rush.edu needs all CSS files to be minified and compressed as it can save up to 302.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 82 (90%)

Requests Now

91

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Chart Rush. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

363 ms

common.css

common.css

256 ms

prelogin.css

prelogin.css

359 ms

component.css

component.css

721 ms

colors.css

colors.css

661 ms

themes.css

themes.css

604 ms

externalcolors.css

externalcolors.css

685 ms

jquery-2.2.2.min.js

jquery-2.2.2.min.js

748 ms

jqwrappers.min.js

jqwrappers.min.js

1300 ms

handlebars.runtime.min.js

handlebars.runtime.min.js

1050 ms

common.min.js

common.min.js

1287 ms

prelogin.min.js

prelogin.min.js

1036 ms

core.min.js

core.min.js

1060 ms

debug.min.js

debug.min.js

1036 ms

i18n.min.js

i18n.min.js

2103 ms

formats

formats

2147 ms

pagestartup.min.js

pagestartup.min.js

2146 ms

prelogin.min.js

prelogin.min.js

2146 ms

formvalidation.min.js

formvalidation.min.js

2101 ms

utilities.min.js

utilities.min.js

2246 ms

communityutilities.min.js

communityutilities.min.js

2200 ms

simpletemplates.min.js

simpletemplates.min.js

2209 ms

strings.min.js

strings.min.js

2244 ms

commonutils.min.js

commonutils.min.js

2311 ms

intkeepalive.min.js

intkeepalive.min.js

2212 ms

wp.events.min.js

wp.events.min.js

2569 ms

dateformat.min.js

dateformat.min.js

2568 ms

wp.comm.min.js

wp.comm.min.js

3097 ms

wp.utils.min.js

wp.utils.min.js

2532 ms

mychartjsstrings.min.js

mychartjsstrings.min.js

3336 ms

wp.dom.min.js

wp.dom.min.js

3130 ms

wp.controls.min.js

wp.controls.min.js

3228 ms

wp.controls.menu.min.js

wp.controls.menu.min.js

3229 ms

effects.min.js

effects.min.js

3252 ms

wp.strings.min.js

wp.strings.min.js

3150 ms

jqueryextensions.min.js

jqueryextensions.min.js

3334 ms

calendars.css

calendars.css

3174 ms

Override.css

Override.css

3165 ms

handlebarshelpers.min.js

handlebarshelpers.min.js

2803 ms

behaviors.min.js

behaviors.min.js

3246 ms

loggingout.tmpl.min.js

loggingout.tmpl.min.js

3187 ms

buttonbar.tmpl.min.js

buttonbar.tmpl.min.js

3124 ms

overlay.tmpl.min.js

overlay.tmpl.min.js

2818 ms

loading.tmpl.min.js

loading.tmpl.min.js

2765 ms

externaljump.tmpl.min.js

externaljump.tmpl.min.js

2780 ms

scrollbarwidth.tmpl.min.js

scrollbarwidth.tmpl.min.js

2780 ms

externalorganizationicon.tmpl.min.js

externalorganizationicon.tmpl.min.js

2757 ms

externalloadingindicator.tmpl.min.js

externalloadingindicator.tmpl.min.js

2532 ms

controller.min.js

controller.min.js

2337 ms

component.min.js

component.min.js

1798 ms

viewcomponent.min.js

viewcomponent.min.js

2007 ms

vb6component.min.js

vb6component.min.js

2002 ms

templatecomponent.min.js

templatecomponent.min.js

2003 ms

inlineloadingcomponent.min.js

inlineloadingcomponent.min.js

1999 ms

inlineloadingwithsourcescomponent.min.js

inlineloadingwithsourcescomponent.min.js

2014 ms

externaljumppopupcomponent.min.js

externaljumppopupcomponent.min.js

2007 ms

confirmcomponent.min.js

confirmcomponent.min.js

2003 ms

containercomponent.min.js

containercomponent.min.js

1971 ms

positions.min.js

positions.min.js

1986 ms

popup.min.js

popup.min.js

1703 ms

panel.min.js

panel.min.js

1701 ms

calendar.tmpl.min.js

calendar.tmpl.min.js

1906 ms

calendar.min.js

calendar.min.js

1379 ms

multimonthcalendar.min.js

multimonthcalendar.min.js

1427 ms

calendars.min.js

calendars.min.js

1396 ms

wp.validators.min.js

wp.validators.min.js

1447 ms

htmltemplatecontainer.min.js

htmltemplatecontainer.min.js

1459 ms

safetoredirectcomponent.min.js

safetoredirectcomponent.min.js

1459 ms

timeoutwarningcomponent.min.js

timeoutwarningcomponent.min.js

1491 ms

loggingoutcomponent.min.js

loggingoutcomponent.min.js

1469 ms

messagecomponent.min.js

messagecomponent.min.js

1468 ms

signup_login.min.js

signup_login.min.js

1468 ms

override.css

override.css

250 ms

prelogin.jpg

prelogin.jpg

2377 ms

warning.png

warning.png

819 ms

badge_apple.png

badge_apple.png

964 ms

badge_android.png

badge_android.png

963 ms

gtm.js

gtm.js

2381 ms

gtm.js

gtm.js

2511 ms

prelogin_blurred.jpg

prelogin_blurred.jpg

1422 ms

loginlogo.png

loginlogo.png

1421 ms

medical_advice.png

medical_advice.png

1422 ms

test_results.png

test_results.png

1420 ms

medications.png

medications.png

1421 ms

calendar.png

calendar.png

1421 ms

sourcesanspro-regular-webfont.woff

sourcesanspro-regular-webfont.woff

176 ms

sourcesanspro-semibold-webfont.woff

sourcesanspro-semibold-webfont.woff

175 ms

sourcesanspro-it-webfont.woff

sourcesanspro-it-webfont.woff

120 ms

sourcesanspro-semiboldit-webfont.woff

sourcesanspro-semiboldit-webfont.woff

120 ms

analytics.js

analytics.js

1356 ms

highcontrast.css

highcontrast.css

530 ms

print.css

print.css

1906 ms

collect

collect

512 ms

collect

collect

673 ms

collect

collect

282 ms

ga-audiences

ga-audiences

361 ms

Accessibility Review

mychart.rush.edu accessibility score

100

Accessibility Issues

Best Practices

mychart.rush.edu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

mychart.rush.edu SEO score

90

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

High

Tap targets are not sized appropriately

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 Mychart.rush.edu 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 Mychart.rush.edu 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

mychart.rush.edu

Open Graph description is not detected on the main page of My Chart Rush. 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: