1.3 sec in total
277 ms
766 ms
241 ms
Click here to check amazing Myotonic content for United States. Otherwise, check out these important facts you probably never knew about myotonic.org
The Myotonic Dystrophy Foundation (MDF) is the leading global advocate helping patients and families navigate the myotonic dystrophy (DM) disease process.
Visit myotonic.orgWe analyzed Myotonic.org page load time and found that the first response time was 277 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
myotonic.org performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value11.9 s
0/100
25%
Value5.8 s
50/100
10%
Value660 ms
45/100
30%
Value0.023
100/100
15%
Value10.1 s
26/100
10%
277 ms
90 ms
28 ms
38 ms
40 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 91% of them (117 requests) were addressed to the original Myotonic.org, 4% (5 requests) were made to Use.fontawesome.com and 2% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (277 ms) belongs to the original domain Myotonic.org.
Page size can be reduced by 206.0 kB (18%)
1.2 MB
956.0 kB
In fact, the total size of Myotonic.org main page is 1.2 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. 70% of websites need less resources to load. Images take 655.5 kB which makes up the majority of the site volume.
Potential reduce by 88.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 11.5 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 88.4 kB or 84% of the original size.
Potential reduce by 7.6 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. Myotonic images are well optimized though.
Potential reduce by 37.6 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 37.6 kB or 17% of the original size.
Potential reduce by 72.5 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. Myotonic.org needs all CSS files to be minified and compressed as it can save up to 72.5 kB or 41% of the original size.
Number of requests can be reduced by 108 (90%)
120
12
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Myotonic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 63 to 1 for CSS and as a result speed up the page load time.
www.myotonic.org
277 ms
js
90 ms
slick.css
28 ms
views-responsive-grid.css
38 ms
slick.module.css
40 ms
ajax-progress.module.css
36 ms
align.module.css
50 ms
autocomplete-loading.module.css
39 ms
fieldgroup.module.css
37 ms
container-inline.module.css
43 ms
clearfix.module.css
43 ms
details.module.css
41 ms
hidden.module.css
41 ms
item-list.module.css
46 ms
js.module.css
45 ms
nowrap.module.css
47 ms
position-container.module.css
47 ms
progress.module.css
48 ms
reset-appearance.module.css
49 ms
resize.module.css
57 ms
sticky-header.module.css
54 ms
system-status-counter.css
57 ms
system-status-report-counters.css
52 ms
system-status-report-general-info.css
56 ms
tabledrag.module.css
56 ms
tablesort.module.css
67 ms
tree-child.module.css
57 ms
views.module.css
66 ms
blazy.css
67 ms
blazy.loading.css
68 ms
addtoany.css
68 ms
all.css
61 ms
v4-shims.css
81 ms
smm.css
67 ms
font-awesome.min.css
47 ms
tb_megamenu.bootstrap.css
70 ms
tb_megamenu.base.css
74 ms
tb_megamenu.default.css
74 ms
tb_megamenu.compatibility.css
77 ms
black.css
78 ms
gximage2
168 ms
membership_badge_plat.png
109 ms
page.js
54 ms
normalize.css
70 ms
action-links.css
87 ms
breadcrumb.css
78 ms
container-inline.css
77 ms
details.css
77 ms
exposed-filters.css
78 ms
field.css
82 ms
form.css
76 ms
icons.css
76 ms
inline-form.css
76 ms
item-list.css
75 ms
links.css
76 ms
menu.css
74 ms
more-link.css
74 ms
pager.css
74 ms
tabledrag.css
75 ms
tableselect.css
81 ms
tablesort.css
73 ms
textarea.css
70 ms
ui-dialog.css
70 ms
messages.css
69 ms
progress.css
68 ms
style.css
73 ms
style.css
69 ms
style1.css
82 ms
blazy.polyfill.min.js
72 ms
jquery.min.js
99 ms
blazy.classlist.min.js
106 ms
blazy.promise.min.js
106 ms
blazy.raf.min.js
107 ms
once.min.js
108 ms
drupalSettingsLoader.js
100 ms
drupal.js
103 ms
drupal.init.js
102 ms
debounce.js
103 ms
dblazy.min.js
106 ms
blazy.once.min.js
85 ms
blazy.sanitizer.min.js
81 ms
blazy.dom.min.js
80 ms
blazy.base.min.js
81 ms
blazy.dataset.min.js
84 ms
blazy.viewport.min.js
82 ms
blazy.xlazy.min.js
79 ms
blazy.observer.min.js
82 ms
blazy.loading.min.js
82 ms
blazy.webp.min.js
81 ms
blazy.min.js
82 ms
bio.min.js
81 ms
slick.min.js
82 ms
bio.media.min.js
84 ms
blazy.drupal.min.js
80 ms
blazy.load.min.js
81 ms
blazy.compat.min.js
81 ms
index.umd.min.js
82 ms
addtoany.js
82 ms
google_analytics.js
81 ms
bootstrap.bundle.js
85 ms
smm.min.js
78 ms
tb-megamenu-frontend.js
70 ms
progress.js
69 ms
loadjs.min.js
46 ms
announce.js
38 ms
message.js
38 ms
ajax.js
36 ms
bio.ajax.min.js
41 ms
jquery.form.min.js
38 ms
base.js
36 ms
ajax_view.js
33 ms
slick.load.min.js
35 ms
logo-animated_nav.gif
34 ms
PostGrotesk-Book.woff
42 ms
PostGrotesk-Medium.woff
34 ms
badge_bst.gif
35 ms
badge_resourcecenter.jpg
34 ms
badge_pro-resources3.jpg
34 ms
badge_calendar.jpg
34 ms
Bades1_0.jpg
49 ms
MDF-Silver-White.png
32 ms
sm.25.html
28 ms
eso.D0Uc7kY6.js
69 ms
Myotonic-Reckless-Regular.woff
33 ms
Myotonic-Reckless-Medium.woff
9 ms
Myotonic-Reckless-SemiBold.woff
14 ms
fa-brands-400.ttf
100 ms
fa-solid-900.ttf
45 ms
fa-regular-400.ttf
26 ms
myotonic.org 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
myotonic.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
myotonic.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Myotonic.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 Myotonic.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.
myotonic.org
Open Graph description is not detected on the main page of Myotonic. 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: