Tools & Wizards About Us
genealogyexplained.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

genealogyexplained.com

Genealogy Explained: Learn how to Build Your Family Tree

Page Load Speed

1.6 sec in total

First Response

89 ms

Resources Loaded

795 ms

Page Rendered

677 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 89 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

genealogyexplained.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

genealogyexplained.com

89 ms

www.genealogyexplained.com

69 ms

style.min.css

16 ms

surecart.css

37 ms

style.css

32 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original Genealogyexplained.com, 2% (1 request) were made to Js.surecart.com and 2% (1 request) were made to Clickstreammedia.ck.page. The less responsive or slowest element that took the longest time to load (189 ms) relates to the external source Clickstreammedia.ck.page.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.4 kB (17%)

Content Size

679.9 kB

After Optimization

566.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 104.1 kB

  • Original 126.1 kB
  • After minification 126.1 kB
  • After compression 22.0 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 104.1 kB or 83% 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 238 B

  • Original 73.7 kB
  • After minification 73.7 kB
  • After compression 73.5 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.

CSS Optimization

-1%

Potential reduce by 509 B

  • Original 38.1 kB
  • After minification 38.1 kB
  • After compression 37.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. Genealogyexplained.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (51%)

Requests Now

61

After Optimization

30

  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genealogy Explained. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

genealogyexplained.com

genealogyexplained.com

89 ms

www.genealogyexplained.com

www.genealogyexplained.com

69 ms

style.min.css

style.min.css

16 ms

surecart.css

surecart.css

37 ms

style.css

style.css

32 ms

broadcasts.css

broadcasts.css

45 ms

button.css

button.css

31 ms

form.css

form.css

31 ms

style.min.css

style.min.css

28 ms

all.min.css

all.min.css

44 ms

style.css

style.css

41 ms

wp-featherlight.min.css

wp-featherlight.min.css

39 ms

style-3759.css

style-3759.css

45 ms

offside.min.css

offside.min.css

47 ms

navigation-branding.min.css

navigation-branding.min.css

67 ms

affiliates

affiliates

116 ms

jquery.min.js

jquery.min.js

53 ms

offside.min.js

offside.min.js

49 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

52 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

56 ms

wp-polyfill.min.js

wp-polyfill.min.js

53 ms

hooks.min.js

hooks.min.js

62 ms

i18n.min.js

i18n.min.js

61 ms

static-loader.js

static-loader.js

111 ms

broadcasts.js

broadcasts.js

112 ms

commerce.js

commerce.js

189 ms

convertkit.js

convertkit.js

163 ms

ta.js

ta.js

163 ms

menu.min.js

menu.min.js

165 ms

navigation-search.min.js

navigation-search.min.js

166 ms

lazyload.min.js

lazyload.min.js

164 ms

wpFeatherlight.pkgd.min.js

wpFeatherlight.pkgd.min.js

163 ms

pminstantpage.min.js

pminstantpage.min.js

166 ms

gtm.js

gtm.js

187 ms

fbevents.js

fbevents.js

116 ms

logo2.svg

logo2.svg

126 ms

research-process.jpg

research-process.jpg

125 ms

genealogy-websites.jpg

genealogy-websites.jpg

129 ms

genetic-genealogy.jpg

genetic-genealogy.jpg

127 ms

genealogy-software-large.jpg

genealogy-software-large.jpg

124 ms

research.jpg

research.jpg

127 ms

kinship.jpg

kinship.jpg

127 ms

family-tree.svg

family-tree.svg

51 ms

ancestry.png

ancestry.png

56 ms

legacy.png

legacy.png

56 ms

myheritage-1.png

myheritage-1.png

56 ms

cnn.png

cnn.png

57 ms

genealogy-explained-forbes.png

genealogy-explained-forbes.png

59 ms

Wired_logo.png

Wired_logo.png

58 ms

toronto-sun-logo.png

toronto-sun-logo.png

59 ms

USA-Today-logo.png

USA-Today-logo.png

58 ms

fox_10_phoenix_logo.png

fox_10_phoenix_logo.png

61 ms

abc-15-arizona-logo.png

abc-15-arizona-logo.png

60 ms

start-genealogy-research-gray.jpg

start-genealogy-research-gray.jpg

62 ms

genealogical-proof-standard.png

genealogical-proof-standard.png

68 ms

free-genealogy-websites.png

free-genealogy-websites.png

95 ms

best-dna-test.png

best-dna-test.png

98 ms

23andme-vs-ancestry-dna.png

23andme-vs-ancestry-dna.png

73 ms

genealogy-software.jpg

genealogy-software.jpg

73 ms

ancestry-review.png

ancestry-review.png

74 ms

myheritage.png

myheritage.png

96 ms

familysearch-review.png

familysearch-review.png

95 ms

logo-white.svg

logo-white.svg

96 ms

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

High

Missing source maps for large first-party JavaScript

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

genealogyexplained.com

Open Graph data is detected on the main page of Genealogy Explained. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: