2 sec in total
153 ms
1.5 sec
272 ms
Welcome to familytreedna.com homepage info - get ready to check Family TreeDNA best content for United States right away, or after learning these important things about familytreedna.com
Discover your DNA story and unlock the secrets of your ancestry and genealogy with our DNA kits for ancestry and the world’s most comprehensive DNA database.
Visit familytreedna.comWe analyzed Familytreedna.com page load time and found that the first response time was 153 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
familytreedna.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value15.5 s
0/100
25%
Value9.5 s
12/100
10%
Value5,770 ms
0/100
30%
Value0.632
9/100
15%
Value21.5 s
1/100
10%
153 ms
174 ms
72 ms
218 ms
100 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 67% of them (32 requests) were addressed to the original Familytreedna.com, 8% (4 requests) were made to Google-analytics.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (655 ms) belongs to the original domain Familytreedna.com.
Page size can be reduced by 70.9 kB (11%)
670.4 kB
599.5 kB
In fact, the total size of Familytreedna.com main page is 670.4 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. 20% of websites need less resources to load. Images take 593.0 kB which makes up the majority of the site volume.
Potential reduce by 23.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 9.2 kB, which is 31% 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 23.2 kB or 78% of the original size.
Potential reduce by 25.8 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. Family TreeDNA images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 20.8 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. Familytreedna.com needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 91% of the original size.
Number of requests can be reduced by 11 (25%)
44
33
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 12 to 1 for JavaScripts and as a result speed up the page load time.
familytreedna.com
153 ms
www.familytreedna.com
174 ms
css
72 ms
styles
218 ms
animations.css
100 ms
js
96 ms
jquery.min.js
82 ms
angular.min.js
101 ms
common
288 ms
homepage
99 ms
gtm.js
205 ms
familytreelogo.png
251 ms
slide-unlock.png
394 ms
slider-ydna.png
301 ms
slider-ff.png
303 ms
slider-abc-20-20.png
252 ms
slider-mt.png
353 ms
spx
327 ms
ydna.png
317 ms
familyfinder-icon.png
316 ms
mtdna.png
369 ms
icon-finder.png
381 ms
mdc.png
498 ms
icon-faq.png
414 ms
icon-forums.png
433 ms
icon-community.png
463 ms
natg_geo_bg.jpg
524 ms
facebook.png
463 ms
twitter.png
501 ms
instagram_icon.png
523 ms
youtube.png
551 ms
pinterest.png
549 ms
tumblr.png
578 ms
gplus.png
581 ms
reddit.png
608 ms
partnership_logo.jpg
610 ms
fontawesome-webfont.woff
655 ms
shoppingCart
498 ms
analytics.js
46 ms
ec.js
9 ms
collect
21 ms
collect
58 ms
collect
30 ms
collect
64 ms
st
168 ms
ga-audiences
47 ms
gs
165 ms
st
206 ms
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.
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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
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 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 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.
familytreedna.com
Open Graph description is not detected on the main page of 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: