6.5 sec in total
492 ms
4.7 sec
1.3 sec
Click here to check amazing Distantcousin content for United States. Otherwise, check out these important facts you probably never knew about distantcousin.com
Free Genealogy and Family History Research including city directories, obituaries, military, cemetery photographs, marriage records
Visit distantcousin.comWe analyzed Distantcousin.com page load time and found that the first response time was 492 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
distantcousin.com performance score
492 ms
17 ms
8 ms
353 ms
706 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 20% of them (10 requests) were addressed to the original Distantcousin.com, 14% (7 requests) were made to Apis.google.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 39.2 kB (52%)
75.6 kB
36.4 kB
In fact, the total size of Distantcousin.com main page is 75.6 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. 65% of websites need less resources to load. HTML takes 35.2 kB which makes up the majority of the site volume.
Potential reduce by 25.8 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 25.8 kB or 73% of the original size.
Potential reduce by 27 B
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. Distantcousin images are well optimized though.
Potential reduce by 11.5 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 11.5 kB or 34% of the original size.
Potential reduce by 1.9 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. Distantcousin.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 75% of the original size.
Number of requests can be reduced by 29 (64%)
45
16
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Distantcousin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
distantcousin.com
492 ms
stylesheet.css
17 ms
show_ads.js
8 ms
all.js
353 ms
ca-pub-4413761096642534.js
706 ms
zrt_lookup.html
1037 ms
show_ads_impl.js
243 ms
widgets.js
644 ms
dc_logo.gif
859 ms
corner_top_left.gif
859 ms
corner_top_right.gif
919 ms
corner_bottom_left.gif
919 ms
corner_bottom_right.gif
902 ms
blue-star.gif
935 ms
Bottom-Nav.js
858 ms
Copyright.js
858 ms
image-2771901-10596726
823 ms
ads
490 ms
osd.js
395 ms
10596726-1427754973563
214 ms
css
568 ms
m_js_controller.js
448 ms
abg.js
743 ms
718 ms
xd_arbiter.php
689 ms
xd_arbiter.php
1189 ms
plusone.js
1189 ms
button.b059c0eb61ea902a882e5c5b3c66a17a.js
597 ms
favicon
1183 ms
googlelogo_color_112x36dp.png
1189 ms
nessie_icon_tiamat_white.png
321 ms
like.php
622 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
1072 ms
x_button_blue2.png
141 ms
s
505 ms
tweet_button.baa54ded21a982344c4ced326592f3de.en.html
342 ms
zH0IPw-UmpL.js
1644 ms
LVx-xkvaJ0b.png
1614 ms
cb=gapi.loaded_0
188 ms
cb=gapi.loaded_1
488 ms
fastbutton
731 ms
AUrdvhejKSJD2XN0WEoLkNJn8VW-ISfFFTHwdQR0Ws4.js
309 ms
jot
681 ms
postmessageRelay
686 ms
cb=gapi.loaded_0
444 ms
cb=gapi.loaded_1
143 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
360 ms
api.js
93 ms
core:rpc:shindig.random:shindig.sha1.js
173 ms
2536007149-postmessagerelay.js
173 ms
distantcousin.com SEO score
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Distantcousin.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Distantcousin.com main page’s claimed encoding is iso-8859-1. 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.
distantcousin.com
Open Graph description is not detected on the main page of Distantcousin. 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: