Tools & Wizards About Us
web001.myheritage.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

web001.myheritage.com

Free Family Tree, Genealogy, Family History, and DNA Testing

Page Load Speed

2.3 sec in total

First Response

215 ms

Resources Loaded

1.5 sec

Page Rendered

543 ms

web001.myheritage.com screenshot

About Website

Click here to check amazing Web 001 Myheritage content for United States. Otherwise, check out these important facts you probably never knew about web001.myheritage.com

Create your family tree. Take a MyHeritage DNA test for ancestry and genetic testing. Access 19.6 billion historical records for genealogy research.

Visit web001.myheritage.com

Key Findings

We analyzed Web001.myheritage.com page load time and found that the first response time was 215 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

web001.myheritage.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

www.myheritage.com

215 ms

base-responsive_ltr_v1457854095o.css

157 ms

CompanyHome_ltr_v1457603602o.css

146 ms

jquery-all-combined_v1457603347.js

172 ms

initialize_v1457603431.js

168 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Web001.myheritage.com, 9% (2 requests) were made to Myheritage.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (230 ms) relates to the external source D.mhcache.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (52%)

Content Size

2.1 MB

After Optimization

989.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Web001.myheritage.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. 60% of websites need less resources to load. Javascripts take 931.0 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 88.3 kB

  • Original 103.0 kB
  • After minification 63.4 kB
  • After compression 14.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 39.6 kB, which is 38% 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 88.3 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 7.6 kB

  • Original 702.1 kB
  • After minification 694.4 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. Web 001 Myheritage images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 703.5 kB

  • Original 931.0 kB
  • After minification 820.7 kB
  • After compression 227.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 703.5 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 276.8 kB

  • Original 329.5 kB
  • After minification 326.2 kB
  • After compression 52.7 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. Web001.myheritage.com needs all CSS files to be minified and compressed as it can save up to 276.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (43%)

Requests Now

21

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Web 001 Myheritage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.myheritage.com

www.myheritage.com

215 ms

base-responsive_ltr_v1457854095o.css

base-responsive_ltr_v1457854095o.css

157 ms

CompanyHome_ltr_v1457603602o.css

CompanyHome_ltr_v1457603602o.css

146 ms

jquery-all-combined_v1457603347.js

jquery-all-combined_v1457603347.js

172 ms

initialize_v1457603431.js

initialize_v1457603431.js

168 ms

TestimonialQuotesUS_ltr_v1457603595o.css

TestimonialQuotesUS_ltr_v1457603595o.css

124 ms

jquery.validationEngine_dLTR_bMZ_v1457603615.css

jquery.validationEngine_dLTR_bMZ_v1457603615.css

168 ms

CompanyHome_v1457961232.js

CompanyHome_v1457961232.js

169 ms

get-dictionary.php

get-dictionary.php

86 ms

CompanyHomeAnimations_v1457603431.js

CompanyHomeAnimations_v1457603431.js

168 ms

main-standalone_v1458132152.js

main-standalone_v1458132152.js

230 ms

spacer.gif

spacer.gif

71 ms

Desktop.png

Desktop.png

88 ms

Logos_US.png

Logos_US.png

85 ms

Logos_US.png

Logos_US.png

89 ms

animations_sprite.png

animations_sprite.png

87 ms

DiscoveryBg.jpg

DiscoveryBg.jpg

85 ms

masterpage_sprite.png

masterpage_sprite.png

84 ms

companyhomequotesus_sprite.png

companyhomequotesus_sprite.png

60 ms

state_specific_1.jpg

state_specific_1.jpg

55 ms

Play.png

Play.png

4 ms

gtm.js

gtm.js

69 ms

Accessibility Review

web001.myheritage.com accessibility score

88

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.

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

Best Practices

web001.myheritage.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

Missing source maps for large first-party JavaScript

SEO Factors

web001.myheritage.com SEO score

93

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

web001.myheritage.com

Open Graph description is not detected on the main page of Web 001 Myheritage. 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: