Tools & Wizards About Us
ancestry.app.link screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

ancestry.app.link

Ancestry® | Family Tree, Genealogy & Family History Records

Page Load Speed

1.5 sec in total

First Response

77 ms

Resources Loaded

1.1 sec

Page Rendered

309 ms

ancestry.app.link screenshot

About Website

Visit ancestry.app.link now to see the best up-to-date Ancestry App content for United States and also check out these interesting facts you probably never knew about ancestry.app.link

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 ancestry.app.link

Key Findings

We analyzed Ancestry.app.link page load time and found that the first response time was 77 ms and then it took 1.4 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

ancestry.app.link performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

www.ancestry.com

77 ms

gtm.js

255 ms

p13n.min.js

41 ms

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

62 ms

clientlib-js-base.min.ACSHASH91e14a91d138b585d6ed64b14e2e10349131eab365f65bdb2c9979a3b6d75919.js

77 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ancestry.app.link, 26% (14 requests) were made to Ancestrycdn.com and 4% (2 requests) were made to Ancestry.com. The less responsive or slowest element that took the longest time to load (446 ms) relates to the external source Cmsasset.ancestrycdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 596.3 kB (57%)

Content Size

1.0 MB

After Optimization

448.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ancestry.app.link main page is 1.0 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. 70% of websites need less resources to load. Javascripts take 386.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 216.0 kB

  • Original 263.5 kB
  • After minification 252.0 kB
  • After compression 47.5 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 216.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 220.5 kB
  • After minification 219.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. Ancestry App images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 234.2 kB

  • Original 386.9 kB
  • After minification 386.9 kB
  • After compression 152.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 234.2 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 145.0 kB

  • Original 174.1 kB
  • After minification 174.0 kB
  • After compression 29.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. Ancestry.app.link needs all CSS files to be minified and compressed as it can save up to 145.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (78%)

Requests Now

50

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ancestry.com

www.ancestry.com

77 ms

gtm.js

gtm.js

255 ms

p13n.min.js

p13n.min.js

41 ms

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

62 ms

clientlib-js-base.min.ACSHASH91e14a91d138b585d6ed64b14e2e10349131eab365f65bdb2c9979a3b6d75919.js

clientlib-js-base.min.ACSHASH91e14a91d138b585d6ed64b14e2e10349131eab365f65bdb2c9979a3b6d75919.js

77 ms

at.js

at.js

73 ms

core.css

core.css

51 ms

clientlib-marketing.min.ACSHASH54477308e0049c25a255a67e18d0e9b8810435f0b2de13dfd5ac4861c11f2ac7.css

clientlib-marketing.min.ACSHASH54477308e0049c25a255a67e18d0e9b8810435f0b2de13dfd5ac4861c11f2ac7.css

76 ms

clientlib-marketing.min.ACSHASHb7cf03adbdd01d757f6a281ae2314f545c8940dd44ccbf44aca25477ba234579.js

clientlib-marketing.min.ACSHASHb7cf03adbdd01d757f6a281ae2314f545c8940dd44ccbf44aca25477ba234579.js

59 ms

geo-redirector.min.js

geo-redirector.min.js

47 ms

banners-injection.min.js

banners-injection.min.js

49 ms

ajax-manager.js

ajax-manager.js

52 ms

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

70 ms

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

70 ms

clientlib-global.min.ACSHASH9f3783745a1a9ae6045b6276f30e48bf7d0dc0e39493cc6545013db14d5198eb.js

clientlib-global.min.ACSHASH9f3783745a1a9ae6045b6276f30e48bf7d0dc0e39493cc6545013db14d5198eb.js

71 ms

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

71 ms

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

233 ms

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

230 ms

core.js

core.js

53 ms

switch.js

switch.js

51 ms

carousel.js

carousel.js

54 ms

clientlib-site-split.min.ACSHASHe53b0e69511b86b06f6570312876927b357114c279c82a1d5e8fa5d5e3a971c2.js

clientlib-site-split.min.ACSHASHe53b0e69511b86b06f6570312876927b357114c279c82a1d5e8fa5d5e3a971c2.js

248 ms

clientlib-dependencies.min.ACSHASH3b0dd8bb3833cbd3db4f06da92b70001dcc4e6cfbe50fc5dccb39c52c9c6dc23.js

clientlib-dependencies.min.ACSHASH3b0dd8bb3833cbd3db4f06da92b70001dcc4e6cfbe50fc5dccb39c52c9c6dc23.js

229 ms

tracking.js

tracking.js

68 ms

clientlib-linklist.min.ACSHASHb06ec9b19a8fb45f12a42891b0248e3e4c83343651d5b87bef02befc6d7c7742.js

clientlib-linklist.min.ACSHASHb06ec9b19a8fb45f12a42891b0248e3e4c83343651d5b87bef02befc6d7c7742.js

240 ms

clientlib-container.min.ACSHASH9a1842ea9d4f6cfdbc00829e7c9ce8cfbe4f2446e04616e35f9c8589484c3d0b.js

clientlib-container.min.ACSHASH9a1842ea9d4f6cfdbc00829e7c9ce8cfbe4f2446e04616e35f9c8589484c3d0b.js

241 ms

clientlib-image.min.ACSHASHfa8f85160342f2830321e6aeaf845395b5b09bee1768fa2552b6c0c2114a418e.js

clientlib-image.min.ACSHASHfa8f85160342f2830321e6aeaf845395b5b09bee1768fa2552b6c0c2114a418e.js

241 ms

clientlib-header.min.ACSHASH48da59359cbda79960f2ca69e5b8f1334401d81a524c5ce78f13a5c2b0c595b3.js

clientlib-header.min.ACSHASH48da59359cbda79960f2ca69e5b8f1334401d81a524c5ce78f13a5c2b0c595b3.js

242 ms

clientlib-button.min.ACSHASH1c4934d3439450a182021963b92532ade55ddb84f0d0cd8aa87e33cd969e49b3.js

clientlib-button.min.ACSHASH1c4934d3439450a182021963b92532ade55ddb84f0d0cd8aa87e33cd969e49b3.js

242 ms

clientlib-itemlist.min.ACSHASH0202121d48a87cf5fbf46411e2ac57fa367ddcbbeadf125ff5095191f4d9c9d3.js

clientlib-itemlist.min.ACSHASH0202121d48a87cf5fbf46411e2ac57fa367ddcbbeadf125ff5095191f4d9c9d3.js

242 ms

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

243 ms

clientlib-webpart.min.ACSHASH916994145f961f024a3272ead50ec17343e8d741dd6686b3bbce5df4253bedb9.js

clientlib-webpart.min.ACSHASH916994145f961f024a3272ead50ec17343e8d741dd6686b3bbce5df4253bedb9.js

247 ms

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

245 ms

clientlib-badgecampaign.min.ACSHASHfebcf1feccc0f4825c56620e02bff394ac872dc63f3a49701d0c324dc79d85af.js

clientlib-badgecampaign.min.ACSHASHfebcf1feccc0f4825c56620e02bff394ac872dc63f3a49701d0c324dc79d85af.js

244 ms

clientlib-footer-region.min.ACSHASHfdb4e1665217d8642241b7a7d5e436447eae419365662051d63e7e93ddac4081.js

clientlib-footer-region.min.ACSHASHfdb4e1665217d8642241b7a7d5e436447eae419365662051d63e7e93ddac4081.js

245 ms

clientlib-text.min.ACSHASH6b1f1f7ad9f15801be6f5edbd56461d4f427db5ce098177d8d12166511252a43.js

clientlib-text.min.ACSHASH6b1f1f7ad9f15801be6f5edbd56461d4f427db5ce098177d8d12166511252a43.js

246 ms

unified-tracking.js

unified-tracking.js

247 ms

cq5dam.web.1400.1400.png

cq5dam.web.1400.1400.png

78 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

78 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

76 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

79 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

79 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

76 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

79 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

78 ms

ancestry-icon.woff

ancestry-icon.woff

70 ms

ancestry-icon.woff

ancestry-icon.woff

446 ms

landing

landing

62 ms

utag.js

utag.js

59 ms

false

false

186 ms

main.js

main.js

12 ms

landing

landing

32 ms

footer-db63c4d0.min.css

footer-db63c4d0.min.css

22 ms

footer-19b74378.js

footer-19b74378.js

11 ms

Accessibility Review

ancestry.app.link accessibility score

78

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

Document doesn't have a <title> element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

ancestry.app.link best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

ancestry.app.link SEO score

58

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

Document doesn't have a <title> element

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 Ancestry.app.link 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 Ancestry.app.link 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

ancestry.app.link

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