3.3 sec in total
176 ms
3 sec
191 ms
Click here to check amazing Cm Family TreeDNA content for United States. Otherwise, check out these important facts you probably never knew about cm.familytreedna.com
Visit cm.familytreedna.comWe analyzed Cm.familytreedna.com page load time and found that the first response time was 176 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cm.familytreedna.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value23.0 s
0/100
25%
Value17.1 s
0/100
10%
Value31,140 ms
0/100
30%
Value0.627
9/100
15%
Value41.3 s
0/100
10%
176 ms
112 ms
181 ms
111 ms
64 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Cm.familytreedna.com, 59% (55 requests) were made to Familytreedna.com and 13% (12 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Familytreedna.com.
Page size can be reduced by 487.2 kB (68%)
713.5 kB
226.3 kB
In fact, the total size of Cm.familytreedna.com main page is 713.5 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. 40% of websites need less resources to load. Javascripts take 321.2 kB which makes up the majority of the site volume.
Potential reduce by 26.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. This page needs HTML code to be minified as it can gain 7.7 kB, which is 22% 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 26.2 kB or 76% of the original size.
Potential reduce by 6.1 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. Cm Family TreeDNA images are well optimized though.
Potential reduce by 210.2 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 210.2 kB or 65% of the original size.
Potential reduce by 244.6 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. Cm.familytreedna.com needs all CSS files to be minified and compressed as it can save up to 244.6 kB or 84% of the original size.
Number of requests can be reduced by 57 (70%)
81
24
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cm Family TreeDNA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cm.familytreedna.com
176 ms
login.aspx
112 ms
login.aspx
181 ms
skin.css
111 ms
css
64 ms
shadowbox-base.js
114 ms
shadowbox.js
120 ms
main.js
130 ms
AC_RunActiveContent.js
132 ms
login.css
130 ms
styles
366 ms
js
98 ms
jquery.min.js
73 ms
angular.min.js
90 ms
common
443 ms
generic
228 ms
animations.css
222 ms
WebResource.axd
222 ms
skin.css
103 ms
skin.js
211 ms
shadowbox-en.js
215 ms
shadowbox-html.js
217 ms
shadowbox-img.js
216 ms
shadowbox-swf.js
341 ms
shadowbox-iframe.js
341 ms
shadowbox-flv.js
342 ms
skin.css
106 ms
skin.js
111 ms
shadowbox-en.js
112 ms
searchInContentPane.css
105 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
201 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
217 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
294 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
335 ms
gtm.js
212 ms
spx
487 ms
familytreelogo.png
339 ms
wVmTYXVQmzg
308 ms
a-small.gif
365 ms
a-med.gif
345 ms
a-large.gif
340 ms
icon_delete_round_sm.png
366 ms
bg_sm_button_orange.gif
343 ms
login_button_170.gif
488 ms
button_orderNow.gif
542 ms
discover-your-past-300x140.jpg
562 ms
bg_navBar.png
544 ms
bg_sm_button_orange_search.gif
542 ms
video-still-bennett.jpg
541 ms
kit-thumb.jpg
648 ms
facebook.png
652 ms
twitter.png
655 ms
instagram_icon.png
657 ms
youtube.png
659 ms
pinterest.png
684 ms
tumblr.png
757 ms
gplus.png
762 ms
reddit.png
761 ms
partnership_logo.jpg
765 ms
shoppingCart
676 ms
fontawesome-webfont.woff
844 ms
analytics.js
139 ms
www-embed-player-vflfNyN_r.css
93 ms
www-embed-player.js
135 ms
ec.js
51 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
117 ms
ad_status.js
113 ms
collect
59 ms
collect
142 ms
collect
78 ms
collect
74 ms
collect
74 ms
collect
143 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
45 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
45 ms
st
209 ms
collect
9 ms
ga-audiences
24 ms
gs
165 ms
st
116 ms
generic
23 ms
generic
7 ms
bg_tableHead.gif
107 ms
collect
11 ms
collect
5 ms
collect
5 ms
collect
6 ms
collect
6 ms
close.png
109 ms
next.png
108 ms
play.png
110 ms
pause.png
114 ms
previous.png
115 ms
loading.gif
206 ms
cm.familytreedna.com accessibility score
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
cm.familytreedna.com 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
Missing source maps for large first-party JavaScript
cm.familytreedna.com 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
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cm.familytreedna.com 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 Cm.familytreedna.com 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.
cm.familytreedna.com
Open Graph description is not detected on the main page of Cm Family TreeDNA. 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: