Tools & Wizards About Us
familytreemaker.genealogy.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

familytreemaker.genealogy.com

Genealogy.com: Genforum & Family History Search

Page Load Speed

1.6 sec in total

First Response

74 ms

Resources Loaded

1.3 sec

Page Rendered

159 ms

familytreemaker.genealogy.com screenshot

About Website

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

Trace your ancestors' unique story and your family tree with help of the GenForum community and research archives on Genealogy.com.

Visit familytreemaker.genealogy.com

Key Findings

We analyzed Familytreemaker.genealogy.com page load time and found that the first response time was 74 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

familytreemaker.genealogy.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value3,530 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

familytreemaker.genealogy.com

74 ms

www.genealogy.com

252 ms

gtm.js

98 ms

wrapperMessagingWithoutDetection.js

44 ms

combo.css

23 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Familytreemaker.genealogy.com, 35% (21 requests) were made to Genealogy.com and 23% (14 requests) were made to Cdn.privacy-mgmt.com. The less responsive or slowest element that took the longest time to load (382 ms) relates to the external source Genealogy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.5 kB (14%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Familytreemaker.genealogy.com main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 41.5 kB

  • Original 60.1 kB
  • After minification 57.4 kB
  • After compression 18.6 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 41.5 kB or 69% of the original size.

Image Optimization

-72%

Potential reduce by 103.8 kB

  • Original 143.2 kB
  • After minification 39.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. Obviously, Family Treemaker Genealogy needs image optimization as it can save up to 103.8 kB or 72% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 21.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 998.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.

CSS Optimization

-28%

Potential reduce by 8.2 kB

  • Original 29.7 kB
  • After minification 29.7 kB
  • After compression 21.5 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. Familytreemaker.genealogy.com needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (69%)

Requests Now

49

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

familytreemaker.genealogy.com

familytreemaker.genealogy.com

74 ms

www.genealogy.com

www.genealogy.com

252 ms

gtm.js

gtm.js

98 ms

wrapperMessagingWithoutDetection.js

wrapperMessagingWithoutDetection.js

44 ms

combo.css

combo.css

23 ms

gcom.css

gcom.css

92 ms

tooltipster.css

tooltipster.css

39 ms

selectordie.css

selectordie.css

149 ms

selectordie_theme_genealogy.css

selectordie_theme_genealogy.css

88 ms

jquery-1.7.0.min.js

jquery-1.7.0.min.js

91 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

87 ms

selectordie.js

selectordie.js

95 ms

bundle.js

bundle.js

147 ms

adb.5781260.min.js

adb.5781260.min.js

92 ms

gpt.js

gpt.js

182 ms

apstag.js

apstag.js

92 ms

custom.1a28bbe027bd69b90733.bundle.js

custom.1a28bbe027bd69b90733.bundle.js

68 ms

gdpr-tcf.326dc0fcac2e9cce1493.bundle.js

gdpr-tcf.326dc0fcac2e9cce1493.bundle.js

74 ms

usnat.6df6ca45594f51824f67.bundle.js

usnat.6df6ca45594f51824f67.bundle.js

107 ms

get_site_data

get_site_data

99 ms

apstag.js

apstag.js

225 ms

js

js

90 ms

css

css

168 ms

meta-data

meta-data

148 ms

messages

messages

147 ms

source-sans-pro.woff

source-sans-pro.woff

367 ms

source-sans-pro-light.woff

source-sans-pro-light.woff

145 ms

source-sans-pro-semi-bold.woff

source-sans-pro-semi-bold.woff

144 ms

source-sans-pro-bold.woff

source-sans-pro-bold.woff

133 ms

1528ad08-abbd-4ec4-8d43-0727f6c0342e.js

1528ad08-abbd-4ec4-8d43-0727f6c0342e.js

184 ms

genealogy-logo.png

genealogy-logo.png

26 ms

truck5.jpg

truck5.jpg

258 ms

question_icon.png

question_icon.png

258 ms

tree.png

tree.png

259 ms

tracking.js

tracking.js

156 ms

sourcesanspro-regular.woff

sourcesanspro-regular.woff

322 ms

sourcesanspro-semibold.woff

sourcesanspro-semibold.woff

234 ms

amatic-bold.woff

amatic-bold.woff

382 ms

1528ad08-abbd-4ec4-8d43-0727f6c0342e.js

1528ad08-abbd-4ec4-8d43-0727f6c0342e.js

281 ms

pubads_impl.js

pubads_impl.js

97 ms

v2fkjaTCp6wdcVoWHDZUFStuNwd6gUyIGAsGBonfNnyccO_4dJiKRago

v2fkjaTCp6wdcVoWHDZUFStuNwd6gUyIGAsGBonfNnyccO_4dJiKRago

314 ms

adb.5781260.cr.b.js

adb.5781260.cr.b.js

132 ms

adb.5781260.pb.js

adb.5781260.pb.js

166 ms

pv-data

pv-data

103 ms

sourcesanspro-bold.woff

sourcesanspro-bold.woff

337 ms

index.html

index.html

93 ms

72deb316-81a2-4126-92d6-6bd1e1dd9315.js

72deb316-81a2-4126-92d6-6bd1e1dd9315.js

78 ms

72deb316-81a2-4126-92d6-6bd1e1dd9315-hb.js

72deb316-81a2-4126-92d6-6bd1e1dd9315-hb.js

127 ms

72deb316-81a2-4126-92d6-6bd1e1dd9315-dmp.js

72deb316-81a2-4126-92d6-6bd1e1dd9315-dmp.js

172 ms

170 ms

index.html

index.html

168 ms

utag.js

utag.js

177 ms

polyfills.b0798.js

polyfills.b0798.js

87 ms

Custom.32167.js

Custom.32167.js

99 ms

Custom.318f9.css

Custom.318f9.css

88 ms

pv-data

pv-data

218 ms

pv-data

pv-data

151 ms

authIframe.js

authIframe.js

14 ms

skeleton.gif

skeleton.gif

39 ms

nr-spa-1216.min.js

nr-spa-1216.min.js

12 ms

Accessibility Review

familytreemaker.genealogy.com accessibility score

89

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.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

familytreemaker.genealogy.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

familytreemaker.genealogy.com SEO score

94

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familytreemaker.genealogy.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Familytreemaker.genealogy.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

familytreemaker.genealogy.com

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