1.9 sec in total
531 ms
1 sec
323 ms
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 21,0 mld archiwalnych rekordów w trakcie genealogicznych poszukiwań.
Visit myheritage.plWe analyzed Myheritage.pl page load time and found that the first response time was 531 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
myheritage.pl performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value5.0 s
27/100
25%
Value7.4 s
27/100
10%
Value1,080 ms
24/100
30%
Value0.047
99/100
15%
Value11.8 s
17/100
10%
531 ms
189 ms
76 ms
49 ms
29 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 39% of them (18 requests) were addressed to the original Myheritage.pl, 59% (27 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 (531 ms) belongs to the original domain Myheritage.pl.
Page size can be reduced by 130.4 kB (63%)
206.5 kB
76.1 kB
In fact, the total size of Myheritage.pl main page is 206.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 144.5 kB which makes up the majority of the site volume.
Potential reduce by 113.2 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.2 kB or 78% of the original size.
Potential reduce by 17.2 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.
Potential reduce by 12 B
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.
Number of requests can be reduced by 3 (11%)
28
25
The browser has sent 28 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.
myheritage.pl
531 ms
www.myheritage.pl
189 ms
report-violation.php
76 ms
report-violation.php
49 ms
minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css
29 ms
TypographyComponents_bundle_ltr_v1MVa7d91d757d08fdfb5fbb5b2b74f4fe7ao.css
43 ms
CompanyHomePageDesktop_bundle_ltr_v1MV5546d181ba37c8474f18e79a9caf4d66o.css
34 ms
Themes_bundle_ltr_v1MV508f72f03d1aa3e0986cf1d9e2ef4383o.css
43 ms
report-violation.php
84 ms
report-violation.php
83 ms
report-violation.php
46 ms
report-violation.php
73 ms
report-violation.php
94 ms
report-violation.php
90 ms
report-violation.php
101 ms
report-violation.php
91 ms
US-top-section-bg.webp
38 ms
myheritage_logo_inverse.svg
42 ms
logo.svg
27 ms
dna-genetic-groups-section-bg.webp
25 ms
ethnicity_card_face.webp
27 ms
deep-nostalgia.webp
31 ms
discovery-bg.webp
32 ms
community.webp
30 ms
devices-logo-desktop.webp
31 ms
tablet.webp
31 ms
mobile.webp
31 ms
desktop.webp
35 ms
Logos_US_1.png
35 ms
Logos_US_2.png
33 ms
Logos_US_3.png
34 ms
Logos_US_4.png
31 ms
Logos_US_1.png
32 ms
Logos_US_2.png
37 ms
Logos_US_3.png
37 ms
Logos_US_4.png
37 ms
companyhomequotesus_sprite.png
37 ms
spacer.gif
36 ms
report-violation.php
73 ms
report-violation.php
125 ms
report-violation.php
126 ms
report-violation.php
124 ms
report-violation.php
126 ms
report-violation.php
125 ms
index.php
73 ms
GtmIframeLoaderBundled_v1MV82db7c63f4d024337ddf28f7d826f0e7.js
4 ms
myheritage.pl accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
myheritage.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
myheritage.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
PL
PL
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 it matches the claimed language. 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.
myheritage.pl
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: