Tools & Wizards About Us
shops.ancestry.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

shops.ancestry.com

Ancestry® | Family Tree, Genealogy & Family History Records

Page Load Speed

1.6 sec in total

First Response

308 ms

Resources Loaded

976 ms

Page Rendered

359 ms

shops.ancestry.com screenshot

About Website

Visit shops.ancestry.com now to see the best up-to-date Shops Ancestry content for United States and also check out these interesting facts you probably never knew about shops.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 shops.ancestry.com

Key Findings

We analyzed Shops.ancestry.com page load time and found that the first response time was 308 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

shops.ancestry.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

shops.ancestry.com

308 ms

www.ancestry.com

55 ms

gtm.js

251 ms

p13n.min.js

40 ms

clientlib-site-split.min.ACSHASH8c434c8d6f4878805000404d9a9c786f921592fb5d2d423d27754c3f406d3217.css

48 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Shops.ancestry.com, 65% (35 requests) were made to Cmsasset.ancestrycdn.com and 26% (14 requests) were made to Ancestrycdn.com. The less responsive or slowest element that took the longest time to load (308 ms) belongs to the original domain Shops.ancestry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 663.3 kB (47%)

Content Size

1.4 MB

After Optimization

736.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shops.ancestry.com main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 521.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 214.4 kB

  • Original 257.6 kB
  • After minification 242.3 kB
  • After compression 43.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 214.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 962 B

  • Original 521.7 kB
  • After minification 520.7 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. Shops Ancestry images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 305.6 kB

  • Original 449.1 kB
  • After minification 449.1 kB
  • After compression 143.4 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 305.6 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 142.3 kB

  • Original 171.6 kB
  • After minification 171.6 kB
  • After compression 29.4 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. Shops.ancestry.com needs all CSS files to be minified and compressed as it can save up to 142.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (78%)

Requests Now

50

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shops 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 37 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

shops.ancestry.com

shops.ancestry.com

308 ms

www.ancestry.com

www.ancestry.com

55 ms

gtm.js

gtm.js

251 ms

p13n.min.js

p13n.min.js

40 ms

clientlib-site-split.min.ACSHASH8c434c8d6f4878805000404d9a9c786f921592fb5d2d423d27754c3f406d3217.css

clientlib-site-split.min.ACSHASH8c434c8d6f4878805000404d9a9c786f921592fb5d2d423d27754c3f406d3217.css

48 ms

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

clientlib-js-base.min.ACSHASH3ae3cdaab3628d70e124b8b46988e5e281ac6a7fb98c5f53914c076b323df291.js

64 ms

at.js

at.js

36 ms

core.css

core.css

36 ms

clientlib-marketing.min.ACSHASH713f7ce5d51e5b2645f01f80cbd08063e9295ae0bf08b56f20bbb03eb2a4251a.css

clientlib-marketing.min.ACSHASH713f7ce5d51e5b2645f01f80cbd08063e9295ae0bf08b56f20bbb03eb2a4251a.css

64 ms

clientlib-marketing.min.ACSHASH76c65e5cdfbf22c31928f28a1a938bc812ff3e81f08f23c68148893fdb6b0ba0.js

clientlib-marketing.min.ACSHASH76c65e5cdfbf22c31928f28a1a938bc812ff3e81f08f23c68148893fdb6b0ba0.js

84 ms

geo-redirector.min.js

geo-redirector.min.js

32 ms

banners-injection.min.js

banners-injection.min.js

32 ms

ajax-manager.js

ajax-manager.js

30 ms

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

utils.min.ACSHASH5536b5afb6906533e4496762711f68f65e47e47643ebb6b5e26155b2e74423d6.js

207 ms

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

shared.min.ACSHASH6312dca37f1bcec119ada11995eee758ecda536a5f85c14bf0e0f73e3445defd.js

207 ms

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

jquery.min.ACSHASH83d7d4ef45e68b3932f4727c0195c8ff7367aa66bb18c750c9f262c5b7807491.js

210 ms

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

granite.min.ACSHASHfa83c7ff4a41134cd4b0295b7a1744ae46a77f46caa517db20995e4420280fa8.js

209 ms

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

jquery.min.ACSHASHd0978c376fd25efab1265255e67c4f305e7c232a4622df2c6a683ed3df30d237.js

221 ms

clientlib-global.min.ACSHASHcd5e5905f01ca3abee89f380bbe9693afb288ef0137d33830d6c7eb0da2a0601.js

clientlib-global.min.ACSHASHcd5e5905f01ca3abee89f380bbe9693afb288ef0137d33830d6c7eb0da2a0601.js

221 ms

core.js

core.js

33 ms

switch.js

switch.js

32 ms

carousel.js

carousel.js

35 ms

clientlib-dependencies.min.ACSHASHfee650633c89138c52d99e351321badfc25c5ad395bbae5c7d5aa68a3a2678a4.js

clientlib-dependencies.min.ACSHASHfee650633c89138c52d99e351321badfc25c5ad395bbae5c7d5aa68a3a2678a4.js

209 ms

clientlib-site-split.min.ACSHASH7af25764d2a69277d045e26adc92fa4a77709b0e49cf585cd7080e57a18fecff.js

clientlib-site-split.min.ACSHASH7af25764d2a69277d045e26adc92fa4a77709b0e49cf585cd7080e57a18fecff.js

228 ms

tracking.js

tracking.js

34 ms

moment.min.ACSHASHb693aec0aca5989d5cfa1d54def11df855fe603dadcab5295a53ded3fc5f7a3b.js

moment.min.ACSHASHb693aec0aca5989d5cfa1d54def11df855fe603dadcab5295a53ded3fc5f7a3b.js

219 ms

clientlib-header.min.ACSHASH5ff65449782872a7724051b3a4c3ca7598d91c754cc9d3748766d6dff76ccb3c.js

clientlib-header.min.ACSHASH5ff65449782872a7724051b3a4c3ca7598d91c754cc9d3748766d6dff76ccb3c.js

229 ms

clientlib-text.min.ACSHASHa69496104ffdeec1d3627496f57e874033104fb420a23e9748e77306e558b85d.js

clientlib-text.min.ACSHASHa69496104ffdeec1d3627496f57e874033104fb420a23e9748e77306e558b85d.js

220 ms

clientlib-webpart.min.ACSHASH3e728647d7d1adf0fab0d5ec2d84ad5948f3c23429770bea83cb7c1fde08fd7a.js

clientlib-webpart.min.ACSHASH3e728647d7d1adf0fab0d5ec2d84ad5948f3c23429770bea83cb7c1fde08fd7a.js

221 ms

clientlib-container.min.ACSHASH533cf7122921bd3a4284ea270a75c1c5a86f4a912be8c61a59350b800ef3f190.js

clientlib-container.min.ACSHASH533cf7122921bd3a4284ea270a75c1c5a86f4a912be8c61a59350b800ef3f190.js

221 ms

clientlib-linklist.min.ACSHASHe2e2b6afca8812b04ed72036abb7022c61bf83d435a0f8fee27112f75699019c.js

clientlib-linklist.min.ACSHASHe2e2b6afca8812b04ed72036abb7022c61bf83d435a0f8fee27112f75699019c.js

222 ms

clientlib-itemlist.min.ACSHASH889ef3693ba05f6d728b700d9365fca8c0d6b871addfbce3b27327e51229324d.js

clientlib-itemlist.min.ACSHASH889ef3693ba05f6d728b700d9365fca8c0d6b871addfbce3b27327e51229324d.js

223 ms

clientlib-button.min.ACSHASHd97137f4b67b64852d3830289a4209692a47b7b38ffa660439e7ba832a611ae1.js

clientlib-button.min.ACSHASHd97137f4b67b64852d3830289a4209692a47b7b38ffa660439e7ba832a611ae1.js

222 ms

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

site.min.ACSHASH3e7d325ccd332e988ad389c886870dc4425700f7d167a11cab5564c0f72040d6.js

222 ms

clientlib-footer-region.min.ACSHASH545fe52ad9270ccb90dbcf814cf638be6ca76a881438cd7168a1ca5c316bd1d7.js

clientlib-footer-region.min.ACSHASH545fe52ad9270ccb90dbcf814cf638be6ca76a881438cd7168a1ca5c316bd1d7.js

224 ms

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

site.min.ACSHASHf96c143a11dc60634f649ea504d16ff799b1cbf433770c08903dc8fc2242ca7a.js

224 ms

clientlib-image.min.ACSHASH4b9bbc193da7c739358b0cae189458d5f02925314447e2ae77314d82e6e7d640.js

clientlib-image.min.ACSHASH4b9bbc193da7c739358b0cae189458d5f02925314447e2ae77314d82e6e7d640.js

222 ms

clientlib-badgecampaign.min.ACSHASH39fb25541246c78759274f98947436afa5a80265df9fd72e84353aafca739858.js

clientlib-badgecampaign.min.ACSHASH39fb25541246c78759274f98947436afa5a80265df9fd72e84353aafca739858.js

225 ms

unified-tracking.js

unified-tracking.js

30 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

74 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

36 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

37 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

35 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

36 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

37 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

39 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

37 ms

cq5dam.web.1280.1280.png

cq5dam.web.1280.1280.png

38 ms

false

false

144 ms

ancestry-icon.woff

ancestry-icon.woff

8 ms

ancestry-icon.woff

ancestry-icon.woff

197 ms

main.js

main.js

12 ms

footer-cc4c12e3.min.css

footer-cc4c12e3.min.css

8 ms

footer-235c199d.js

footer-235c199d.js

7 ms

Accessibility Review

shops.ancestry.com accessibility score

100

Accessibility Issues

Best Practices

shops.ancestry.com 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

shops.ancestry.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Shops.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 Shops.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.

Social Sharing Optimization

shops.ancestry.com

Open Graph description is not detected on the main page of Shops 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: