Tools & Wizards About Us
ancestry.ie screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ancestry.ie

AncestryDNA® | DNA Tests for Ethnicity & Genealogy DNA Test

Page Load Speed

1.7 sec in total

First Response

103 ms

Resources Loaded

1.3 sec

Page Rendered

251 ms

ancestry.ie screenshot

About Website

Welcome to ancestry.ie homepage info - get ready to check Ancestry best content for United States right away, or after learning these important things about ancestry.ie

Discover your family history and build a family tree with the world’s largest genealogy website. Search birth records, census data, obituaries and more!

Visit ancestry.ie

Key Findings

We analyzed Ancestry.ie page load time and found that the first response time was 103 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 35% of websites can load faster.

Performance Metrics

ancestry.ie performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value1,070 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

ancestry.ie

103 ms

www.ancestry.co.uk

86 ms

gtm.js

116 ms

p13n.min.js

87 ms

clientlib-site-split.min.ACSHASH1a12d205f41c57e8ff245e5724221babae0b68d199938a0edd9b98c39bf953b3.css

45 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ancestry.ie, 61% (27 requests) were made to Cmsasset.ancestrycdn.com and 27% (12 requests) were made to Ancestrycdn.com. The less responsive or slowest element that took the longest time to load (544 ms) relates to the external source Ancestrycdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 785.7 kB (75%)

Content Size

1.0 MB

After Optimization

261.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ancestry.ie main page is 1.0 MB. 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 445.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 340.2 kB

  • Original 386.9 kB
  • After minification 351.4 kB
  • After compression 46.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 340.2 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 44.3 kB
  • After minification 44.3 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.

JavaScript Optimization

-68%

Potential reduce by 303.3 kB

  • Original 445.2 kB
  • After minification 445.2 kB
  • After compression 142.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 303.3 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 142.2 kB

  • Original 170.3 kB
  • After minification 170.2 kB
  • After compression 28.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.ie needs all CSS files to be minified and compressed as it can save up to 142.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (88%)

Requests Now

40

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 40 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 36 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

ancestry.ie

ancestry.ie

103 ms

www.ancestry.co.uk

www.ancestry.co.uk

86 ms

gtm.js

gtm.js

116 ms

p13n.min.js

p13n.min.js

87 ms

clientlib-site-split.min.ACSHASH1a12d205f41c57e8ff245e5724221babae0b68d199938a0edd9b98c39bf953b3.css

clientlib-site-split.min.ACSHASH1a12d205f41c57e8ff245e5724221babae0b68d199938a0edd9b98c39bf953b3.css

45 ms

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

65 ms

at.js

at.js

110 ms

core.css

core.css

148 ms

clientlib-marketing.min.ACSHASH713f7ce5d51e5b2645f01f80cbd08063e9295ae0bf08b56f20bbb03eb2a4251a.css

clientlib-marketing.min.ACSHASH713f7ce5d51e5b2645f01f80cbd08063e9295ae0bf08b56f20bbb03eb2a4251a.css

44 ms

clientlib-marketing.min.ACSHASH76c65e5cdfbf22c31928f28a1a938bc812ff3e81f08f23c68148893fdb6b0ba0.js

clientlib-marketing.min.ACSHASH76c65e5cdfbf22c31928f28a1a938bc812ff3e81f08f23c68148893fdb6b0ba0.js

63 ms

geo-redirector.min.js

geo-redirector.min.js

103 ms

banners-injection.min.js

banners-injection.min.js

544 ms

ajax-manager.js

ajax-manager.js

144 ms

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

59 ms

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

59 ms

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

71 ms

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

80 ms

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

75 ms

clientlib-global.min.ACSHASHbb0e119237e23fd17808b06e100b917390ea0ae444c4cdc2b8f11e481496d177.js

clientlib-global.min.ACSHASHbb0e119237e23fd17808b06e100b917390ea0ae444c4cdc2b8f11e481496d177.js

78 ms

core.js

core.js

142 ms

switch.js

switch.js

141 ms

carousel.js

carousel.js

540 ms

clientlib-site-split.min.ACSHASHdd52dc0160fc19446fa93cb49ce26c9a904fa7dd092bc8902bf923f181151873.js

clientlib-site-split.min.ACSHASHdd52dc0160fc19446fa93cb49ce26c9a904fa7dd092bc8902bf923f181151873.js

77 ms

clientlib-dependencies.min.ACSHASHfee650633c89138c52d99e351321badfc25c5ad395bbae5c7d5aa68a3a2678a4.js

clientlib-dependencies.min.ACSHASHfee650633c89138c52d99e351321badfc25c5ad395bbae5c7d5aa68a3a2678a4.js

73 ms

tracking.js

tracking.js

539 ms

moment.min.ACSHASH8dbac393b462220216deb2cd3504d2007049cf9a595f24cfaa6ae8bc55262ff7.js

moment.min.ACSHASH8dbac393b462220216deb2cd3504d2007049cf9a595f24cfaa6ae8bc55262ff7.js

73 ms

clientlib-button.min.ACSHASH3eebdcc7669c4e32946a1f6f56e002c00bb9f1ec34a0d95ad54d329bca64ef67.js

clientlib-button.min.ACSHASH3eebdcc7669c4e32946a1f6f56e002c00bb9f1ec34a0d95ad54d329bca64ef67.js

81 ms

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

74 ms

clientlib-itemlist.min.ACSHASH889ef3693ba05f6d728b700d9365fca8c0d6b871addfbce3b27327e51229324d.js

clientlib-itemlist.min.ACSHASH889ef3693ba05f6d728b700d9365fca8c0d6b871addfbce3b27327e51229324d.js

83 ms

clientlib-badgecampaign.min.ACSHASH39fb25541246c78759274f98947436afa5a80265df9fd72e84353aafca739858.js

clientlib-badgecampaign.min.ACSHASH39fb25541246c78759274f98947436afa5a80265df9fd72e84353aafca739858.js

75 ms

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

78 ms

clientlib-header.min.ACSHASH5ff65449782872a7724051b3a4c3ca7598d91c754cc9d3748766d6dff76ccb3c.js

clientlib-header.min.ACSHASH5ff65449782872a7724051b3a4c3ca7598d91c754cc9d3748766d6dff76ccb3c.js

80 ms

clientlib-image.min.ACSHASH6f4bf01d88440e322c70b41ce73a18e4999be37cba66444203b1b026268a65bf.js

clientlib-image.min.ACSHASH6f4bf01d88440e322c70b41ce73a18e4999be37cba66444203b1b026268a65bf.js

79 ms

clientlib-text.min.ACSHASHa69496104ffdeec1d3627496f57e874033104fb420a23e9748e77306e558b85d.js

clientlib-text.min.ACSHASHa69496104ffdeec1d3627496f57e874033104fb420a23e9748e77306e558b85d.js

77 ms

clientlib-linklist.min.ACSHASHe2e2b6afca8812b04ed72036abb7022c61bf83d435a0f8fee27112f75699019c.js

clientlib-linklist.min.ACSHASHe2e2b6afca8812b04ed72036abb7022c61bf83d435a0f8fee27112f75699019c.js

78 ms

clientlib-teaser.min.ACSHASHb06ec9b19a8fb45f12a42891b0248e3e4c83343651d5b87bef02befc6d7c7742.js

clientlib-teaser.min.ACSHASHb06ec9b19a8fb45f12a42891b0248e3e4c83343651d5b87bef02befc6d7c7742.js

80 ms

clientlib-footer-region.min.ACSHASH8914ad024c5a77cc0b6189e27a03e0e8be2cdebc4d3b409d02678144bd6cccd1.js

clientlib-footer-region.min.ACSHASH8914ad024c5a77cc0b6189e27a03e0e8be2cdebc4d3b409d02678144bd6cccd1.js

81 ms

clientlib-container.min.ACSHASH533cf7122921bd3a4284ea270a75c1c5a86f4a912be8c61a59350b800ef3f190.js

clientlib-container.min.ACSHASH533cf7122921bd3a4284ea270a75c1c5a86f4a912be8c61a59350b800ef3f190.js

82 ms

unified-tracking.js

unified-tracking.js

537 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

481 ms

ancestry-icon.woff

ancestry-icon.woff

55 ms

ancestry-icon.woff

ancestry-icon.woff

222 ms

false

false

234 ms

main.js

main.js

7 ms

Accessibility Review

ancestry.ie accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

ancestry.ie best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ancestry.ie SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ancestry.ie 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.ie 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.

Social Sharing Optimization

ancestry.ie

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: