2.7 sec in total
198 ms
2.2 sec
306 ms
Visit dnaheritage.com now to see the best up-to-date DNA Heritage content and also check out these interesting facts you probably never knew about dnaheritage.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 dnaheritage.comWe analyzed Dnaheritage.com page load time and found that the first response time was 198 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
dnaheritage.com performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value15.1 s
0/100
25%
Value9.7 s
10/100
10%
Value3,210 ms
2/100
30%
Value0.632
9/100
15%
Value20.1 s
2/100
10%
198 ms
300 ms
60 ms
260 ms
126 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dnaheritage.com, 14% (7 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 (745 ms) relates to the external source Familytreedna.com.
Page size can be reduced by 68.4 kB (19%)
356.1 kB
287.8 kB
In fact, the total size of Dnaheritage.com main page is 356.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. 20% of websites need less resources to load. Images take 274.7 kB which makes up the majority of the site volume.
Potential reduce by 31.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. This page needs HTML code to be minified as it can gain 11.6 kB, which is 30% 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 31.7 kB or 83% of the original size.
Potential reduce by 17.5 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. DNA Heritage images are well optimized though.
Potential reduce by 75 B
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 19.1 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. Dnaheritage.com needs all CSS files to be minified and compressed as it can save up to 19.1 kB or 92% of the original size.
Number of requests can be reduced by 17 (38%)
45
28
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DNA Heritage. 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.
dna-heritage.aspx
198 ms
products.aspx
300 ms
css
60 ms
styles
260 ms
animations.css
126 ms
js
85 ms
jquery.min.js
79 ms
angular.min.js
98 ms
common
452 ms
generic
124 ms
gtm.js
152 ms
familytreelogo.png
330 ms
table_fficon.png
344 ms
table_y37icon.png
349 ms
table_y67icon.png
338 ms
table_y111icon.png
346 ms
table_mtDNAplusicon.png
382 ms
table_mtFullicon.png
460 ms
spx
381 ms
table_sep1.png
441 ms
table_sep2.png
441 ms
bg-suggestbox2.png
510 ms
bg-suggestbox.png
521 ms
bundle_ff_y67.png
567 ms
bundle_CG.png
634 ms
facebook.png
561 ms
twitter.png
563 ms
instagram_icon.png
630 ms
youtube.png
640 ms
pinterest.png
669 ms
tumblr.png
670 ms
gplus.png
676 ms
reddit.png
736 ms
partnership_logo.jpg
745 ms
fontawesome-webfont.woff
742 ms
analytics.js
136 ms
shoppingCart
527 ms
ec.js
11 ms
st
167 ms
collect
14 ms
collect
68 ms
collect
20 ms
collect
39 ms
collect
49 ms
collect
72 ms
collect
19 ms
ga-audiences
47 ms
gs
158 ms
st
155 ms
generic
23 ms
generic
12 ms
dnaheritage.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.
dnaheritage.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
dnaheritage.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 Dnaheritage.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 Dnaheritage.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.
dnaheritage.com
Open Graph description is not detected on the main page of DNA Heritage. 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: