Tools & Wizards About Us
mymontefiore.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

mymontefiore.com

Patients and Visitors - Manage Your Health Online - Montefiore Medical Center

Page Load Speed

15.2 sec in total

First Response

1 sec

Resources Loaded

11.2 sec

Page Rendered

3 sec

mymontefiore.com screenshot

About Website

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

Staying in touch with your doctor just got easier: anytime, anywhere, from any Internet connection. It’s easy, secure and for your non-urgent needs, you may even save yourself an office visit.

Visit mymontefiore.com

Key Findings

We analyzed Mymontefiore.com page load time and found that the first response time was 1 sec and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

mymontefiore.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.341

33/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

mymontefiore.com

1026 ms

responsive-body_dropdown.cfm

253 ms

mychart

1156 ms

gtm.js

315 ms

gtm.js

455 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mymontefiore.com, 43% (40 requests) were made to Montefiore.org and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Montefiore.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.2 kB (16%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mymontefiore.com main page is 1.5 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. 75% 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 77.5 kB

  • Original 101.2 kB
  • After minification 89.9 kB
  • After compression 23.6 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 11.2 kB, which is 11% 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 77.5 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 83.1 kB

  • Original 1.0 MB
  • After minification 957.0 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. My Montefiore images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 62.1 kB

  • Original 308.6 kB
  • After minification 295.7 kB
  • After compression 246.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 62.1 kB or 20% of the original size.

CSS Optimization

-22%

Potential reduce by 10.4 kB

  • Original 46.5 kB
  • After minification 44.9 kB
  • After compression 36.1 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. Mymontefiore.com needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (61%)

Requests Now

88

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mymontefiore.com

mymontefiore.com

1026 ms

responsive-body_dropdown.cfm

responsive-body_dropdown.cfm

253 ms

mychart

mychart

1156 ms

gtm.js

gtm.js

315 ms

gtm.js

gtm.js

455 ms

jquery.min.js

jquery.min.js

136 ms

jquery-ui.min.js

jquery-ui.min.js

212 ms

jquery.ui.core.js

jquery.ui.core.js

48 ms

jquery.ui.widget.js

jquery.ui.widget.js

93 ms

jquery.ui.mouse.js

jquery.ui.mouse.js

85 ms

jquery.ui.accordion.js

jquery.ui.accordion.js

100 ms

0a9584333e.js

0a9584333e.js

285 ms

BrowserDetect-min.js

BrowserDetect-min.js

99 ms

main-min.css

main-min.css

100 ms

basis-stylesheet.css

basis-stylesheet.css

99 ms

MyFontsWebfontsKit.css

MyFontsWebfontsKit.css

98 ms

jquery-ui.css

jquery-ui.css

289 ms

responsive_supplemental.css

responsive_supplemental.css

188 ms

publicGeneral.js

publicGeneral.js

191 ms

modernizr.js

modernizr.js

189 ms

frontEnd-min.js

frontEnd-min.js

281 ms

buttons.js

buttons.js

183 ms

slick.min.js

slick.min.js

188 ms

analytics.js

analytics.js

693 ms

fbevents.js

fbevents.js

3523 ms

bat.js

bat.js

2561 ms

conversion_async.js

conversion_async.js

3823 ms

insight.min.js

insight.min.js

3837 ms

scevent.min.js

scevent.min.js

3745 ms

pixel.js

pixel.js

3737 ms

js

js

713 ms

js

js

2293 ms

js

js

835 ms

cse.js

cse.js

3608 ms

62L7W-X8NB3-QS7TG-WMVKQ-94FHQ

62L7W-X8NB3-QS7TG-WMVKQ-94FHQ

3604 ms

button_topnav_findADoctor.gif

button_topnav_findADoctor.gif

353 ms

MONTE-LOGO-PLAIN.JPG

MONTE-LOGO-PLAIN.JPG

351 ms

ME-my-chart-logo.png

ME-my-chart-logo.png

351 ms

banner-image.png

banner-image.png

350 ms

banner-tablet-image.png

banner-tablet-image.png

350 ms

my-chart-illustration.png

my-chart-illustration.png

345 ms

VIDEO_POSTER_DESKTOP.PNG

VIDEO_POSTER_DESKTOP.PNG

3754 ms

VIDEO_POSTER_TABLET.PNG

VIDEO_POSTER_TABLET.PNG

617 ms

VIDEO_POSTER_PHONEPNG.PNG

VIDEO_POSTER_PHONEPNG.PNG

595 ms

mychart-image1.png

mychart-image1.png

596 ms

mychart-image2.png

mychart-image2.png

596 ms

mychart-image-3.png

mychart-image-3.png

615 ms

TWO_PHONES.SVG

TWO_PHONES.SVG

2303 ms

mychart-image-4.png

mychart-image-4.png

2304 ms

video-visits-app-icon.jpg

video-visits-app-icon.jpg

2304 ms

DOWNLOAD-ON-THE-APP-STORE-BADGE-1.PNG

DOWNLOAD-ON-THE-APP-STORE-BADGE-1.PNG

3043 ms

2000px-Get_it_on_Google_play.svg.png

2000px-Get_it_on_Google_play.svg.png

3264 ms

footer-icon-facebook.gif

footer-icon-facebook.gif

3589 ms

footer-icon-twitter.gif

footer-icon-twitter.gif

3590 ms

footer-icon-youtube.gif

footer-icon-youtube.gif

3590 ms

footer-icon-share-text.gif

footer-icon-share-text.gif

3591 ms

monte-einstein-lockup.png

monte-einstein-lockup.png

3743 ms

systemnav-bkg.gif

systemnav-bkg.gif

3856 ms

espanol.gif

espanol.gif

3871 ms

events.js

events.js

3742 ms

collect

collect

2793 ms

collect

collect

3453 ms

collect

collect

3420 ms

fontello.woff

fontello.woff

3119 ms

webengage-min-v-5.0.js

webengage-min-v-5.0.js

2066 ms

170292692.js

170292692.js

2059 ms

collect

collect

1212 ms

identity.js

identity.js

433 ms

2860654470886536

2860654470886536

722 ms

cse_element__en.js

cse_element__en.js

883 ms

default+en.css

default+en.css

992 ms

default.css

default.css

1023 ms

578 ms

rp.gif

rp.gif

885 ms

config.json

config.json

849 ms

ga-audiences

ga-audiences

442 ms

storage-frame-1.18.htm

storage-frame-1.18.htm

470 ms

465 ms

43 ms

v4.js

v4.js

570 ms

22 ms

widget.js

widget.js

519 ms

uwt.js

uwt.js

319 ms

collect

collect

93 ms

upf.js

upf.js

185 ms

adsct

adsct

257 ms

adsct

adsct

303 ms

results.txt

results.txt

244 ms

results.txt

results.txt

219 ms

l3.jpg

l3.jpg

105 ms

feedback-widget-close.png

feedback-widget-close.png

64 ms

1lbkil1.png

1lbkil1.png

105 ms

feedback-tab-bg-dark.png

feedback-tab-bg-dark.png

89 ms

Accessibility Review

mymontefiore.com accessibility score

80

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

mymontefiore.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mymontefiore.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Mymontefiore.com 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 Mymontefiore.com 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

mymontefiore.com

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