Tools & Wizards About Us
ftdna.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ftdna.com

DNA Testing for Ancestry & Genealogy - FamilyTreeDNA

Page Load Speed

5 sec in total

First Response

1.1 sec

Resources Loaded

2.5 sec

Page Rendered

1.3 sec

ftdna.com screenshot

About Website

Click here to check amazing Ft DNA content. Otherwise, check out these important facts you probably never knew about ftdna.com

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

Visit ftdna.com

Key Findings

We analyzed Ftdna.com page load time and found that the first response time was 1.1 sec and then it took 3.9 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

ftdna.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value5,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.1

89/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

www.familytreedna.com

1088 ms

css

110 ms

css

108 ms

css

109 ms

icon

108 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 Ftdna.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.1 sec) relates to the external source Familytreedna.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.5 kB (7%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ftdna.com main page is 2.1 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 119.8 kB

  • Original 148.4 kB
  • After minification 147.2 kB
  • After compression 28.7 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 119.8 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 27.4 kB

  • Original 1.9 MB
  • After minification 1.9 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. Ft DNA images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 9.3 kB

  • Original 51.0 kB
  • After minification 51.0 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 9.3 kB or 18% 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 Ft DNA. 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

1088 ms

css

css

110 ms

css

css

108 ms

css

css

109 ms

icon

icon

108 ms

materialdesignicons.min.css

materialdesignicons.min.css

92 ms

header

header

98 ms

bdt-uikit.css

bdt-uikit.css

131 ms

prime-slider-site.css

prime-slider-site.css

124 ms

eae.min.css

eae.min.css

142 ms

peel.css

peel.css

193 ms

v4-shims.min.css

v4-shims.min.css

160 ms

all.min.css

all.min.css

150 ms

vegas.min.css

vegas.min.css

168 ms

theme.min.css

theme.min.css

189 ms

header-footer.min.css

header-footer.min.css

204 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

211 ms

post-129.css

post-129.css

194 ms

swiper.min.css

swiper.min.css

206 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

228 ms

post-14409.css

post-14409.css

245 ms

css

css

105 ms

iconHelper.js

iconHelper.js

245 ms

jquery.min.js

jquery.min.js

257 ms

jquery-migrate.min.js

jquery-migrate.min.js

241 ms

css2

css2

111 ms

ftdna

ftdna

170 ms

10048998-100410151.js

10048998-100410151.js

104 ms

uc.js

uc.js

116 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

209 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

278 ms

jquery

jquery

150 ms

collapsible-menu

collapsible-menu

88 ms

runtime

runtime

126 ms

polyfills

polyfills

381 ms

main

main

205 ms

runtime

runtime

122 ms

main

main

383 ms

animations.min.css

animations.min.css

277 ms

tabbed-ancestry.css

tabbed-ancestry.css

275 ms

eae.min.js

eae.min.js

277 ms

index.min.js

index.min.js

380 ms

v4-shims.min.js

v4-shims.min.js

381 ms

animated-main.min.js

animated-main.min.js

380 ms

particles.min.js

particles.min.js

380 ms

magnific.min.js

magnific.min.js

379 ms

vegas.min.js

vegas.min.js

382 ms

hello-frontend.min.js

hello-frontend.min.js

472 ms

ftdna-cart.js

ftdna-cart.js

472 ms

tabbed-ancestry.js

tabbed-ancestry.js

433 ms

bdt-uikit.min.js

bdt-uikit.min.js

472 ms

webpack.runtime.min.js

webpack.runtime.min.js

431 ms

frontend-modules.min.js

frontend-modules.min.js

471 ms

waypoints.min.js

waypoints.min.js

471 ms

core.min.js

core.min.js

404 ms

frontend.min.js

frontend.min.js

651 ms

prime-slider-site.min.js

prime-slider-site.min.js

635 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

628 ms

hooks.min.js

hooks.min.js

620 ms

i18n.min.js

i18n.min.js

617 ms

frontend.min.js

frontend.min.js

614 ms

elements-handlers.min.js

elements-handlers.min.js

604 ms

mtDNA-box-1.png

mtDNA-box-1.png

506 ms

Family-Finder-box-1.png

Family-Finder-box-1.png

502 ms

Big-Y-box-1.png

Big-Y-box-1.png

510 ms

Y-DNA-box-1.png

Y-DNA-box-1.png

507 ms

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

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

904 ms

quiz-BG-22-1024x858.png

quiz-BG-22-1024x858.png

512 ms

person_a@2x.jpg

person_a@2x.jpg

510 ms

person_b@2x.jpg

person_b@2x.jpg

528 ms

person_c@2x.jpg

person_c@2x.jpg

513 ms

persona_a_card.svg

persona_a_card.svg

604 ms

BG-77.png

BG-77.png

500 ms

persona_b_card.svg

persona_b_card.svg

476 ms

persona_c_card.svg

persona_c_card.svg

554 ms

Group-Projects.png

Group-Projects.png

569 ms

1-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

1-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

566 ms

2-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

2-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

467 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

96 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

97 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

348 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

352 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

352 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

353 ms

3-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

3-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

467 ms

4-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

4-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

470 ms

dna-secure-mobile@2x.webp

dna-secure-mobile@2x.webp

465 ms

myorigins_map.webp

myorigins_map.webp

467 ms

myorigins_map_persona_1.webp

myorigins_map_persona_1.webp

467 ms

ftdna-brand.svg

ftdna-brand.svg

82 ms

Twitter.svg

Twitter.svg

44 ms

Facebook.svg

Facebook.svg

44 ms

Instagram.svg

Instagram.svg

45 ms

YouTube.svg

YouTube.svg

47 ms

header

header

221 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

40 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

39 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

38 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

36 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

37 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

38 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

39 ms

api.min.js

api.min.js

74 ms

Accessibility Review

ftdna.com accessibility score

73

Accessibility Issues

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

ftdna.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

ftdna.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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ftdna.com 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 Ftdna.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

ftdna.com

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