Tools & Wizards About Us
ancestry.de screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

ancestry.de

Ancestry® | Ahnenforschung, Stammbaum und Familiengeschichte

Page Load Speed

3.6 sec in total

First Response

130 ms

Resources Loaded

3.2 sec

Page Rendered

200 ms

ancestry.de screenshot

About Website

Visit ancestry.de now to see the best up-to-date Ancestry content for Germany and also check out these interesting facts you probably never knew about ancestry.de

Ancestry.de bietet historische Daten und Dokumente für Ahnenforschung. Erstellung eines Familienstammbaums online und Informationen und Tipps rund um die Ahnenforschung und Genealogie.

Visit ancestry.de

Key Findings

We analyzed Ancestry.de page load time and found that the first response time was 130 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ancestry.de performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value2,390 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

ancestry.de

130 ms

www.ancestry.de

263 ms

combo.ashx

33 ms

combo.ashx

42 ms

header.js

39 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ancestry.de, 32% (30 requests) were made to C.mfcreative.com and 16% (15 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Mitsvc.ancestry.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 474.1 kB (42%)

Content Size

1.1 MB

After Optimization

664.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ancestry.de main page is 1.1 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. 60% of websites need less resources to load. Images take 471.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 52.3 kB

  • Original 69.9 kB
  • After minification 67.3 kB
  • After compression 17.5 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 52.3 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 2.1 kB

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

JavaScript Optimization

-67%

Potential reduce by 274.3 kB

  • Original 410.7 kB
  • After minification 402.4 kB
  • After compression 136.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 274.3 kB or 67% of the original size.

CSS Optimization

-78%

Potential reduce by 145.4 kB

  • Original 186.4 kB
  • After minification 183.6 kB
  • After compression 41.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.de needs all CSS files to be minified and compressed as it can save up to 145.4 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (66%)

Requests Now

73

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ancestry.de

ancestry.de

130 ms

www.ancestry.de

www.ancestry.de

263 ms

combo.ashx

combo.ashx

33 ms

combo.ashx

combo.ashx

42 ms

header.js

header.js

39 ms

header.css

header.css

30 ms

v1.css

v1.css

25 ms

alert.js

alert.js

38 ms

combo.ashx

combo.ashx

38 ms

callout.js

callout.js

67 ms

template.css

template.css

72 ms

ancestry-on-dark.svg

ancestry-on-dark.svg

7 ms

progen.svg

progen.svg

3 ms

ancestry-de.png

ancestry-de.png

10 ms

delohp-tv-logos.jpg

delohp-tv-logos.jpg

9 ms

delohp-trees.jpg

delohp-trees.jpg

7 ms

delohp-quotes-anja.png

delohp-quotes-anja.png

10 ms

standard

standard

13 ms

delohp-hero-bkg2.jpg

delohp-hero-bkg2.jpg

45 ms

X0ABE2EFBDB34007DD6909340B8FB872B.js

X0ABE2EFBDB34007DD6909340B8FB872B.js

211 ms

standard

standard

13 ms

delohp-icons-sprite.png

delohp-icons-sprite.png

50 ms

delohp-quotes-bkg.jpg

delohp-quotes-bkg.jpg

35 ms

delohp-contact-bkg.jpg

delohp-contact-bkg.jpg

51 ms

utag.js

utag.js

80 ms

ga.js

ga.js

30 ms

source-sans-pro.woff

source-sans-pro.woff

4 ms

source-sans-pro-light.woff

source-sans-pro-light.woff

10 ms

source-sans-pro-semi-bold.woff

source-sans-pro-semi-bold.woff

17 ms

source-sans-pro-bold.woff

source-sans-pro-bold.woff

9 ms

__utm.gif

__utm.gif

17 ms

ancestry-icon.woff

ancestry-icon.woff

23 ms

combo.ashx

combo.ashx

10 ms

combo.ashx

combo.ashx

189 ms

utag.50.js

utag.50.js

23 ms

utag.86.js

utag.86.js

12 ms

utag.93.js

utag.93.js

22 ms

utag.97.js

utag.97.js

21 ms

utag.98.js

utag.98.js

21 ms

utag.101.js

utag.101.js

21 ms

utag.102.js

utag.102.js

21 ms

utag.108.js

utag.108.js

23 ms

utag.112.js

utag.112.js

22 ms

utag.134.js

utag.134.js

22 ms

utag.136.js

utag.136.js

22 ms

utag.145.js

utag.145.js

83 ms

utag.156.js

utag.156.js

83 ms

utag.161.js

utag.161.js

83 ms

__utm.gif

__utm.gif

58 ms

conversion_async.js

conversion_async.js

25 ms

rd

rd

1313 ms

fbds.js

fbds.js

23 ms

ld.js

ld.js

34 ms

fbevents.js

fbevents.js

19 ms

combo.ashx

combo.ashx

61 ms

collect

collect

72 ms

affadvc.aspx

affadvc.aspx

325 ms

script.js

script.js

292 ms

65 ms

114 ms

182 ms

event

event

29 ms

pixel

pixel

18 ms

event

event

169 ms

37 ms

pixel

pixel

16 ms

r2

r2

5 ms

affact.aspx

affact.aspx

275 ms

s.aspx

s.aspx

323 ms

si.aspx

si.aspx

328 ms

events

events

286 ms

e9008746e1.js

e9008746e1.js

275 ms

30785.html

30785.html

51 ms

p.min.js

p.min.js

420 ms

combo.ashx

combo.ashx

4 ms

combo.ashx

combo.ashx

7 ms

e9008746e1.js

e9008746e1.js

292 ms

ancestry.svg

ancestry.svg

111 ms

geo-header.jpg

geo-header.jpg

21 ms

source-sans-pro.woff

source-sans-pro.woff

19 ms

source-sans-pro-light.woff

source-sans-pro-light.woff

19 ms

source-sans-pro-semi-bold.woff

source-sans-pro-semi-bold.woff

20 ms

source-sans-pro-bold.woff

source-sans-pro-bold.woff

20 ms

ancestry-icon.woff

ancestry-icon.woff

19 ms

source-sans-pro-italic.woff

source-sans-pro-italic.woff

18 ms

source-sans-pro-italic.woff

source-sans-pro-italic.woff

18 ms

source-sans-pro-light-italic.woff

source-sans-pro-light-italic.woff

18 ms

source-sans-pro-light-italic.woff

source-sans-pro-light-italic.woff

16 ms

401 ms

e9008746e1.html

e9008746e1.html

187 ms

retarget

retarget

201 ms

dis.aspx

dis.aspx

213 ms

19 ms

Accessibility Review

ancestry.de accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

ancestry.de best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ancestry.de 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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ancestry.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Ancestry.de 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.de

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: