Tools & Wizards About Us
myheritagedna.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

myheritagedna.com

MyHeritage DNA | Reveal your Ethnicity & Ancestry | DNA Testing - MyHeritage

Page Load Speed

1.8 sec in total

First Response

167 ms

Resources Loaded

1.4 sec

Page Rendered

210 ms

myheritagedna.com screenshot

About Website

Welcome to myheritagedna.com homepage info - get ready to check My Heritage DNA best content right away, or after learning these important things about myheritagedna.com

Discover your ancestry - DNA testing reveals both your ancestry and ethnicity. Order your DNA test kit.

Visit myheritagedna.com

Key Findings

We analyzed Myheritagedna.com page load time and found that the first response time was 167 ms and then it took 1.6 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.

Performance Metrics

myheritagedna.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value3,080 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

myheritagedna.com

167 ms

456 ms

report-violation.php

87 ms

report-violation.php

83 ms

report-violation.php

84 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Myheritagedna.com, 80% (56 requests) were made to Myheritage.com and 17% (12 requests) were made to Cf.mhcache.com. The less responsive or slowest element that took the longest time to load (749 ms) relates to the external source Myheritage-container.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.7 kB (48%)

Content Size

245.0 kB

After Optimization

128.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myheritagedna.com main page is 245.0 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. 30% of websites need less resources to load. HTML takes 150.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 113.6 kB

  • Original 150.6 kB
  • After minification 147.7 kB
  • After compression 37.0 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 113.6 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 55 B

  • Original 27.8 kB
  • After minification 27.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. My Heritage DNA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 12.5 kB
  • After minification 12.5 kB
  • After compression 12.5 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.

CSS Optimization

-6%

Potential reduce by 3.1 kB

  • Original 54.1 kB
  • After minification 54.1 kB
  • After compression 51.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. Myheritagedna.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (38%)

Requests Now

13

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Heritage 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

myheritagedna.com

myheritagedna.com

167 ms

456 ms

report-violation.php

report-violation.php

87 ms

report-violation.php

report-violation.php

83 ms

report-violation.php

report-violation.php

84 ms

report-violation.php

report-violation.php

85 ms

report-violation.php

report-violation.php

85 ms

Themes_bundle_ltr_v02a01c035a1beaba691dc38455adca04.css

Themes_bundle_ltr_v02a01c035a1beaba691dc38455adca04.css

104 ms

NavigationBar_bundle_ltr_v76800a4bcd9370268d2539bacaa7f63e.css

NavigationBar_bundle_ltr_v76800a4bcd9370268d2539bacaa7f63e.css

104 ms

minimal-thin-base-responsive_ltr_v1cf8028011d278b825d266319102cbd9.css

minimal-thin-base-responsive_ltr_v1cf8028011d278b825d266319102cbd9.css

106 ms

DnaBareHeader_ltr_v5031732b9e32f73cc65692fd8b2a5b7c.css

DnaBareHeader_ltr_v5031732b9e32f73cc65692fd8b2a5b7c.css

134 ms

DnaSite_bundle_ltr_v197d635e9747ce804be8bc4e21000052.css

DnaSite_bundle_ltr_v197d635e9747ce804be8bc4e21000052.css

134 ms

report-violation.php

report-violation.php

127 ms

report-violation.php

report-violation.php

127 ms

report-violation.php

report-violation.php

126 ms

PromotionalBannerSystem_bundle_ltr_v08ec9c276aa2656912db359e5b119390.css

PromotionalBannerSystem_bundle_ltr_v08ec9c276aa2656912db359e5b119390.css

157 ms

report-violation.php

report-violation.php

137 ms

report-violation.php

report-violation.php

135 ms

report-violation.php

report-violation.php

89 ms

report-violation.php

report-violation.php

137 ms

report-violation.php

report-violation.php

136 ms

report-violation.php

report-violation.php

134 ms

report-violation.php

report-violation.php

137 ms

report-violation.php

report-violation.php

168 ms

report-violation.php

report-violation.php

169 ms

report-violation.php

report-violation.php

170 ms

report-violation.php

report-violation.php

187 ms

report-violation.php

report-violation.php

189 ms

report-violation.php

report-violation.php

170 ms

report-violation.php

report-violation.php

199 ms

report-violation.php

report-violation.php

213 ms

report-violation.php

report-violation.php

197 ms

masterpage_sprite.png

masterpage_sprite.png

40 ms

spacer.gif

spacer.gif

40 ms

report-violation.php

report-violation.php

183 ms

report-violation.php

report-violation.php

195 ms

report-violation.php

report-violation.php

223 ms

report-violation.php

report-violation.php

206 ms

report-violation.php

report-violation.php

209 ms

report-violation.php

report-violation.php

216 ms

report-violation.php

report-violation.php

244 ms

report-violation.php

report-violation.php

225 ms

report-violation.php

report-violation.php

239 ms

report-violation.php

report-violation.php

240 ms

report-violation.php

report-violation.php

248 ms

report-violation.php

report-violation.php

257 ms

report-violation.php

report-violation.php

259 ms

report-violation.php

report-violation.php

266 ms

report-violation.php

report-violation.php

270 ms

report-violation.php

report-violation.php

271 ms

report-violation.php

report-violation.php

281 ms

report-violation.php

report-violation.php

287 ms

report-violation.php

report-violation.php

289 ms

report-violation.php

report-violation.php

300 ms

report-violation.php

report-violation.php

310 ms

report-violation.php

report-violation.php

306 ms

report-violation.php

report-violation.php

315 ms

report-violation.php

report-violation.php

323 ms

report-violation.php

report-violation.php

321 ms

report-violation.php

report-violation.php

331 ms

report-violation.php

report-violation.php

346 ms

report-violation.php

report-violation.php

346 ms

report-violation.php

report-violation.php

345 ms

report-violation.php

report-violation.php

354 ms

749 ms

report-violation.php

report-violation.php

354 ms

dna-kit.webp

dna-kit.webp

7 ms

dna-package.webp

dna-package.webp

6 ms

dnasite_sprite.png

dnasite_sprite.png

7 ms

GtmIframeLoaderBundled_v7cfc9687627545be03fb65c96f4b4696.js

GtmIframeLoaderBundled_v7cfc9687627545be03fb65c96f4b4696.js

4 ms

Accessibility Review

myheritagedna.com accessibility score

84

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 match their roles

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

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

myheritagedna.com best practices score

83

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

Page has valid source maps

SEO Factors

myheritagedna.com SEO score

93

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

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myheritagedna.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 Myheritagedna.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

myheritagedna.com

Open Graph description is not detected on the main page of My Heritage DNA. 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: