Tools & Wizards About Us
home.ancestry.fr screenshot

Report Summary

  • 44

    Performance

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

  • 93

    SEO

    Google-friendlier than
    83% of websites

home.ancestry.fr

Ancestry® | Généalogie, arbres généalogiques et documents d’histoire familiale

Page Load Speed

1.6 sec in total

First Response

288 ms

Resources Loaded

1.1 sec

Page Rendered

166 ms

home.ancestry.fr screenshot

About Website

Welcome to home.ancestry.fr homepage info - get ready to check Home Ancestry best content for France right away, or after learning these important things about home.ancestry.fr

Découvrez vos ancêtres à l’aide du plus grand site généalogique au monde. Commencez un arbre généalogique, explorez les recensements et bien plus en ligne sur le site d’Ancestry

Visit home.ancestry.fr

Key Findings

We analyzed Home.ancestry.fr page load time and found that the first response time was 288 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

home.ancestry.fr performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

www.ancestry.fr

288 ms

gtm.js

156 ms

p13n.min.js

47 ms

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

52 ms

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

77 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 557.7 kB (60%)

Content Size

937.3 kB

After Optimization

379.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Home.ancestry.fr main page is 937.3 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. 70% of websites need less resources to load. Javascripts take 463.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 104.5 kB

  • Original 140.6 kB
  • After minification 138.0 kB
  • After compression 36.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 104.5 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 159.4 kB
  • After minification 159.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. Home Ancestry images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 308.2 kB

  • Original 463.1 kB
  • After minification 463.1 kB
  • After compression 155.0 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 308.2 kB or 67% 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. Home.ancestry.fr 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 37 (93%)

Requests Now

40

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Home 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 35 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.fr

www.ancestry.fr

288 ms

gtm.js

gtm.js

156 ms

p13n.min.js

p13n.min.js

47 ms

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

clientlib-site-split.min.ACSHASH9d0a8db51cae58bcf39bd57e2d38f798b4662b13b5a13ed873670031777b9650.css

52 ms

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

77 ms

at.js

at.js

74 ms

core.css

core.css

94 ms

clientlib-marketing.min.ACSHASH54477308e0049c25a255a67e18d0e9b8810435f0b2de13dfd5ac4861c11f2ac7.css

clientlib-marketing.min.ACSHASH54477308e0049c25a255a67e18d0e9b8810435f0b2de13dfd5ac4861c11f2ac7.css

74 ms

clientlib-marketing.min.ACSHASHb7cf03adbdd01d757f6a281ae2314f545c8940dd44ccbf44aca25477ba234579.js

clientlib-marketing.min.ACSHASHb7cf03adbdd01d757f6a281ae2314f545c8940dd44ccbf44aca25477ba234579.js

75 ms

geo-redirector.min.js

geo-redirector.min.js

72 ms

banners-injection.min.js

banners-injection.min.js

71 ms

ajax-manager.js

ajax-manager.js

73 ms

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

130 ms

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

90 ms

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

140 ms

clientlib-global.min.ACSHASH9f7e65e6ad1f9a8a331807b813457463824e0cc38a08031bd0bf8f1e374681b9.js

clientlib-global.min.ACSHASH9f7e65e6ad1f9a8a331807b813457463824e0cc38a08031bd0bf8f1e374681b9.js

139 ms

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

152 ms

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

155 ms

core.js

core.js

141 ms

switch.js

switch.js

141 ms

carousel.js

carousel.js

140 ms

clientlib-site-split.min.ACSHASHcb51b8a4edd967da941de5d4eeb68cf4338ee6225631e32a8c61bc3cac897b51.js

clientlib-site-split.min.ACSHASHcb51b8a4edd967da941de5d4eeb68cf4338ee6225631e32a8c61bc3cac897b51.js

147 ms

clientlib-dependencies.min.ACSHASH327e7e87486b772ffe78af718dedbdf12a90eccfb9bc41c5a6b62d9adf8c2d7a.js

clientlib-dependencies.min.ACSHASH327e7e87486b772ffe78af718dedbdf12a90eccfb9bc41c5a6b62d9adf8c2d7a.js

141 ms

tracking.js

tracking.js

140 ms

moment.min.ACSHASH8dbac393b462220216deb2cd3504d2007049cf9a595f24cfaa6ae8bc55262ff7.js

moment.min.ACSHASH8dbac393b462220216deb2cd3504d2007049cf9a595f24cfaa6ae8bc55262ff7.js

143 ms

clientlib-footer-region.min.ACSHASHfdb4e1665217d8642241b7a7d5e436447eae419365662051d63e7e93ddac4081.js

clientlib-footer-region.min.ACSHASHfdb4e1665217d8642241b7a7d5e436447eae419365662051d63e7e93ddac4081.js

141 ms

clientlib-image.min.ACSHASHfa8f85160342f2830321e6aeaf845395b5b09bee1768fa2552b6c0c2114a418e.js

clientlib-image.min.ACSHASHfa8f85160342f2830321e6aeaf845395b5b09bee1768fa2552b6c0c2114a418e.js

144 ms

clientlib-button.min.ACSHASH4a3a91773f9d5546608a24766ba4870f7c3b774d3155cd07d73ff1b0508a9b86.js

clientlib-button.min.ACSHASH4a3a91773f9d5546608a24766ba4870f7c3b774d3155cd07d73ff1b0508a9b86.js

147 ms

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

150 ms

clientlib-container.min.ACSHASH9a1842ea9d4f6cfdbc00829e7c9ce8cfbe4f2446e04616e35f9c8589484c3d0b.js

clientlib-container.min.ACSHASH9a1842ea9d4f6cfdbc00829e7c9ce8cfbe4f2446e04616e35f9c8589484c3d0b.js

151 ms

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

147 ms

clientlib-header.min.ACSHASH48da59359cbda79960f2ca69e5b8f1334401d81a524c5ce78f13a5c2b0c595b3.js

clientlib-header.min.ACSHASH48da59359cbda79960f2ca69e5b8f1334401d81a524c5ce78f13a5c2b0c595b3.js

147 ms

clientlib-text.min.ACSHASH6b1f1f7ad9f15801be6f5edbd56461d4f427db5ce098177d8d12166511252a43.js

clientlib-text.min.ACSHASH6b1f1f7ad9f15801be6f5edbd56461d4f427db5ce098177d8d12166511252a43.js

147 ms

unified-tracking.js

unified-tracking.js

142 ms

cq5dam.web.1280.1280.jpeg

cq5dam.web.1280.1280.jpeg

152 ms

false

false

270 ms

utag.js

utag.js

39 ms

ancestry-icon.woff

ancestry-icon.woff

19 ms

ancestry-icon.woff

ancestry-icon.woff

379 ms

main.js

main.js

14 ms

utag.v.js

utag.v.js

3 ms

footer-db63c4d0.min.css

footer-db63c4d0.min.css

7 ms

footer-8615446f.js

footer-8615446f.js

5 ms

Accessibility Review

home.ancestry.fr 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

home.ancestry.fr 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

home.ancestry.fr SEO score

93

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

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Home.ancestry.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Home.ancestry.fr 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

home.ancestry.fr

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