Tools & Wizards About Us

Report Summary

  • 33

    Performance

    Renders faster than
    53% 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.no

Ubegrenset Slektstre, Genealogi, Slektshistorie og DNA testing

Page Load Speed

2.1 sec in total

First Response

546 ms

Resources Loaded

1.2 sec

Page Rendered

317 ms

About Website

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

Opprett ditt slektstre. Ta en MyHeritage DNA test for testing av aner og genetikk. Få tilgang til 36,9 milliarder historiske dokumenter for slektsforskning.

Visit myheritage.no

Key Findings

We analyzed Myheritage.no page load time and found that the first response time was 546 ms and then it took 1.5 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.

Performance Metrics

myheritage.no performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

myheritage.no

546 ms

www.myheritage.no

312 ms

report-violation.php

56 ms

report-violation.php

51 ms

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

30 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 47% of them (26 requests) were addressed to the original Myheritage.no, 51% (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 (546 ms) belongs to the original domain Myheritage.no.

Page Optimization Overview & Recommendations

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

Content Size

205.7 kB

After Optimization

76.2 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-78%

Potential reduce by 112.2 kB

  • Original 143.0 kB
  • After minification 140.2 kB
  • After compression 30.7 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.2 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 52 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.

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

Accessibility Review

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

    NO

  • Language Claimed

    NO

  • Encoding

    ISO-8859-1

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