Tools & Wizards About Us
maps.familysearch.org screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

maps.familysearch.org

Page Load Speed

976 ms in total

First Response

35 ms

Resources Loaded

666 ms

Page Rendered

275 ms

maps.familysearch.org screenshot

About Website

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

Visit maps.familysearch.org

Key Findings

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

Performance Metrics

maps.familysearch.org performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.329

35/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

maps.familysearch.org

35 ms

jquery-ui-1.8.13.custom.css

12 ms

tab.css

17 ms

banner.css

18 ms

button.css

13 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 77% of them (49 requests) were addressed to the original Maps.familysearch.org, 13% (8 requests) were made to Serverapi.arcgisonline.com and 3% (2 requests) were made to Ecn.dev.virtualearth.net. The less responsive or slowest element that took the longest time to load (183 ms) relates to the external source Ldscdn.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (72%)

Content Size

1.5 MB

After Optimization

409.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Maps.familysearch.org main page is 1.5 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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 24.2 kB

  • Original 29.0 kB
  • After minification 18.0 kB
  • After compression 4.8 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. This page needs HTML code to be minified as it can gain 11.0 kB, which is 38% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.2 kB or 84% of the original size.

Image Optimization

-35%

Potential reduce by 50.1 kB

  • Original 142.7 kB
  • After minification 92.6 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, Maps Familysearch needs image optimization as it can save up to 50.1 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 887.6 kB

  • Original 1.2 MB
  • After minification 951.6 kB
  • After compression 289.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 887.6 kB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 102.0 kB

  • Original 125.1 kB
  • After minification 108.7 kB
  • After compression 23.1 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. Maps.familysearch.org needs all CSS files to be minified and compressed as it can save up to 102.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (84%)

Requests Now

62

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

maps.familysearch.org

maps.familysearch.org

35 ms

jquery-ui-1.8.13.custom.css

jquery-ui-1.8.13.custom.css

12 ms

tab.css

tab.css

17 ms

banner.css

banner.css

18 ms

button.css

button.css

13 ms

famSearch.css

famSearch.css

19 ms

main.css

main.css

14 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

39 ms

jquery-ui-1.8.13.custom.min.js

jquery-ui-1.8.13.custom.min.js

39 ms

famSearch.js

famSearch.js

25 ms

prototypes.js

prototypes.js

16 ms

Layer.js

Layer.js

25 ms

js

js

31 ms

85 ms

mapcontrol.ashx

mapcontrol.ashx

80 ms

Map.js

Map.js

25 ms

Jurisdiction.js

Jurisdiction.js

24 ms

Record.js

Record.js

25 ms

EsriService.js

EsriService.js

24 ms

ApiService.js

ApiService.js

27 ms

arcgisLink.js

arcgisLink.js

32 ms

UIControllers.js

UIControllers.js

30 ms

mapController.js

mapController.js

31 ms

searchForm.js

searchForm.js

34 ms

DataType.js

DataType.js

73 ms

EJ1851.js

EJ1851.js

72 ms

EJ1851ParishInfoFormat.js

EJ1851ParishInfoFormat.js

71 ms

USA.js

USA.js

74 ms

LayerController.js

LayerController.js

74 ms

initialize.js

initialize.js

73 ms

FamilyTree.js

FamilyTree.js

72 ms

popupWindows.js

popupWindows.js

72 ms

analytics.js

analytics.js

73 ms

bg.png

bg.png

57 ms

jsapi.css

jsapi.css

52 ms

InfoWindow.css

InfoWindow.css

53 ms

svg.xd.js

svg.xd.js

46 ms

jsapi_en-us.xd.js

jsapi_en-us.xd.js

38 ms

veapicore.js

veapicore.js

80 ms

shape.xd.js

shape.xd.js

7 ms

path.xd.js

path.xd.js

5 ms

s_code_ldsall.js

s_code_ldsall.js

183 ms

firmament.jpg

firmament.jpg

38 ms

blank.gif

blank.gif

27 ms

Loading.png

Loading.png

25 ms

ajaxLoader.gif

ajaxLoader.gif

26 ms

gradient_bc.gif

gradient_bc.gif

25 ms

print_16.gif

print_16.gif

25 ms

feedback_16.gif

feedback_16.gif

26 ms

help.png

help.png

27 ms

world.gif

world.gif

32 ms

tabs-top.gif

tabs-top.gif

27 ms

tabs-top-right.gif

tabs-top-right.gif

28 ms

tab-left-a.gif

tab-left-a.gif

26 ms

tab-right-a.gif

tab-right-a.gif

29 ms

tab-left.gif

tab-left.gif

31 ms

bkg-button.gif

bkg-button.gif

32 ms

yellow_dot.png

yellow_dot.png

36 ms

close.gif

close.gif

33 ms

familysearch_logo.png

familysearch_logo.png

34 ms

feedback_button.gif

feedback_button.gif

34 ms

validateSession

validateSession

76 ms

LDSGlobal.js

LDSGlobal.js

148 ms

ga.js

ga.js

5 ms

Accessibility Review

maps.familysearch.org accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

maps.familysearch.org best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

maps.familysearch.org SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maps.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 Maps.familysearch.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

maps.familysearch.org

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