1.4 sec in total
128 ms
1.1 sec
155 ms
Welcome to ancestry.ca homepage info - get ready to check Ancestry best content for Canada right away, or after learning these important things about ancestry.ca
Discover your family history and start your family tree. Try free and access billions of genealogy records including Census, SSDI & Military records.
Visit ancestry.caWe analyzed Ancestry.ca page load time and found that the first response time was 128 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
ancestry.ca performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value5.9 s
14/100
25%
Value6.7 s
36/100
10%
Value8,190 ms
0/100
30%
Value0
100/100
15%
Value20.0 s
2/100
10%
128 ms
213 ms
23 ms
37 ms
36 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ancestry.ca, 21% (16 requests) were made to C.mfcreative.com and 17% (13 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (277 ms) relates to the external source C.mfcreative.com.
Page size can be reduced by 447.0 kB (54%)
830.7 kB
383.7 kB
In fact, the total size of Ancestry.ca main page is 830.7 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 357.3 kB which makes up the majority of the site volume.
Potential reduce by 29.2 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.2 kB or 73% of the original size.
Potential reduce by 26 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 247.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 247.0 kB or 69% of the original size.
Potential reduce by 170.8 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.ca needs all CSS files to be minified and compressed as it can save up to 170.8 kB or 79% of the original size.
Number of requests can be reduced by 40 (75%)
53
13
The browser has sent 53 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 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ancestry.ca
128 ms
www.ancestry.ca
213 ms
combo.ashx
23 ms
combo.ashx
37 ms
v1.css
36 ms
combo.ashx
35 ms
ancestry.svg
9 ms
us-lohp-gc-dnachart.png
12 ms
standard
10 ms
us-lohp-gc-herobkg.jpg
11 ms
combo.ashx
277 ms
standard
10 ms
source-sans-pro.woff
5 ms
source-sans-pro-light.woff
2 ms
source-sans-pro-semi-bold.woff
5 ms
source-sans-pro-bold.woff
5 ms
utag.js
58 ms
ga.js
8 ms
__utm.gif
13 ms
collect
82 ms
utag.24.js
40 ms
utag.118.js
66 ms
utag.125.js
79 ms
utag.138.js
79 ms
utag.148.js
79 ms
utag.155.js
78 ms
utag.170.js
78 ms
utag.194.js
91 ms
utag.198.js
109 ms
utag.199.js
110 ms
utag.200.js
114 ms
utag.223.js
112 ms
ga-audiences
52 ms
event.php
125 ms
activityi;src=3463709;type=ances197;cat=ances536;ord=898700084071.6064
100 ms
activityi;src=3463709;type=ances197;cat=ances821;ord=5313447744119.912
98 ms
activityi;src=3463709;type=ances197;cat=ances821;ord=5529611778911.203
94 ms
conversion_async.js
17 ms
rd
166 ms
103 ms
__utm.gif
64 ms
fbds.js
39 ms
fbevents.js
38 ms
collect
25 ms
generic
23 ms
50 ms
121 ms
143 ms
ancestry-icon.woff
9 ms
19 ms
combo.ashx
18 ms
combo.ashx
24 ms
pixel
19 ms
r2
4 ms
134 ms
geo-header.jpg
93 ms
event.php
63 ms
activityi;src=3463709;type=ances197;cat=ances821;ord=1424564775079.4888
67 ms
62 ms
activityi;src=3463709;type=ances197;cat=ances821;ord=8524067839607.597
63 ms
activityi;src=3463709;type=ances197;cat=ances536;ord=81080922391.26562
61 ms
59 ms
__utm.gif
57 ms
31 ms
23 ms
source-sans-pro.woff
19 ms
source-sans-pro-light.woff
9 ms
source-sans-pro-semi-bold.woff
5 ms
source-sans-pro-bold.woff
8 ms
ancestry-icon.woff
8 ms
source-sans-pro-italic.woff
8 ms
source-sans-pro-italic.woff
8 ms
source-sans-pro-light-italic.woff
17 ms
source-sans-pro-light-italic.woff
7 ms
r
6 ms
16 ms
tap.php
6 ms
ancestry.ca 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
Buttons do not have an accessible name
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
Heading elements are not in a sequentially-descending order
ancestry.ca 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ancestry.ca 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ancestry.ca 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.ca 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.ca
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: