1.8 sec in total
216 ms
1.4 sec
213 ms
Click here to check amazing Ancestry content for Italy. Otherwise, check out these important facts you probably never knew about ancestry.it
Scopri i tuoi antenati nel sito Web più grande del mondo dedicato alla storia familiare. Inizia un albero genealogico, consulta il censimento e altro materiale online su Ancestry.it
Visit ancestry.itWe analyzed Ancestry.it page load time and found that the first response time was 216 ms and then it took 1.6 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.
ancestry.it performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value7.5 s
4/100
25%
Value5.2 s
60/100
10%
Value1,710 ms
11/100
30%
Value0
100/100
15%
Value9.0 s
34/100
10%
216 ms
313 ms
12 ms
19 ms
9 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ancestry.it, 42% (22 requests) were made to C.mfcreative.com and 23% (12 requests) were made to Canary.mfcreative.com. The less responsive or slowest element that took the longest time to load (436 ms) relates to the external source Banner.ajax.ancestry.it.
Page size can be reduced by 328.0 kB (56%)
581.8 kB
253.8 kB
In fact, the total size of Ancestry.it main page is 581.8 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. 55% of websites need less resources to load. Javascripts take 212.7 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.6 kB or 75% 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 133.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 133.7 kB or 63% of the original size.
Potential reduce by 146.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. Ancestry.it needs all CSS files to be minified and compressed as it can save up to 146.0 kB or 78% of the original size.
Number of requests can be reduced by 22 (61%)
36
14
The browser has sent 36 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 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ancestry.it
216 ms
www.ancestry.it
313 ms
combo.ashx
12 ms
combo.ashx
19 ms
header.js
9 ms
header.css
17 ms
v1.css
50 ms
combo.ashx
55 ms
alert.js
55 ms
alert.js
51 ms
combo.ashx
51 ms
callout.js
52 ms
ancestry-on-dark.svg
12 ms
progen.svg
9 ms
ancestry.svg
9 ms
standard
12 ms
21
436 ms
us-lohp-kid-car-1600.jpg
37 ms
standard
15 ms
source-sans-pro.woff
5 ms
source-sans-pro.woff
25 ms
source-sans-pro-light.woff
5 ms
source-sans-pro-light.woff
11 ms
source-sans-pro-semi-bold.woff
24 ms
source-sans-pro-semi-bold.woff
11 ms
source-sans-pro-bold.woff
10 ms
source-sans-pro-bold.woff
11 ms
utag.js
139 ms
ga.js
32 ms
21
296 ms
__utm.gif
16 ms
combo.ashx
6 ms
combo.ashx
281 ms
ancestry-icon.woff
11 ms
ancestry-icon.woff
10 ms
utag.24.js
30 ms
utag.91.js
56 ms
utag.92.js
60 ms
utag.94.js
59 ms
rd
147 ms
__utm.gif
48 ms
combo.ashx
9 ms
collect
56 ms
combo.ashx
7 ms
combo.ashx
17 ms
r2
135 ms
geo-header.jpg
115 ms
__utm.gif
72 ms
source-sans-pro-italic.woff
4 ms
source-sans-pro-italic.woff
10 ms
source-sans-pro-light-italic.woff
8 ms
source-sans-pro-light-italic.woff
20 ms
r
4 ms
ancestry.it 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.it 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.it 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
IT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ancestry.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it does not match the claimed English language. Our system also found out that Ancestry.it 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.it
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: