1.2 sec in total
132 ms
946 ms
103 ms
Welcome to ancestry.com homepage info - get ready to check Ancestry best content for United States right away, or after learning these important things about 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 ancestry.comWe analyzed Ancestry.com page load time and found that the first response time was 132 ms and then it took 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.
ancestry.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.1 s
25/100
25%
Value4.6 s
70/100
10%
Value7,070 ms
0/100
30%
Value0.144
77/100
15%
Value22.2 s
1/100
10%
132 ms
207 ms
17 ms
29 ms
41 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ancestry.com, 28% (18 requests) were made to Tags.tiqcdn.com and 25% (16 requests) were made to C.mfcreative.com. The less responsive or slowest element that took the longest time to load (236 ms) relates to the external source Media1.ancestry.com.
Page size can be reduced by 366.1 kB (56%)
651.3 kB
285.2 kB
In fact, the total size of Ancestry.com main page is 651.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. 50% of websites need less resources to load. Javascripts take 363.7 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.6 kB or 76% of the original size.
Potential reduce by 62 B
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 236.1 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 236.1 kB or 65% of the original size.
Potential reduce by 100.3 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.com needs all CSS files to be minified and compressed as it can save up to 100.3 kB or 78% of the original size.
Number of requests can be reduced by 42 (82%)
51
9
The browser has sent 51 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 35 to 1 for JavaScripts and as a result speed up the page load time.
ancestry.com
132 ms
www.ancestry.com
207 ms
combo.ashx
17 ms
combo.ashx
29 ms
v1.css
41 ms
combo.ashx
27 ms
callout.js
13 ms
ancestry.svg
3 ms
uslohp-dnachart2.png
3 ms
standard
12 ms
pbs-logo-white.png
22 ms
standard
7 ms
uslohp-herobkg-kyle.jpg
3 ms
utag.js
43 ms
source-sans-pro.woff
14 ms
source-sans-pro-light.woff
15 ms
source-sans-pro-semi-bold.woff
15 ms
source-sans-pro-bold.woff
15 ms
utag.24.js
20 ms
utag.652.js
4 ms
utag.49.js
8 ms
utag.311.js
8 ms
utag.363.js
8 ms
utag.444.js
6 ms
utag.456.js
18 ms
utag.489.js
21 ms
utag.544.js
18 ms
utag.573.js
18 ms
utag.596.js
20 ms
utag.598.js
21 ms
utag.611.js
38 ms
utag.642.js
39 ms
utag.673.js
39 ms
utag.696.js
40 ms
utag.705.js
39 ms
combo.ashx
17 ms
conversion_async.js
32 ms
dc.js
33 ms
ipixel
236 ms
js
157 ms
js
143 ms
151 ms
rd
213 ms
js
135 ms
154 ms
pixel
151 ms
fbevents.js
202 ms
__utm.gif
125 ms
__utm.gif
36 ms
ancestry-icon.woff
17 ms
source-sans-pro-italic.woff
17 ms
source-sans-pro-light-italic.woff
16 ms
41 ms
i.js
53 ms
38 ms
ga-audiences
77 ms
27 ms
26 ms
99 ms
js
83 ms
js
22 ms
js
24 ms
img
90 ms
r2
5 ms
ancestry.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
ancestry.com 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.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
ancestry.com
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: