Tools & Wizards About Us
myheritage.nl screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

myheritage.nl

Gratis stamboom, genealogie, familiegeschiedenis en DNA-testen

Page Load Speed

1.3 sec in total

First Response

39 ms

Resources Loaded

912 ms

Page Rendered

320 ms

myheritage.nl screenshot

About Website

Click here to check amazing Myheritage content for Netherlands. Otherwise, check out these important facts you probably never knew about myheritage.nl

Maak uw stamboom. Doe een MyHeritage DNA-test voor afstamming en genetische testen. Krijg toegang tot 21,0 miljard historische gegevens voor uw genealogisch onderzoek.

Visit myheritage.nl

Key Findings

We analyzed Myheritage.nl page load time and found that the first response time was 39 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

myheritage.nl performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

myheritage.nl

39 ms

www.myheritage.nl

244 ms

report-violation.php

61 ms

report-violation.php

59 ms

minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css

41 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 60% of them (43 requests) were addressed to the original Myheritage.nl, 39% (28 requests) were made to Cf.mhcache.com and 1% (1 request) were made to Myheritage-container.com. The less responsive or slowest element that took the longest time to load (614 ms) relates to the external source Myheritage-container.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.8 kB (63%)

Content Size

203.0 kB

After Optimization

75.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Myheritage.nl main page is 203.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. 35% of websites need less resources to load. HTML takes 141.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 110.5 kB

  • Original 141.0 kB
  • After minification 138.2 kB
  • After compression 30.5 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 110.5 kB or 78% of the original size.

Image Optimization

-34%

Potential reduce by 17.2 kB

  • Original 50.2 kB
  • After minification 33.0 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. Obviously, Myheritage needs image optimization as it can save up to 17.2 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 12 B

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

Requests Breakdown

Number of requests can be reduced by 8 (28%)

Requests Now

29

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myheritage.nl

myheritage.nl

39 ms

www.myheritage.nl

www.myheritage.nl

244 ms

report-violation.php

report-violation.php

61 ms

report-violation.php

report-violation.php

59 ms

minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css

minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css

41 ms

TypographyComponents_bundle_ltr_v1MVa7d91d757d08fdfb5fbb5b2b74f4fe7ao.css

TypographyComponents_bundle_ltr_v1MVa7d91d757d08fdfb5fbb5b2b74f4fe7ao.css

39 ms

CompanyHomePageDesktop_bundle_ltr_v1MV5546d181ba37c8474f18e79a9caf4d66o.css

CompanyHomePageDesktop_bundle_ltr_v1MV5546d181ba37c8474f18e79a9caf4d66o.css

45 ms

Themes_bundle_ltr_v1MV508f72f03d1aa3e0986cf1d9e2ef4383o.css

Themes_bundle_ltr_v1MV508f72f03d1aa3e0986cf1d9e2ef4383o.css

54 ms

report-violation.php

report-violation.php

95 ms

report-violation.php

report-violation.php

57 ms

report-violation.php

report-violation.php

70 ms

report-violation.php

report-violation.php

77 ms

report-violation.php

report-violation.php

78 ms

report-violation.php

report-violation.php

66 ms

report-violation.php

report-violation.php

90 ms

report-violation.php

report-violation.php

78 ms

US-top-section-bg.webp

US-top-section-bg.webp

36 ms

report-violation.php

report-violation.php

80 ms

report-violation.php

report-violation.php

79 ms

report-violation.php

report-violation.php

84 ms

report-violation.php

report-violation.php

91 ms

report-violation.php

report-violation.php

91 ms

report-violation.php

report-violation.php

98 ms

report-violation.php

report-violation.php

117 ms

report-violation.php

report-violation.php

112 ms

report-violation.php

report-violation.php

115 ms

report-violation.php

report-violation.php

119 ms

report-violation.php

report-violation.php

124 ms

report-violation.php

report-violation.php

165 ms

report-violation.php

report-violation.php

144 ms

report-violation.php

report-violation.php

146 ms

report-violation.php

report-violation.php

154 ms

report-violation.php

report-violation.php

155 ms

report-violation.php

report-violation.php

155 ms

report-violation.php

report-violation.php

199 ms

report-violation.php

report-violation.php

199 ms

report-violation.php

report-violation.php

200 ms

report-violation.php

report-violation.php

199 ms

report-violation.php

report-violation.php

200 ms

report-violation.php

report-violation.php

201 ms

report-violation.php

report-violation.php

243 ms

report-violation.php

report-violation.php

229 ms

report-violation.php

report-violation.php

228 ms

report-violation.php

report-violation.php

230 ms

report-violation.php

report-violation.php

237 ms

report-violation.php

report-violation.php

232 ms

report-violation.php

report-violation.php

259 ms

index.php

index.php

614 ms

report-violation.php

report-violation.php

272 ms

myheritage_logo_inverse.svg

myheritage_logo_inverse.svg

8 ms

AccessibilityButtonInverse.svg

AccessibilityButtonInverse.svg

9 ms

logo.svg

logo.svg

10 ms

dna-genetic-groups-section-bg.webp

dna-genetic-groups-section-bg.webp

14 ms

ethnicity_card_face.webp

ethnicity_card_face.webp

13 ms

deep-nostalgia.webp

deep-nostalgia.webp

12 ms

discovery-bg.webp

discovery-bg.webp

12 ms

community.webp

community.webp

12 ms

devices-logo-desktop.webp

devices-logo-desktop.webp

15 ms

tablet.webp

tablet.webp

15 ms

mobile.webp

mobile.webp

15 ms

desktop.webp

desktop.webp

15 ms

Logos_US_1.png

Logos_US_1.png

20 ms

Logos_US_2.png

Logos_US_2.png

16 ms

Logos_US_3.png

Logos_US_3.png

17 ms

Logos_US_4.png

Logos_US_4.png

16 ms

Logos_US_1.png

Logos_US_1.png

16 ms

Logos_US_2.png

Logos_US_2.png

16 ms

Logos_US_3.png

Logos_US_3.png

18 ms

Logos_US_4.png

Logos_US_4.png

18 ms

companyhomequotesus_sprite.png

companyhomequotesus_sprite.png

17 ms

spacer.gif

spacer.gif

16 ms

GtmIframeLoaderBundled_v1MV82db7c63f4d024337ddf28f7d826f0e7.js

GtmIframeLoaderBundled_v1MV82db7c63f4d024337ddf28f7d826f0e7.js

2 ms

Accessibility Review

myheritage.nl accessibility score

90

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.

Best Practices

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

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

    NL

  • Language Claimed

    NL

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myheritage.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Myheritage.nl main page’s claimed encoding is iso-8859-1. 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

myheritage.nl

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