Tools & Wizards About Us
cm.familytreedna.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

cm.familytreedna.com

DNA Testing for Ancestry & Genealogy | FamilyTreeDNA

Page Load Speed

4.7 sec in total

First Response

1 sec

Resources Loaded

2.6 sec

Page Rendered

1 sec

cm.familytreedna.com screenshot

About Website

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

Discover your DNA story and unlock the secrets of your ancestry and genealogy with our autosomal DNA, Y-DNA and mtDNA tests.

Visit cm.familytreedna.com

Key Findings

We analyzed Cm.familytreedna.com page load time and found that the first response time was 1 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

cm.familytreedna.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value7,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

www.familytreedna.com

1012 ms

css

72 ms

css

72 ms

css

73 ms

icon

118 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Cm.familytreedna.com, 16% (16 requests) were made to Familytreedna.com and 12% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cms.familytreedna.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.5 kB (11%)

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Cm.familytreedna.com main page is 2.7 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. Only a small number of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 104.0 kB

  • Original 131.1 kB
  • After minification 129.9 kB
  • After compression 27.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 104.0 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 116.6 kB

  • Original 2.5 MB
  • After minification 2.4 MB

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.

JavaScript Optimization

-68%

Potential reduce by 87.9 kB

  • Original 129.6 kB
  • After minification 129.6 kB
  • After compression 41.7 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 87.9 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (67%)

Requests Now

89

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 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 35 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.familytreedna.com

www.familytreedna.com

1012 ms

css

css

72 ms

css

css

72 ms

css

css

73 ms

icon

icon

118 ms

materialdesignicons.min.css

materialdesignicons.min.css

104 ms

header

header

112 ms

bdt-uikit.css

bdt-uikit.css

201 ms

prime-slider-site.css

prime-slider-site.css

162 ms

eae.min.css

eae.min.css

179 ms

peel.css

peel.css

165 ms

v4-shims.min.css

v4-shims.min.css

165 ms

all.min.css

all.min.css

171 ms

vegas.min.css

vegas.min.css

209 ms

theme.min.css

theme.min.css

230 ms

header-footer.min.css

header-footer.min.css

206 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

223 ms

post-129.css

post-129.css

247 ms

swiper.min.css

swiper.min.css

230 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

230 ms

post-4505.css

post-4505.css

250 ms

css

css

108 ms

iconHelper.js

iconHelper.js

261 ms

jquery.min.js

jquery.min.js

267 ms

jquery-migrate.min.js

jquery-migrate.min.js

258 ms

css2

css2

108 ms

ftdna

ftdna

203 ms

10048998-100410151.js

10048998-100410151.js

164 ms

uc.js

uc.js

120 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

262 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

369 ms

jquery

jquery

160 ms

collapsible-menu

collapsible-menu

135 ms

runtime

runtime

159 ms

polyfills

polyfills

397 ms

main

main

227 ms

runtime

runtime

172 ms

main

main

431 ms

animations.min.css

animations.min.css

260 ms

tabbed-ancestry.css

tabbed-ancestry.css

261 ms

eae.min.js

eae.min.js

312 ms

index.min.js

index.min.js

366 ms

v4-shims.min.js

v4-shims.min.js

366 ms

animated-main.min.js

animated-main.min.js

397 ms

particles.min.js

particles.min.js

313 ms

magnific.min.js

magnific.min.js

395 ms

vegas.min.js

vegas.min.js

395 ms

hello-frontend.min.js

hello-frontend.min.js

429 ms

ftdna-cart.js

ftdna-cart.js

429 ms

tabbed-ancestry.js

tabbed-ancestry.js

431 ms

bdt-uikit.min.js

bdt-uikit.min.js

430 ms

webpack.runtime.min.js

webpack.runtime.min.js

431 ms

frontend-modules.min.js

frontend-modules.min.js

430 ms

waypoints.min.js

waypoints.min.js

891 ms

core.min.js

core.min.js

387 ms

frontend.min.js

frontend.min.js

764 ms

prime-slider-site.min.js

prime-slider-site.min.js

764 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

756 ms

hooks.min.js

hooks.min.js

738 ms

i18n.min.js

i18n.min.js

726 ms

frontend.min.js

frontend.min.js

800 ms

elements-handlers.min.js

elements-handlers.min.js

794 ms

mtDNA-box-1.png

mtDNA-box-1.png

718 ms

Family-Finder-box-1.png

Family-Finder-box-1.png

715 ms

Big-Y-box-1.png

Big-Y-box-1.png

717 ms

Y-DNA-box-1.png

Y-DNA-box-1.png

722 ms

Making-Connections-Video-Homepage-Wordpress-800-x-500-px-7.gif

Making-Connections-Video-Homepage-Wordpress-800-x-500-px-7.gif

1018 ms

person_a@2x.jpg

person_a@2x.jpg

720 ms

person_b@2x.jpg

person_b@2x.jpg

826 ms

person_c@2x.jpg

person_c@2x.jpg

822 ms

persona_a_card.svg

persona_a_card.svg

811 ms

hero-genealogy-diagram-3.svg

hero-genealogy-diagram-3.svg

641 ms

Hero-person-1.png

Hero-person-1.png

1013 ms

persona_b_card.svg

persona_b_card.svg

826 ms

persona_c_card.svg

persona_c_card.svg

836 ms

Group-Projects.png

Group-Projects.png

856 ms

1-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

1-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

789 ms

2-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

2-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

814 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

198 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

582 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

589 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

592 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

591 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

591 ms

3-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

3-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

808 ms

4-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

4-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

788 ms

dna-secure-mobile@2x.webp

dna-secure-mobile@2x.webp

734 ms

myorigins_map.webp

myorigins_map.webp

758 ms

myorigins_map_persona_1.webp

myorigins_map_persona_1.webp

758 ms

ftdna-brand.svg

ftdna-brand.svg

376 ms

Twitter.svg

Twitter.svg

276 ms

Facebook.svg

Facebook.svg

287 ms

Instagram.svg

Instagram.svg

277 ms

YouTube.svg

YouTube.svg

284 ms

header

header

293 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

123 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

32 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

32 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

34 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

34 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

35 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

34 ms

api.min.js

api.min.js

102 ms

Accessibility Review

cm.familytreedna.com accessibility score

66

Accessibility Issues

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

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

cm.familytreedna.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

cm.familytreedna.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    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. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. 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.

Social Sharing Optimization

cm.familytreedna.com

Open Graph data is detected on the main page of Cm Family TreeDNA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: