Tools & Wizards About Us
myheritage.ee screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% 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.ee

Tasuta sugupuu, genealoogia, perekonnaajaloo ja DNA testimine

Page Load Speed

3.8 sec in total

First Response

849 ms

Resources Loaded

2.5 sec

Page Rendered

388 ms

myheritage.ee screenshot

About Website

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

Looge oma sugupuu. Tehke MyHeritage‘i DNA-test esivanemate ja geneetilise testimise kohta. Juurdepääs 19.5 miljardile ajaloolisele kirjele genealoogiauuringute kohta.

Visit myheritage.ee

Key Findings

We analyzed Myheritage.ee page load time and found that the first response time was 849 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

myheritage.ee performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

myheritage.ee

849 ms

www.myheritage.ee

578 ms

report-violation.php

416 ms

report-violation.php

313 ms

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

47 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 54% of them (34 requests) were addressed to the original Myheritage.ee, 44% (28 requests) were made to Cf.mhcache.com and 2% (1 request) were made to Myheritage-container.com. The less responsive or slowest element that took the longest time to load (849 ms) belongs to the original domain Myheritage.ee.

Page Optimization Overview & Recommendations

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

Content Size

300.5 kB

After Optimization

156.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myheritage.ee main page is 300.5 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 159.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 127.8 kB

  • Original 159.5 kB
  • After minification 156.7 kB
  • After compression 31.6 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 127.8 kB or 80% of the original size.

Image Optimization

-17%

Potential reduce by 13.9 kB

  • Original 82.0 kB
  • After minification 68.1 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 13.9 kB or 17% 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 43 B

  • Original 12.5 kB
  • After minification 12.5 kB
  • After compression 12.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 2.7 kB

  • Original 46.5 kB
  • After minification 46.5 kB
  • After compression 43.8 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. Myheritage.ee has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (10%)

Requests Now

29

After Optimization

26

  • 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.ee

myheritage.ee

849 ms

www.myheritage.ee

www.myheritage.ee

578 ms

report-violation.php

report-violation.php

416 ms

report-violation.php

report-violation.php

313 ms

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

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

47 ms

TypographyComponents_bundle_ltr_v245248b54d5b1a604ebb61c5220ab674.css

TypographyComponents_bundle_ltr_v245248b54d5b1a604ebb61c5220ab674.css

56 ms

CompanyHomePageDesktop_bundle_ltr_va697b272d14f29d579022e965e892f74.css

CompanyHomePageDesktop_bundle_ltr_va697b272d14f29d579022e965e892f74.css

91 ms

Themes_bundle_ltr_v02a01c035a1beaba691dc38455adca04.css

Themes_bundle_ltr_v02a01c035a1beaba691dc38455adca04.css

56 ms

report-violation.php

report-violation.php

230 ms

report-violation.php

report-violation.php

298 ms

report-violation.php

report-violation.php

135 ms

report-violation.php

report-violation.php

344 ms

report-violation.php

report-violation.php

265 ms

report-violation.php

report-violation.php

213 ms

report-violation.php

report-violation.php

412 ms

report-violation.php

report-violation.php

314 ms

report-violation.php

report-violation.php

252 ms

report-violation.php

report-violation.php

313 ms

report-violation.php

report-violation.php

350 ms

report-violation.php

report-violation.php

473 ms

report-violation.php

report-violation.php

415 ms

US-top-section-bg.webp

US-top-section-bg.webp

20 ms

myheritage_logo_inverse.svg

myheritage_logo_inverse.svg

19 ms

logo.svg

logo.svg

17 ms

dna-genetic-groups-section-bg.webp

dna-genetic-groups-section-bg.webp

17 ms

ethnicity_card_face.webp

ethnicity_card_face.webp

21 ms

deep-nostalgia.webp

deep-nostalgia.webp

22 ms

discovery-bg.webp

discovery-bg.webp

23 ms

community.webp

community.webp

22 ms

devices-logo-desktop.webp

devices-logo-desktop.webp

28 ms

tablet.webp

tablet.webp

23 ms

mobile.webp

mobile.webp

23 ms

desktop.webp

desktop.webp

25 ms

Logos_US_1.png

Logos_US_1.png

24 ms

Logos_US_2.png

Logos_US_2.png

24 ms

Logos_US_3.png

Logos_US_3.png

26 ms

Logos_US_4.png

Logos_US_4.png

24 ms

profile_1.jpg

profile_1.jpg

26 ms

profile_2.jpg

profile_2.jpg

27 ms

profile_3.jpg

profile_3.jpg

26 ms

profile_5.jpg

profile_5.jpg

28 ms

profile_4.jpg

profile_4.jpg

28 ms

profile_6.jpg

profile_6.jpg

29 ms

spacer.gif

spacer.gif

29 ms

report-violation.php

report-violation.php

414 ms

report-violation.php

report-violation.php

445 ms

report-violation.php

report-violation.php

488 ms

report-violation.php

report-violation.php

574 ms

report-violation.php

report-violation.php

532 ms

report-violation.php

report-violation.php

533 ms

report-violation.php

report-violation.php

557 ms

report-violation.php

report-violation.php

625 ms

report-violation.php

report-violation.php

584 ms

report-violation.php

report-violation.php

656 ms

report-violation.php

report-violation.php

685 ms

report-violation.php

report-violation.php

756 ms

report-violation.php

report-violation.php

714 ms

report-violation.php

report-violation.php

663 ms

report-violation.php

report-violation.php

746 ms

report-violation.php

report-violation.php

762 ms

report-violation.php

report-violation.php

809 ms

index.php

index.php

797 ms

GtmIframeLoaderBundled_v154b18d97b7a71ae5d3fd4e7071982d5.js

GtmIframeLoaderBundled_v154b18d97b7a71ae5d3fd4e7071982d5.js

3 ms

Accessibility Review

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

    ET

  • Language Claimed

    ET

  • Encoding

    ISO-8859-1

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

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: