1.9 sec in total
204 ms
1.6 sec
102 ms
Welcome to mymercy.net homepage info - get ready to check My Mercy best content for United States right away, or after learning these important things about mymercy.net
Take your health with you: Schedule appointments, E-mail your doctor, Get lab results, Track your health history, Request prescription refills, Pay your bills online and much more
Visit mymercy.netWe analyzed Mymercy.net page load time and found that the first response time was 204 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
mymercy.net performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value16.1 s
0/100
25%
Value8.4 s
19/100
10%
Value650 ms
46/100
30%
Value0.001
100/100
15%
Value16.5 s
5/100
10%
204 ms
226 ms
119 ms
179 ms
92 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 94% of them (64 requests) were addressed to the original Mymercy.net, 3% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (833 ms) belongs to the original domain Mymercy.net.
Page size can be reduced by 690.1 kB (73%)
949.6 kB
259.5 kB
In fact, the total size of Mymercy.net main page is 949.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 686.9 kB which makes up the majority of the site volume.
Potential reduce by 7.1 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 7.1 kB or 76% of the original size.
Potential reduce by 465.1 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 465.1 kB or 68% of the original size.
Potential reduce by 217.8 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. Mymercy.net needs all CSS files to be minified and compressed as it can save up to 217.8 kB or 86% of the original size.
Number of requests can be reduced by 63 (97%)
65
2
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 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 59 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
mymercy.net
204 ms
bootstrap.min.css
226 ms
jquery.smartbanner.css
119 ms
wtf.css
179 ms
fontello.css
92 ms
animate.css
213 ms
font-awesome.css
183 ms
angular.min.js
329 ms
angular-ui-router.min.js
311 ms
scroll.min.js
279 ms
angular-animate.min.js
358 ms
angular-local-storage.min.js
355 ms
jquery.min.js
431 ms
ui-bootstrap-tpls.min.js
495 ms
api.js
33 ms
angular-recaptcha.min.js
416 ms
angular-cookies.min.js
416 ms
angular-gettext.min.js
472 ms
mask.min.js
478 ms
angular-idle.min.js
533 ms
underscore-min.js
562 ms
angulartics.min.js
537 ms
angulartics-google-analytics.min.js
554 ms
angular-sanitize.js
638 ms
jquery.smartbanner.js
634 ms
app.js
627 ms
routes.js
685 ms
config.js
657 ms
localStorageServiceProviderConfig.js
662 ms
constants.js
713 ms
login.js
752 ms
registration.js
779 ms
confirm_identity.js
745 ms
support.js
750 ms
support_request.js
770 ms
forgot_user_id.js
801 ms
forgot_password.js
830 ms
reset_password.js
833 ms
timeout.js
766 ms
keep_mymercy_alive.js
755 ms
logout.js
699 ms
add_dependent.js
754 ms
account_access.js
742 ms
grant_access.js
729 ms
emulate_user.js
672 ms
account_settings.js
654 ms
reset_temporary_password.js
614 ms
focus.js
672 ms
scroll_to_element.js
683 ms
mcy_form_submit.js
630 ms
mcy_recaptcha.js
634 ms
mcy_mref.js
608 ms
mcy_google_analytics.js
592 ms
loading.js
635 ms
recaptcha__en.js
95 ms
mcy_smart_banner.js
623 ms
user_input.js
596 ms
challenge_question_service.js
600 ms
target_url_service.js
582 ms
authentication_service.js
579 ms
recaptcha_service.js
568 ms
support_service.js
575 ms
password_validation_service.js
582 ms
keep_alive_service.js
570 ms
mychart_service.js
569 ms
profile_service.js
548 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
51 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
60 ms
mymercy.net accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
mymercy.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mymercy.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mymercy.net 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 Mymercy.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.
mymercy.net
Open Graph description is not detected on the main page of My Mercy. 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: