1.1 sec in total
131 ms
868 ms
115 ms
Click here to check amazing Records Ancestry content for United States. Otherwise, check out these important facts you probably never knew about records.ancestry.com
Discover your family history by searching your ancestor's name on Ancestry®, the leading online resource for genealogy research. Start your person search here.
Visit records.ancestry.comWe analyzed Records.ancestry.com page load time and found that the first response time was 131 ms and then it took 983 ms 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.
records.ancestry.com performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value2.8 s
82/100
25%
Value2.7 s
96/100
10%
Value3,410 ms
2/100
30%
Value0.074
95/100
15%
Value20.7 s
2/100
10%
131 ms
195 ms
8 ms
22 ms
33 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Records.ancestry.com, 32% (18 requests) were made to C.mfcreative.com and 23% (13 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (195 ms) relates to the external source Ancestry.com.
Page size can be reduced by 449.2 kB (51%)
880.4 kB
431.2 kB
In fact, the total size of Records.ancestry.com main page is 880.4 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 466.3 kB which makes up the majority of the site volume.
Potential reduce by 29.7 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 4.7 kB, which is 12% 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 29.7 kB or 76% of the original size.
Potential reduce by 32.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. Obviously, Records Ancestry needs image optimization as it can save up to 32.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 312.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 312.0 kB or 67% of the original size.
Potential reduce by 74.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. Records.ancestry.com needs all CSS files to be minified and compressed as it can save up to 74.7 kB or 78% of the original size.
Number of requests can be reduced by 36 (78%)
46
10
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Records 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 29 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
records.ancestry.com
131 ms
195 ms
jquery-1.7.1.min.js
8 ms
combo.ashx
22 ms
combo.ashx
33 ms
recordsTop.css
30 ms
header.js
36 ms
header.css
40 ms
v1.css
39 ms
ancestry-on-dark.svg
5 ms
progen.svg
7 ms
standard
11 ms
1940-record@1x.png
98 ms
utag.js
57 ms
records@1x.png
34 ms
hint-graphics@1x.png
37 ms
DNA-graphic@1x.png
33 ms
source-sans-pro.woff
33 ms
source-sans-pro-light.woff
35 ms
source-sans-pro-semi-bold.woff
35 ms
source-sans-pro-bold.woff
33 ms
ancestry-icon.woff
34 ms
utag.24.js
19 ms
utag.652.js
4 ms
utag.311.js
7 ms
utag.363.js
8 ms
utag.444.js
8 ms
utag.456.js
162 ms
utag.573.js
16 ms
utag.598.js
17 ms
utag.611.js
18 ms
utag.642.js
17 ms
utag.673.js
36 ms
utag.696.js
36 ms
combo.ashx
14 ms
js
34 ms
ipixel
32 ms
conversion_async.js
30 ms
js
25 ms
rd
193 ms
ga.js
47 ms
js
26 ms
fbevents.js
189 ms
118 ms
i.js
118 ms
157 ms
__utm.gif
101 ms
67 ms
collect
61 ms
24 ms
25 ms
30 ms
js
24 ms
js
29 ms
js
30 ms
img
24 ms
r2
3 ms
records.ancestry.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
records.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
records.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
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Records.ancestry.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Records.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.
records.ancestry.com
Open Graph description is not detected on the main page of Records 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: