2.5 sec in total
713 ms
1.6 sec
214 ms
Visit monodisease.org now to see the best up-to-date Mono Disease content and also check out these interesting facts you probably never knew about monodisease.org
Mononucleosis Disease Medical Center
Visit monodisease.orgWe analyzed Monodisease.org page load time and found that the first response time was 713 ms and then it took 1.8 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.
monodisease.org performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value5.7 s
17/100
25%
Value5.4 s
57/100
10%
Value2,050 ms
7/100
30%
Value0.228
55/100
15%
Value10.4 s
24/100
10%
713 ms
52 ms
86 ms
74 ms
85 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 55% of them (23 requests) were addressed to the original Monodisease.org, 12% (5 requests) were made to Pagead2.googlesyndication.com and 12% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (713 ms) belongs to the original domain Monodisease.org.
Page size can be reduced by 38.6 kB (26%)
148.8 kB
110.2 kB
In fact, the total size of Monodisease.org main page is 148.8 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. 60% of websites need less resources to load. Javascripts take 101.2 kB which makes up the majority of the site volume.
Potential reduce by 38.2 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 38.2 kB or 80% of the original size.
Potential reduce by 366 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 24 (65%)
37
13
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mono Disease. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
monodisease.org
713 ms
adsbygoogle.js
52 ms
wp-emoji-release.min.js
86 ms
default-style.css
74 ms
css.css
85 ms
fonts.css
74 ms
bootstrap.css
73 ms
bootstrap-theme.min.css
72 ms
font-awesome.min.css
103 ms
style.css
104 ms
style_2.1.2.css
101 ms
jquery.js
113 ms
jquery-migrate.min.js
108 ms
js.min.js
100 ms
bootstrap.min.js
125 ms
sarkpress_script.js
124 ms
button.facebook.js
129 ms
show_ads.js
80 ms
script_no_follow_2.1.2.js
123 ms
button.googleplus.js
123 ms
widgets.js
85 ms
wp-embed.min.js
192 ms
show_ads_impl.js
292 ms
zrt_lookup.html
39 ms
OpenSans-Regular-webfont.woff
52 ms
fontawesome-webfont.woff
112 ms
OpenSans-Semibold-webfont.woff
52 ms
10 ms
plusone.js
38 ms
admin-ajax.php
236 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
64 ms
cb=gapi.loaded_0
44 ms
settings
142 ms
ads
448 ms
sodar
28 ms
ads
203 ms
ads
150 ms
sodar2.js
20 ms
ads
177 ms
runner.html
5 ms
aframe
45 ms
s6Lo-ySsTFszeicWuLCsm9BIHYA2isJaSryvoQutTtY.js
4 ms
monodisease.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
monodisease.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
monodisease.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Monodisease.org 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 Monodisease.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.
monodisease.org
Open Graph description is not detected on the main page of Mono Disease. 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: