Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

mercy.net

Mercy | Doctors, Hospitals & Clinics in MO, AR, OK & KS

Page Load Speed

3.8 sec in total

First Response

895 ms

Resources Loaded

2.7 sec

Page Rendered

153 ms

mercy.net screenshot

About Website

Click here to check amazing Mercy content for United States. Otherwise, check out these important facts you probably never knew about mercy.net

Mercy is one of the largest U.S. health systems with 44 acute care & specialty hospitals, over 700 physician & outpatient clinics in Arkansas, Kansas, Missouri & Oklahoma.

Visit mercy.net

Key Findings

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

Performance Metrics

mercy.net performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value3,170 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

www.mercy.net

895 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

112 ms

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

112 ms

css_wIrZJwFIBbyzDeV3-pyBtCyR_V33U6ZKMx4mTG_-r0Q.css

145 ms

css_rbEZwsbo05Esss66HGibG_7xlGlzF3XWKJSCn03tyCM.css

121 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 71% of them (40 requests) were addressed to the original Mercy.net, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (976 ms) belongs to the original domain Mercy.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 446.6 kB (11%)

Content Size

4.0 MB

After Optimization

3.6 MB

In fact, the total size of Mercy.net main page is 4.0 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. 30% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.6 kB

  • Original 45.3 kB
  • After minification 43.1 kB
  • After compression 9.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. 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 35.6 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 46.3 kB

  • Original 3.5 MB
  • After minification 3.4 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. Mercy images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 242.4 kB

  • Original 341.3 kB
  • After minification 252.0 kB
  • After compression 98.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 242.4 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 122.3 kB

  • Original 150.2 kB
  • After minification 147.6 kB
  • After compression 27.9 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. Mercy.net needs all CSS files to be minified and compressed as it can save up to 122.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (46%)

Requests Now

48

After Optimization

26

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

Accessibility Review

mercy.net accessibility score

91

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

mercy.net 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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mercy.net SEO score

92

Search Engine Optimization Advices

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 Mercy.net 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 Mercy.net 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 data is detected on the main page of Mercy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: