1.3 sec in total
248 ms
852 ms
199 ms
Visit person.ancestry.com now to see the best up-to-date Person Ancestry content for United States and also check out these interesting facts you probably never knew about person.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 person.ancestry.comWe analyzed Person.ancestry.com page load time and found that the first response time was 248 ms and then it took 1.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.
person.ancestry.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value4.4 s
40/100
25%
Value3.4 s
89/100
10%
Value3,370 ms
2/100
30%
Value0.027
100/100
15%
Value15.4 s
7/100
10%
248 ms
33 ms
66 ms
81 ms
64 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Person.ancestry.com, 90% (45 requests) were made to C.mfcreative.com and 2% (1 request) were made to Yui.yahooapis.com. The less responsive or slowest element that took the longest time to load (248 ms) belongs to the original domain Person.ancestry.com.
Page size can be reduced by 256.0 kB (74%)
348.2 kB
92.2 kB
In fact, the total size of Person.ancestry.com main page is 348.2 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 194.9 kB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 3.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.1 kB or 76% of the original size.
Potential reduce by 141.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 141.7 kB or 73% of the original size.
Potential reduce by 92.2 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. Person.ancestry.com needs all CSS files to be minified and compressed as it can save up to 92.2 kB or 74% of the original size.
Number of requests can be reduced by 37 (84%)
44
7
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Person 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 22 to 1 for CSS and as a result speed up the page load time.
person.ancestry.com
248 ms
combo
33 ms
jquery-1.7.1.min.js
66 ms
jquery-ui-1.8.18.custom.min.js
81 ms
resourcemanager.js
64 ms
ajaxmanager.js
62 ms
ancestry.jsx
62 ms
utility.js
62 ms
header.js
172 ms
header.css
170 ms
main.css
206 ms
activity-indicator.css
185 ms
alert.css
184 ms
autocomplete.css
208 ms
button.css
184 ms
callout.css
206 ms
card.css
201 ms
carousel.css
186 ms
container.css
184 ms
form.css
188 ms
grid.css
172 ms
icon.css
182 ms
modal.css
182 ms
paging.css
186 ms
photo.css
182 ms
progress.css
205 ms
tab.css
207 ms
table.css
189 ms
template.css
190 ms
alert.js
203 ms
autocomplete.js
213 ms
callout.js
205 ms
carousel.js
202 ms
form.js
217 ms
modal.js
209 ms
paging.js
211 ms
tab.js
209 ms
header.js
208 ms
v1.css
180 ms
ancestry-on-dark.svg
7 ms
progen.svg
51 ms
source-sans-pro.woff
55 ms
source-sans-pro-light.woff
52 ms
source-sans-pro-semi-bold.woff
51 ms
source-sans-pro-bold.woff
53 ms
ancestry-icon.woff
39 ms
activityi;src=1357971;type=start526;cat=ances638;ord=6869946400109
50 ms
99
223 ms
beacon
124 ms
combo.ashx
50 ms
person.ancestry.com accessibility score
person.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
Page has valid source maps
person.ancestry.com SEO score
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 Person.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 Person.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.
person.ancestry.com
Open Graph description is not detected on the main page of Person 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: