Access person.ancestry.de.

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value6.7 s

57/100

10%

person.ancestry.de

291 ms

3zKx6IAALAAKwCyAQECKwGyAgICKwG3AkQ2KiEUAAgrtwNANiohFAAIKwC3AVFDNCQXAAgrALIECAcrsAAgRX1pGERLsGBSWLABG7AAWbABjgA=

4 ms

P2J905sRc4yYcy+WG7H8Xsw+xuj+T26+V5zgK1eC3iu1Z7q+N9Nxc6JfEmMbegEdnrdDMCJ6PhgQnRBEPHBBb9mtRv3l5jXRJdbU5f98yseiAACwACsAsgEBAisBsgICAisBtwImHhgTDAAIK7cDJR4YEwwACCsAtwEwKCIYEAAIKwCyBAgHK7AAIEV9aRhES7BgUliwARuwAFmwAY4A

2 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Person.ancestry.de, 67% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (291 ms) belongs to the original domain Person.ancestry.de.

Content Size

536.8 kB

After Optimization

275.7 kB

In fact, the total size of Person.ancestry.de main page is 536.8 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. Only 10% of websites need less resources to load. HTML takes 536.8 kB which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 261.1 kB

Original 536.8 kB
After minification 535.9 kB
After compression 275.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. 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 261.1 kB or 49% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Page is blocked from indexing

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

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

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