Tools & Wizards About Us
landing.ancestry.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

landing.ancestry.com

Ancestry® | Family Tree, Genealogy & Family History Records

Page Load Speed

1.1 sec in total

First Response

72 ms

Resources Loaded

720 ms

Page Rendered

341 ms

landing.ancestry.com screenshot

About Website

Welcome to landing.ancestry.com homepage info - get ready to check Landing Ancestry best content for United States right away, or after learning these important things about landing.ancestry.com

Ancestry® helps you understand your genealogy. A family tree takes you back generations—the world's largest collection of online family history records makes it easy to trace your lineage.

Visit landing.ancestry.com

Key Findings

We analyzed Landing.ancestry.com page load time and found that the first response time was 72 ms and then it took 1.1 sec 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

landing.ancestry.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value6,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

72 ms

www.ancestry.com

53 ms

request-header-overrides.js

44 ms

unified-tracking-stub.js

47 ms

p13n.min.js

80 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Landing.ancestry.com, 25% (14 requests) were made to Ancestrycdn.com and 5% (3 requests) were made to Ancestry.com. The less responsive or slowest element that took the longest time to load (356 ms) relates to the external source Cmsasset.ancestrycdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 646.3 kB (52%)

Content Size

1.2 MB

After Optimization

600.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 187.7 kB

  • Original 229.4 kB
  • After minification 220.9 kB
  • After compression 41.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 187.7 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 962 B

  • Original 373.0 kB
  • After minification 372.0 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. Landing Ancestry images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 315.5 kB

  • Original 474.2 kB
  • After minification 474.2 kB
  • After compression 158.7 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 315.5 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 142.2 kB

  • Original 170.3 kB
  • After minification 170.2 kB
  • After compression 28.0 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. Landing.ancestry.com needs all CSS files to be minified and compressed as it can save up to 142.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (75%)

Requests Now

51

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

72 ms

www.ancestry.com

www.ancestry.com

53 ms

request-header-overrides.js

request-header-overrides.js

44 ms

unified-tracking-stub.js

unified-tracking-stub.js

47 ms

p13n.min.js

p13n.min.js

80 ms

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

54 ms

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

67 ms

at.js

at.js

79 ms

core.css

core.css

91 ms

clientlib-marketing.min.ACSHASH54477308e0049c25a255a67e18d0e9b8810435f0b2de13dfd5ac4861c11f2ac7.css

clientlib-marketing.min.ACSHASH54477308e0049c25a255a67e18d0e9b8810435f0b2de13dfd5ac4861c11f2ac7.css

44 ms

clientlib-marketing.min.ACSHASHb7cf03adbdd01d757f6a281ae2314f545c8940dd44ccbf44aca25477ba234579.js

clientlib-marketing.min.ACSHASHb7cf03adbdd01d757f6a281ae2314f545c8940dd44ccbf44aca25477ba234579.js

82 ms

geo-redirector.min.js

geo-redirector.min.js

65 ms

banners-injection.min.js

banners-injection.min.js

82 ms

ajax-manager.js

ajax-manager.js

85 ms

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

81 ms

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

79 ms

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

85 ms

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

84 ms

clientlib-global.min.ACSHASH9f7e65e6ad1f9a8a331807b813457463824e0cc38a08031bd0bf8f1e374681b9.js

clientlib-global.min.ACSHASH9f7e65e6ad1f9a8a331807b813457463824e0cc38a08031bd0bf8f1e374681b9.js

84 ms

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

85 ms

core.js

core.js

85 ms

switch.js

switch.js

84 ms

carousel.js

carousel.js

84 ms

clientlib-site-split.min.ACSHASHcb51b8a4edd967da941de5d4eeb68cf4338ee6225631e32a8c61bc3cac897b51.js

clientlib-site-split.min.ACSHASHcb51b8a4edd967da941de5d4eeb68cf4338ee6225631e32a8c61bc3cac897b51.js

356 ms

clientlib-dependencies.min.ACSHASH327e7e87486b772ffe78af718dedbdf12a90eccfb9bc41c5a6b62d9adf8c2d7a.js

clientlib-dependencies.min.ACSHASH327e7e87486b772ffe78af718dedbdf12a90eccfb9bc41c5a6b62d9adf8c2d7a.js

242 ms

tracking.js

tracking.js

83 ms

moment.min.ACSHASH8dbac393b462220216deb2cd3504d2007049cf9a595f24cfaa6ae8bc55262ff7.js

moment.min.ACSHASH8dbac393b462220216deb2cd3504d2007049cf9a595f24cfaa6ae8bc55262ff7.js

239 ms

clientlib-footer-region.min.ACSHASHfdb4e1665217d8642241b7a7d5e436447eae419365662051d63e7e93ddac4081.js

clientlib-footer-region.min.ACSHASHfdb4e1665217d8642241b7a7d5e436447eae419365662051d63e7e93ddac4081.js

239 ms

clientlib-button.min.ACSHASH4a3a91773f9d5546608a24766ba4870f7c3b774d3155cd07d73ff1b0508a9b86.js

clientlib-button.min.ACSHASH4a3a91773f9d5546608a24766ba4870f7c3b774d3155cd07d73ff1b0508a9b86.js

239 ms

clientlib-itemlist.min.ACSHASH8cefe8c507732925317d7f6e7b86eeb53e191766a3281b4bd2d0943460ab43e7.js

clientlib-itemlist.min.ACSHASH8cefe8c507732925317d7f6e7b86eeb53e191766a3281b4bd2d0943460ab43e7.js

239 ms

clientlib-image.min.ACSHASHfa8f85160342f2830321e6aeaf845395b5b09bee1768fa2552b6c0c2114a418e.js

clientlib-image.min.ACSHASHfa8f85160342f2830321e6aeaf845395b5b09bee1768fa2552b6c0c2114a418e.js

328 ms

clientlib-header.min.ACSHASH48da59359cbda79960f2ca69e5b8f1334401d81a524c5ce78f13a5c2b0c595b3.js

clientlib-header.min.ACSHASH48da59359cbda79960f2ca69e5b8f1334401d81a524c5ce78f13a5c2b0c595b3.js

316 ms

clientlib-badgecampaign.min.ACSHASHfebcf1feccc0f4825c56620e02bff394ac872dc63f3a49701d0c324dc79d85af.js

clientlib-badgecampaign.min.ACSHASHfebcf1feccc0f4825c56620e02bff394ac872dc63f3a49701d0c324dc79d85af.js

315 ms

clientlib-linklist.min.ACSHASHb06ec9b19a8fb45f12a42891b0248e3e4c83343651d5b87bef02befc6d7c7742.js

clientlib-linklist.min.ACSHASHb06ec9b19a8fb45f12a42891b0248e3e4c83343651d5b87bef02befc6d7c7742.js

316 ms

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

316 ms

clientlib-webpart.min.ACSHASH33a8ee2fc5b0cbe1027cc17157849d7c1560a7ec441003fdbf36d734ae9d479c.js

clientlib-webpart.min.ACSHASH33a8ee2fc5b0cbe1027cc17157849d7c1560a7ec441003fdbf36d734ae9d479c.js

326 ms

clientlib-container.min.ACSHASH9a1842ea9d4f6cfdbc00829e7c9ce8cfbe4f2446e04616e35f9c8589484c3d0b.js

clientlib-container.min.ACSHASH9a1842ea9d4f6cfdbc00829e7c9ce8cfbe4f2446e04616e35f9c8589484c3d0b.js

327 ms

clientlib-text.min.ACSHASH6b1f1f7ad9f15801be6f5edbd56461d4f427db5ce098177d8d12166511252a43.js

clientlib-text.min.ACSHASH6b1f1f7ad9f15801be6f5edbd56461d4f427db5ce098177d8d12166511252a43.js

326 ms

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

326 ms

unified-tracking.js

unified-tracking.js

239 ms

gtm.js

gtm.js

336 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

189 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

126 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

185 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

147 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

185 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

186 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

187 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

244 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

186 ms

utag.js

utag.js

115 ms

false

false

235 ms

ancestry-icon.woff

ancestry-icon.woff

94 ms

ancestry-icon.woff

ancestry-icon.woff

93 ms

main.js

main.js

56 ms

Accessibility Review

landing.ancestry.com accessibility score

100

Accessibility Issues

Best Practices

landing.ancestry.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

landing.ancestry.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Landing.ancestry.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 Landing.ancestry.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

landing.ancestry.com

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