1.5 sec in total
67 ms
1.1 sec
329 ms
Visit myheritage.de now to see the best up-to-date Myheritage content for Germany and also check out these interesting facts you probably never knew about myheritage.de
Erstellen Sie Ihren Familienstammbaum. Machen Sie einen MyHeritage DNA-Test für Abstammung und Gentests. Greifen Sie auf 21,0 Milliarden Historische Aufzeichnungen für genealogische Forschung zu.
Visit myheritage.deWe analyzed Myheritage.de page load time and found that the first response time was 67 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.de performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value4.3 s
41/100
25%
Value6.0 s
46/100
10%
Value820 ms
35/100
30%
Value0.031
100/100
15%
Value10.4 s
24/100
10%
67 ms
398 ms
153 ms
152 ms
33 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 59% of them (42 requests) were addressed to the original Myheritage.de, 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 (595 ms) relates to the external source Myheritage-container.com.
Page size can be reduced by 130.1 kB (63%)
206.4 kB
76.3 kB
In fact, the total size of Myheritage.de main page is 206.4 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. 25% of websites need less resources to load. HTML takes 144.2 kB which makes up the majority of the site volume.
Potential reduce by 112.9 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 112.9 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 8 (28%)
29
21
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.
myheritage.de
67 ms
www.myheritage.de
398 ms
report-violation.php
153 ms
report-violation.php
152 ms
minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css
33 ms
TypographyComponents_bundle_ltr_v1MVa7d91d757d08fdfb5fbb5b2b74f4fe7ao.css
49 ms
CompanyHomePageDesktop_bundle_ltr_v1MV5546d181ba37c8474f18e79a9caf4d66o.css
40 ms
Themes_bundle_ltr_v1MV508f72f03d1aa3e0986cf1d9e2ef4383o.css
50 ms
report-violation.php
91 ms
report-violation.php
91 ms
report-violation.php
117 ms
report-violation.php
137 ms
report-violation.php
168 ms
report-violation.php
167 ms
report-violation.php
148 ms
report-violation.php
167 ms
US-top-section-bg.webp
27 ms
myheritage_logo_inverse.svg
30 ms
AccessibilityButtonInverse.svg
29 ms
report-violation.php
138 ms
report-violation.php
212 ms
report-violation.php
211 ms
report-violation.php
210 ms
report-violation.php
223 ms
report-violation.php
225 ms
logo.svg
8 ms
dna-genetic-groups-section-bg.webp
33 ms
ethnicity_card_face.webp
13 ms
deep-nostalgia.webp
14 ms
discovery-bg.webp
15 ms
community.webp
13 ms
devices-logo-desktop.webp
14 ms
tablet.webp
15 ms
mobile.webp
15 ms
desktop.webp
16 ms
Logos_US_1.png
16 ms
Logos_US_2.png
17 ms
Logos_US_3.png
17 ms
Logos_US_4.png
16 ms
Logos_US_1.png
28 ms
Logos_US_2.png
18 ms
Logos_US_3.png
29 ms
Logos_US_4.png
27 ms
companyhomequotesus_sprite.png
27 ms
spacer.gif
28 ms
report-violation.php
200 ms
report-violation.php
236 ms
report-violation.php
255 ms
report-violation.php
252 ms
report-violation.php
287 ms
report-violation.php
263 ms
report-violation.php
275 ms
report-violation.php
297 ms
report-violation.php
335 ms
report-violation.php
315 ms
report-violation.php
374 ms
report-violation.php
556 ms
report-violation.php
365 ms
report-violation.php
331 ms
report-violation.php
368 ms
report-violation.php
383 ms
report-violation.php
447 ms
report-violation.php
444 ms
report-violation.php
483 ms
report-violation.php
482 ms
report-violation.php
545 ms
report-violation.php
551 ms
report-violation.php
552 ms
index.php
595 ms
report-violation.php
580 ms
GtmIframeLoaderBundled_v1MV34fb34db9bf5d1d7785ccee33165c501.js
3 ms
myheritage.de 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.de 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.de 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
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myheritage.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Myheritage.de 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.de
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: