Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

nmdi.org

Munson Healthcare

Page Load Speed

6.6 sec in total

First Response

28 ms

Resources Loaded

5.8 sec

Page Rendered

782 ms

nmdi.org screenshot

About Website

Visit nmdi.org now to see the best up-to-date Nmdi content and also check out these interesting facts you probably never knew about nmdi.org

Munson Healthcare, based in Traverse City, Mich., is northern Michigan’s largest health care system with nine award-winning community hospitals.

Visit nmdi.org

Key Findings

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

Performance Metrics

nmdi.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value26,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value43.0 s

0/100

10%

Network Requests Diagram

nmdi.org

28 ms

128 ms

nmdi

7 ms

diabetes-care

466 ms

font-awesome.min.css

405 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Nmdi.org, 34% (35 requests) were made to Munsonhealthcare.org and 10% (10 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Munsonhealthcare.org.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

2.2 MB

In fact, the total size of Nmdi.org main page is 3.4 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 77.7 kB

  • Original 129.1 kB
  • After minification 110.7 kB
  • After compression 51.4 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 18.4 kB, which is 14% 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.7 kB or 60% of the original size.

Image Optimization

-26%

Potential reduce by 609.7 kB

  • Original 2.4 MB
  • After minification 1.8 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, Nmdi needs image optimization as it can save up to 609.7 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 169.4 kB

  • Original 431.2 kB
  • After minification 422.9 kB
  • After compression 261.9 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 169.4 kB or 39% of the original size.

CSS Optimization

-71%

Potential reduce by 329.5 kB

  • Original 465.9 kB
  • After minification 461.3 kB
  • After compression 136.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. Nmdi.org needs all CSS files to be minified and compressed as it can save up to 329.5 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (68%)

Requests Now

81

After Optimization

26

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

Accessibility Review

nmdi.org accessibility score

81

Accessibility Issues

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

nmdi.org best practices score

58

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

Displays images with incorrect aspect ratio

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

nmdi.org SEO score

87

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nmdi.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nmdi.org 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

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