Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

genealogyexplained.com

Genealogy Explained: Learn how to Build Your Family Tree

Page Load Speed

1.5 sec in total

First Response

63 ms

Resources Loaded

765 ms

Page Rendered

673 ms

genealogyexplained.com screenshot

About Website

Visit genealogyexplained.com now to see the best up-to-date Genealogy Explained content for United States and also check out these interesting facts you probably never knew about genealogyexplained.com

Genealogy Explained is an educational site designed to help weekend-warrior genealogists learn how to climb their family trees.

Visit genealogyexplained.com

Key Findings

We analyzed Genealogyexplained.com page load time and found that the first response time was 63 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 25% of websites can load faster.

Performance Metrics

genealogyexplained.com performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

www.genealogyexplained.com

63 ms

lazyload.min.js

14 ms

logo2.svg

23 ms

research-process.jpg

58 ms

genealogy-websites.jpg

27 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that all of those requests were addressed to Genealogyexplained.com and no external sources were called. The less responsive or slowest element that took the longest time to load (147 ms) belongs to the original domain Genealogyexplained.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.7 kB (22%)

Content Size

599.7 kB

After Optimization

467.9 kB

In fact, the total size of Genealogyexplained.com main page is 599.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. 15% of websites need less resources to load. Images take 442.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 123.2 kB

  • Original 154.7 kB
  • After minification 154.7 kB
  • After compression 31.5 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 123.2 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 8.5 kB

  • Original 442.0 kB
  • After minification 433.4 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. Genealogy Explained images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 5 B

  • Original 3.1 kB
  • After minification 3.1 kB
  • After compression 3.0 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

We found no issues to fix!

Requests Now

29

After Optimization

29

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genealogy Explained. According to our analytics all requests are already optimized.

Accessibility Review

genealogyexplained.com accessibility score

97

Accessibility Issues

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

genealogyexplained.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

genealogyexplained.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genealogyexplained.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Genealogyexplained.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Genealogy Explained. 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: