2.6 sec in total
128 ms
2.2 sec
270 ms
Welcome to ancestry.fr homepage info - get ready to check Ancestry best content for France right away, or after learning these important things about 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 ancestry.frWe analyzed Ancestry.fr page load time and found that the first response time was 128 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
ancestry.fr performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.7 s
8/100
25%
Value5.6 s
52/100
10%
Value2,690 ms
4/100
30%
Value0
100/100
15%
Value10.0 s
27/100
10%
128 ms
1379 ms
19 ms
30 ms
29 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Ancestry.fr, 54% (19 requests) were made to C.mfcreative.com and 14% (5 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ancestry.fr.
Page size can be reduced by 272.7 kB (58%)
474.0 kB
201.3 kB
In fact, the total size of Ancestry.fr main page is 474.0 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. 45% of websites need less resources to load. Javascripts take 195.1 kB which makes up the majority of the site volume.
Potential reduce by 32.4 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 32.4 kB or 74% of the original size.
Potential reduce by 9.8 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 images are well optimized though.
Potential reduce by 121.9 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 121.9 kB or 62% of the original size.
Potential reduce by 108.7 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.fr needs all CSS files to be minified and compressed as it can save up to 108.7 kB or 78% of the original size.
Number of requests can be reduced by 18 (67%)
27
9
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ancestry.fr
128 ms
www.ancestry.fr
1379 ms
combo.ashx
19 ms
combo.ashx
30 ms
header.js
29 ms
header.css
61 ms
v1.css
58 ms
ancestry-on-dark.svg
15 ms
alert.js
8 ms
combo.ashx
14 ms
callout.js
12 ms
progen.svg
8 ms
ancestry.svg
14 ms
standard
172 ms
source-sans-pro.woff
20 ms
source-sans-pro-light.woff
21 ms
source-sans-pro-semi-bold.woff
21 ms
source-sans-pro-bold.woff
47 ms
ancestry-icon.woff
19 ms
us-lohp-kid-car-1600.jpg
29 ms
standard
9 ms
utag.js
150 ms
ga.js
29 ms
21
181 ms
__utm.gif
11 ms
combo.ashx
8 ms
combo.ashx
263 ms
utag.24.js
82 ms
utag.96.js
6 ms
utag.97.js
4 ms
utag.99.js
80 ms
__utm.gif
64 ms
rd
154 ms
collect
73 ms
combo.ashx
40 ms
ancestry.fr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ancestry.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ancestry.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ancestry.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that 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.
ancestry.fr
Open Graph description is not detected on the main page of 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: