2.3 sec in total
107 ms
2 sec
263 ms
Visit genealogybuff.com now to see the best up-to-date Genealogy Buff content for United States and also check out these interesting facts you probably never knew about genealogybuff.com
free online obituary collections, free online obituary archives, a free genealogy site for locating ancestors, free obituary searches, free obituary collections, free obituary archives, large genealog...
Visit genealogybuff.comWe analyzed Genealogybuff.com page load time and found that the first response time was 107 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
genealogybuff.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value4.9 s
28/100
25%
Value10.4 s
8/100
10%
Value6,680 ms
0/100
30%
Value0
100/100
15%
Value36.1 s
0/100
10%
107 ms
109 ms
15 ms
164 ms
269 ms
Our browser made a total of 217 requests to load all elements on the main page. We found that 9% of them (20 requests) were addressed to the original Genealogybuff.com, 63% (136 requests) were made to Rc.rlcdn.com and 9% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (819 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 317.9 kB (64%)
497.2 kB
179.2 kB
In fact, the total size of Genealogybuff.com main page is 497.2 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. 45% of websites need less resources to load. Javascripts take 277.2 kB which makes up the majority of the site volume.
Potential reduce by 16.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 16.2 kB or 71% of the original size.
Potential reduce by 8.5 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. Obviously, Genealogy Buff needs image optimization as it can save up to 8.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 189.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 189.4 kB or 68% of the original size.
Potential reduce by 103.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. Genealogybuff.com needs all CSS files to be minified and compressed as it can save up to 103.9 kB or 87% of the original size.
Number of requests can be reduced by 172 (80%)
215
43
The browser has sent 215 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genealogy Buff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
genealogybuff.com
107 ms
prp728.htm
109 ms
image-1543849-10470501-1449535196000
15 ms
100160.html
164 ms
all.js
269 ms
nmedianet.js
36 ms
library.gif
29 ms
uco.gif
60 ms
search.gif
60 ms
ucd.gif
59 ms
newspapers.gif
60 ms
canada_obits.gif
61 ms
surnames.gif
60 ms
finding.gif
81 ms
free_ancestry.gif
80 ms
research.gif
84 ms
vitals.gif
86 ms
cities.gif
82 ms
census.gif
85 ms
counties.gif
105 ms
cemeteries.gif
106 ms
software.gif
107 ms
immigration.gif
106 ms
gbbanner.jpg
106 ms
px.gif
12 ms
bping.php
7 ms
fcmdynet.js
164 ms
px.gif
19 ms
pbArchivesTransparentWhite.png
45 ms
btn_searchBlue.gif
31 ms
bootstrap.css
176 ms
jquery.js
223 ms
bootstrap.js
181 ms
mediamain.html
269 ms
counter.js
13 ms
t.php
172 ms
403266.html
44 ms
66 ms
xrefid.xgi
25 ms
px
26 ms
xd_arbiter.php
253 ms
xd_arbiter.php
456 ms
52154.gif
9 ms
378348.gif
8 ms
logo-small.png
47 ms
glyphicons-halflings-regular.woff
44 ms
1x1pixel.png
7 ms
47154.gif
9 ms
nrr.js
24 ms
AdChoices.png
21 ms
like_box.php
200 ms
bql.php
15 ms
px.gif
159 ms
FbUd6dZS1Af.css
285 ms
dGJLq38YL-C.css
353 ms
f7m6HODnCDd.css
422 ms
i5_N_HL0uEJ.css
553 ms
Msuaq9yC6iC.css
563 ms
_rx8naC75Dy.js
621 ms
x5F9OMjKyLw.js
647 ms
ICDbTSzjQEg.js
490 ms
TTCre3391I0.js
490 ms
njO1TPvGzoR.js
572 ms
b_6HNn_J2BZ.js
573 ms
7cm7D75Y0Sf.js
685 ms
rFmE1g6Dkoz.js
819 ms
336JejShbZp.js
662 ms
403266.gif
4 ms
403266.gif
6 ms
403266.gif
8 ms
403266.gif
6 ms
403266.gif
10 ms
403266.gif
11 ms
403266.gif
10 ms
403266.gif
10 ms
403266.gif
10 ms
403266.gif
11 ms
403266.gif
10 ms
403266.gif
8 ms
403266.gif
8 ms
403266.gif
9 ms
403266.gif
9 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
4 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
8 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
7 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
10 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
7 ms
403266.gif
6 ms
403266.gif
7 ms
403266.gif
5 ms
403266.gif
7 ms
403266.gif
7 ms
403266.gif
7 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
13 ms
403266.gif
5 ms
403266.gif
7 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
10 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
7 ms
403266.gif
12 ms
403266.gif
4 ms
403266.gif
4 ms
403266.gif
4 ms
403266.gif
4 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
8 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
8 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
10 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
9 ms
403266.gif
8 ms
403266.gif
9 ms
403266.gif
7 ms
403266.gif
8 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
63 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
5 ms
403266.gif
4 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
4 ms
403266.gif
10 ms
403266.gif
6 ms
403266.gif
6 ms
403266.gif
5 ms
403266.gif
6 ms
403266.gif
4 ms
403266.gif
5 ms
403266.gif
5 ms
12742400_10153886363875692_8791763584394819804_n.jpg
126 ms
safe_image.php
127 ms
12042607_10153622013585692_548834338152471985_n.jpg
120 ms
11998900_1056853601031667_7267796647781365872_n.jpg
125 ms
1471810_10200230720571251_165983811_n.jpg
123 ms
12670385_10154012416259783_8264588305044837314_n.jpg
126 ms
644495_10151499613319722_1867747754_n.jpg
124 ms
12734078_10153522484097620_4577246507101806113_n.jpg
125 ms
12274198_975355915856236_5197680277258116461_n.jpg
122 ms
wL6VQj7Ab77.png
111 ms
s7jcwEQH7Sx.png
110 ms
QDwYpIaRyfG.png
110 ms
a-ZN6WoEOje.png
111 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
134 ms
genealogybuff.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
genealogybuff.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
genealogybuff.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genealogybuff.com 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 Genealogybuff.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.
genealogybuff.com
Open Graph description is not detected on the main page of Genealogy Buff. 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: