47 sec in total
1.4 sec
42.3 sec
3.4 sec
Click here to check amazing Find A Grave content for United States. Otherwise, check out these important facts you probably never knew about findagrave.com
Find famous graves from cemeteries in .
Visit findagrave.comWe analyzed Findagrave.com page load time and found that the first response time was 1.4 sec and then it took 45.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
findagrave.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.3 s
22/100
25%
Value19.7 s
0/100
10%
Value34,060 ms
0/100
30%
Value0.18
67/100
15%
Value49.9 s
0/100
10%
1361 ms
845 ms
934 ms
872 ms
871 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 7% of them (7 requests) were addressed to the original Findagrave.com, 13% (13 requests) were made to Simage2.pubmatic.com and 6% (6 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (11.3 sec) relates to the external source Aax.amazon-adsystem.com.
Page size can be reduced by 1.2 MB (65%)
1.9 MB
659.4 kB
In fact, the total size of Findagrave.com main page is 1.9 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. 55% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 20.0 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. This page needs HTML code to be minified as it can gain 7.6 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.0 kB or 78% of the original size.
Potential reduce by 52 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. Find A Grave images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 64% of the original size.
Potential reduce by 41.4 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. Findagrave.com needs all CSS files to be minified and compressed as it can save up to 41.4 kB or 85% of the original size.
Number of requests can be reduced by 66 (75%)
88
22
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Find A Grave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and as a result speed up the page load time.
findagrave.com
1361 ms
main.css
845 ms
legacy.css
934 ms
domain-setter.js
872 ms
utag.sync.js
871 ms
jquery.min.js
872 ms
jquery-cookie.js
870 ms
findagravewhite.gif
1554 ms
buryicon.jpg
1554 ms
quant.js
2234 ms
ga.js
1386 ms
utag.js
325 ms
utag.2.js
188 ms
utag.3.js
178 ms
utag.13.js
1017 ms
utag.15.js
1377 ms
i.gif
2616 ms
__utm.gif
98 ms
apstag.js
1875 ms
adb.5781260.min.js
3018 ms
gpt.js
2404 ms
publishertag.js
2593 ms
rules-p-74FukXLzwUso-.js
2963 ms
rd
811 ms
dest5.html
2682 ms
id
2270 ms
pubads_impl_147.js
1570 ms
pixel.gif
496 ms
pixel.gif
563 ms
sovrn_standalone_beacon.js
3116 ms
pixel;r=1804686178;rf=0;a=p-74FukXLzwUso-;url=https%3A%2F%2Ffindagrave.com%2F;fpan=1;fpa=P0-1435111351-1504624135982;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504624135887;tzo=-180;ogl=
3019 ms
id
618 ms
ibs:dpid=411&dpuuid=Wa6_CAAAA4D3qV-i
2707 ms
s73462117302697
2265 ms
bid
11288 ms
jpt
9236 ms
jpt
8741 ms
kmn_sa_kb_c.15f9a8e69c664fe5820f612c02abd705.js
6783 ms
header
9363 ms
getjs.static.js
8036 ms
cygnus
10992 ms
jpt
8696 ms
14544.js
8669 ms
pubtaglib_0_4_0.js
7184 ms
bid
4620 ms
jpt
8611 ms
jpt
8362 ms
container.html
7704 ms
ads
3243 ms
LDR-search.php
5907 ms
osd_listener.js
4324 ms
osd.js
5905 ms
s
5956 ms
s
6024 ms
s
4291 ms
arj
2776 ms
sync
5021 ms
fastlane.json
3027 ms
LDR-search.css
1460 ms
jquery.min.js
840 ms
ADTECH;cfp=1;rndc=1504624150;cors=yes;cmd=bid;alias=FindAGrave_ConnectHB_Atf_728x90;grp=636;misc=1504624146472
3008 ms
user_sync.html
3008 ms
newspaperslogo-sm.png
1559 ms
__utm.gif
619 ms
showad.js
349 ms
collect
505 ms
PugMaster
889 ms
p-P7x87XHnVfbWr.gif
2670 ms
pixel
7464 ms
CookieSyncPubMatic
7143 ms
sync
7469 ms
Pug
7856 ms
epm
9727 ms
ps
7255 ms
activeview
1276 ms
Pug
7564 ms
generic
1597 ms
Pug
3379 ms
generic
1997 ms
Pug
3714 ms
Pug
2613 ms
Pug
3480 ms
Pug
3389 ms
cfcm.ashx
754 ms
Pug
2874 ms
Pug
2737 ms
mapuser
1639 ms
sync
1934 ms
receive
1571 ms
Pug
3289 ms
Pug
2975 ms
i.match
2185 ms
receive
1847 ms
Pug
1962 ms
Pug
2105 ms
ecc
2511 ms
Pug
1725 ms
sn.ashx
1177 ms
Pug
737 ms
1x1
901 ms
px
289 ms
Pug
22 ms
findagrave.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
findagrave.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
findagrave.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Findagrave.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 Findagrave.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.
findagrave.com
Open Graph description is not detected on the main page of Find A Grave. 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: