3.4 sec in total
142 ms
2.8 sec
462 ms
Visit mylymedata.org now to see the best up-to-date My Lyme Data content and also check out these interesting facts you probably never knew about mylymedata.org
MyLymeData is a Lyme disease research project. It lets Lyme disease patients provide data that can help drive research to find a cure for Lyme disease
Visit mylymedata.orgWe analyzed Mylymedata.org page load time and found that the first response time was 142 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mylymedata.org performance score
name
value
score
weighting
Value10.8 s
0/100
10%
Value12.7 s
0/100
25%
Value14.0 s
1/100
10%
Value2,090 ms
7/100
30%
Value0
100/100
15%
Value15.0 s
8/100
10%
142 ms
697 ms
199 ms
196 ms
237 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Mylymedata.org, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Mylymedata.org.
Page size can be reduced by 808.5 kB (46%)
1.8 MB
967.0 kB
In fact, the total size of Mylymedata.org main page is 1.8 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. 55% of websites need less resources to load. Images take 762.2 kB which makes up the majority of the site volume.
Potential reduce by 20.3 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 3.1 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 20.3 kB or 75% of the original size.
Potential reduce by 42.9 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. My Lyme Data images are well optimized though.
Potential reduce by 397.8 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 397.8 kB or 69% of the original size.
Potential reduce by 347.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. Mylymedata.org needs all CSS files to be minified and compressed as it can save up to 347.5 kB or 84% of the original size.
Number of requests can be reduced by 35 (67%)
52
17
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Lyme Data. 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 19 to 1 for CSS and as a result speed up the page load time.
mylymedata.org
142 ms
mylymedata.org
697 ms
jquery-1.8.3.min.js
199 ms
BrowserUpdateWarning.css
196 ms
template.css.php
237 ms
jcemediabox.css
234 ms
style.css
235 ms
modal.css
260 ms
bootstrap.css
388 ms
template.css
400 ms
bootstrap-responsive.css
331 ms
template-responsive.css
333 ms
megamenu.css
275 ms
megamenu-responsive.css
318 ms
off-canvas.css
353 ms
fix_ja-mainbody.css
417 ms
mootools-core.js
456 ms
core.js
428 ms
mootools-more.js
605 ms
BrowserUpdateWarning.js
444 ms
jquery.fpss.js
445 ms
jcemediabox.js
527 ms
modal.js
519 ms
jquery.noconflict.js
519 ms
bootstrap.js
718 ms
jquery.tap.min.js
524 ms
off-canvas.js
581 ms
script.js
582 ms
menu.js
588 ms
responsive.js
600 ms
script.js
732 ms
cb_fix_menu_top.js
732 ms
system.css
734 ms
custom.css
736 ms
font-awesome.css
741 ms
font-awesome.min.css
746 ms
system.css
70 ms
stylesheet.css
300 ms
analytics.js
341 ms
logolyme.png
334 ms
popup.html
116 ms
tooltip.html
101 ms
video-playhd.png
78 ms
98_63503204d18160dd6a733e989b70c404_m.jpg
151 ms
99_063ee9aeb9f60efa02823e51450f82ce_m.jpg
271 ms
100_a63cd9e38964634741a5a3fe89055308_m.jpg
224 ms
101_c1011ef61ed9937904f4938c63d014ea_m.jpg
345 ms
logo-mld-foot.png
152 ms
thin_facebook.png
173 ms
thin_twitter.png
223 ms
thin_youtube.png
224 ms
logo-lymedisease-footgr.png
225 ms
pxr_logo.png
337 ms
freight_sans_medium_sc-webfont.woff
151 ms
proxima_nova_bold-webfont.woff
274 ms
proxima_nova_semibold-webfont.woff
338 ms
proximanova-regular-webfont.woff
282 ms
fontawesome-webfont.woff
341 ms
fontawesome-webfont.eot
432 ms
fontawesome-webfont.woff
433 ms
collect
31 ms
fontawesome-webfont.woff
130 ms
mylymedata.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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mylymedata.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
mylymedata.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Mylymedata.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 Mylymedata.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.
mylymedata.org
Open Graph description is not detected on the main page of My Lyme Data. 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: