Report Summary

  • 62

    Performance

    Renders faster than
    76% 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

  • 98

    SEO

    Google-friendlier than
    92% of websites

Page Load Speed

979 ms in total

First Response

8 ms

Resources Loaded

921 ms

Page Rendered

50 ms

About Website

Welcome to library.familysearch.org homepage info - get ready to check Library Familysearch best content for United States right away, or after learning these important things about library.familysearch.org

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

Visit library.familysearch.org

Key Findings

We analyzed Library.familysearch.org page load time and found that the first response time was 8 ms and then it took 971 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

library.familysearch.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

library.familysearch.org

8 ms

www.familysearch.org

119 ms

www.familysearch.org

159 ms

84 ms

110 ms

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

Page Optimization Overview & Recommendations

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

Content Size

795.7 kB

After Optimization

790.7 kB

In fact, the total size of Library.familysearch.org main page is 795.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. Javascripts take 761.2 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 4.6 kB

  • Original 7.6 kB
  • After minification 7.4 kB
  • After compression 3.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 4.6 kB or 61% of the original size.

JavaScript Optimization

-0%

Potential reduce by 39 B

  • Original 761.2 kB
  • After minification 761.2 kB
  • After compression 761.1 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 373 B

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 26.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. Library.familysearch.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (82%)

Requests Now

11

After Optimization

2

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Library 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 5 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

library.familysearch.org 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

library.familysearch.org 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

library.familysearch.org SEO score

98

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 Library.familysearch.org 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 Library.familysearch.org 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 Library 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: