Access genealogysearch.org. GenealogySearch.org

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

genealogysearch.org

67 ms

adsbygoogle.js

109 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Genealogysearch.org, 50% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (109 ms) relates to the external source Pagead2.googlesyndication.com.

Content Size

67.8 kB

After Optimization

65.0 kB

In fact, the total size of Genealogysearch.org main page is 67.8 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Javascripts take 63.8 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 2.7 kB

Original 4.0 kB
After minification 3.8 kB
After compression 1.3 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 2.7 kB or 68% of the original size.

JavaScript Optimization

-0%

Potential reduce by 20 B

Original 63.8 kB
After minification 63.8 kB
After compression 63.8 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. This website has mostly compressed JavaScripts.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genealogy Search. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Page has valid source maps

Search Engine Optimization Advices

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genealogysearch.org 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 Genealogysearch.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

genealogysearch.org

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