Tools & Wizards About Us
familysearch.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

familysearch.com

Page Load Speed

642 ms in total

First Response

11 ms

Resources Loaded

580 ms

Page Rendered

51 ms

familysearch.com screenshot

About Website

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

Discover your family history. Explore the world’s largest collection of free family trees, genealogy records and resources.

Visit familysearch.com

Key Findings

We analyzed Familysearch.com page load time and found that the first response time was 11 ms and then it took 631 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

familysearch.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

familysearch.com

11 ms

www.familysearch.org

15 ms

www.familysearch.org

52 ms

25 ms

31 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Familysearch.com, 29% (5 requests) were made to Foundry.familysearch.org and 29% (5 requests) were made to Familysearch.org. The less responsive or slowest element that took the longest time to load (389 ms) relates to the external source Foundry.familysearch.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.2 kB (1%)

Content Size

788.8 kB

After Optimization

783.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Familysearch.com main page is 788.8 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. 20% of websites need less resources to load. Javascripts take 754.0 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 4.7 kB

  • Original 7.8 kB
  • After minification 7.6 kB
  • After compression 3.1 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 4.7 kB or 61% of the original size.

JavaScript Optimization

-0%

Potential reduce by 98 B

  • Original 754.0 kB
  • After minification 754.0 kB
  • After compression 753.9 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 328 B

  • Original 27.0 kB
  • After minification 27.0 kB
  • After compression 26.7 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. Familysearch.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (83%)

Requests Now

12

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

familysearch.com

familysearch.com

11 ms

www.familysearch.org

www.familysearch.org

15 ms

www.familysearch.org

www.familysearch.org

52 ms

25 ms

31 ms

Hemlock-Night-Gosper-this-go-this-Famids-not-of-

Hemlock-Night-Gosper-this-go-this-Famids-not-of-

6 ms

css

css

263 ms

css

css

389 ms

css

css

356 ms

css

css

344 ms

css

css

351 ms

dynatrace-20221104-prod.min-44bb9345beec8a984c2fca40385b4f41.js

dynatrace-20221104-prod.min-44bb9345beec8a984c2fca40385b4f41.js

47 ms

commonVendor.73f8d90842acc363.js

commonVendor.73f8d90842acc363.js

50 ms

72438.df016469c39387e0.js

72438.df016469c39387e0.js

68 ms

main.f5b4b6600ff4e25b.js

main.f5b4b6600ff4e25b.js

58 ms

72438.4410298d1254e113.css

72438.4410298d1254e113.css

58 ms

ruxitagent_A2NVfqru_10253221019152312.js

ruxitagent_A2NVfqru_10253221019152312.js

15 ms

Accessibility Review

familysearch.com accessibility score

98

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

familysearch.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

familysearch.com SEO score

95

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familysearch.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Familysearch.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

familysearch.com

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