Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

myheritage.pl

Bezpłatne drzewo rodowe, genealogia, historia rodziny i testy DNA

Page Load Speed

5.3 sec in total

First Response

140 ms

Resources Loaded

2.2 sec

Page Rendered

2.9 sec

myheritage.pl screenshot

About Website

Welcome to myheritage.pl homepage info - get ready to check Myheritage best content for Poland right away, or after learning these important things about myheritage.pl

Stwórz swoje własne drzewo genealogiczne. Wykonaj test MyHeritage DNA do celów genetycznych i genealogicznych. Skorzystaj z 19,8 mld archiwalnych rekordów w trakcie genealogicznych poszukiwań.

Visit myheritage.pl

Key Findings

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

Performance Metrics

myheritage.pl performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

65/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.5 s

37/100

10%

Network Requests Diagram

myheritage.pl

140 ms

www.myheritage.pl

300 ms

base-responsive_ltr_v1455627155o.css

209 ms

CompanyHome_ltr_v1452592749o.css

201 ms

jquery-all-combined_v1453031109.js

327 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 13% of them (3 requests) were addressed to the original Myheritage.pl, 83% (19 requests) were made to D.mhcache.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (417 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

984.3 kB

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

HTML Optimization

-85%

Potential reduce by 88.2 kB

  • Original 103.8 kB
  • After minification 64.2 kB
  • After compression 15.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. 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.2 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 10.3 kB

  • Original 699.4 kB
  • After minification 689.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. Myheritage images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 702.3 kB

  • Original 929.2 kB
  • After minification 819.1 kB
  • After compression 226.9 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 702.3 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 276.2 kB

  • Original 328.9 kB
  • After minification 325.5 kB
  • After compression 52.6 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.pl needs all CSS files to be minified and compressed as it can save up to 276.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

21

After Optimization

12

The browser has sent 21 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 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

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

    PL

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myheritage.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish 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 Myheritage.pl 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

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: