3.5 sec in total
270 ms
2.9 sec
299 ms
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 DNA kits for ancestry and the world’s most comprehensive DNA database.
Visit ftdna.comWe analyzed Ftdna.com page load time and found that the first response time was 270 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.
ftdna.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value28.5 s
0/100
25%
Value22.2 s
0/100
10%
Value38,460 ms
0/100
30%
Value0.627
9/100
15%
Value48.0 s
0/100
10%
270 ms
88 ms
112 ms
102 ms
84 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ftdna.com, 14% (5 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (999 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 114.7 kB (54%)
212.1 kB
97.3 kB
In fact, the total size of Ftdna.com main page is 212.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 177.2 kB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.3 kB or 79% of the original size.
Potential reduce by 87.4 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.4 kB or 49% of the original size.
Number of requests can be reduced by 20 (69%)
29
9
The browser has sent 29 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 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.familytreedna.com
270 ms
css
88 ms
icon
112 ms
materialdesignicons.min.css
102 ms
header
84 ms
ftdna
143 ms
optimize.js
305 ms
uc.js
229 ms
jquery
275 ms
collapsible-menu
251 ms
runtime
252 ms
polyfills
420 ms
main
268 ms
runtime
242 ms
main
436 ms
runtime
260 ms
polyfills
263 ms
main
437 ms
jquery-ui.min.js
94 ms
pageinit
254 ms
cc.js
989 ms
ftdna-brand.svg
792 ms
bc-v4.min.html
639 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
921 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
997 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
999 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
988 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
987 ms
Twitter.svg
547 ms
Facebook.svg
544 ms
Instagram.svg
546 ms
YouTube.svg
541 ms
header
517 ms
materialdesignicons-webfont.woff
420 ms
google-analytics.js
324 ms
class.js
321 ms
ftdna.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.
ftdna.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
ftdna.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
EN
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.
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: