794 ms in total
104 ms
581 ms
109 ms
Click here to check amazing Death Date content for United States. Otherwise, check out these important facts you probably never knew about deathdate.info
Death Date is a mysterious place where you will find out when you are going to die... but do you have the guts?
Visit deathdate.infoWe analyzed Deathdate.info page load time and found that the first response time was 104 ms and then it took 690 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
deathdate.info performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value2.1 s
96/100
25%
Value5.4 s
57/100
10%
Value1,890 ms
9/100
30%
Value0
100/100
15%
Value10.8 s
22/100
10%
104 ms
8 ms
12 ms
22 ms
16 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 58% of them (21 requests) were addressed to the original Deathdate.info, 11% (4 requests) were made to Pagead2.googlesyndication.com and 11% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (208 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 21.9 kB (32%)
68.9 kB
46.9 kB
In fact, the total size of Deathdate.info main page is 68.9 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. 25% of websites need less resources to load. Javascripts take 26.2 kB which makes up the majority of the site volume.
Potential reduce by 6.5 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 6.5 kB or 69% of the original size.
Potential reduce by 312 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. Death Date images are well optimized though.
Potential reduce by 4.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 4.5 kB or 17% of the original size.
Potential reduce by 10.6 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. Deathdate.info needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 80% of the original size.
Number of requests can be reduced by 24 (71%)
34
10
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Death Date. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
deathdate.info
104 ms
screen.css
8 ms
javascript.js
12 ms
urchin.js
22 ms
show_ads.js
16 ms
zs_logo.jpg
139 ms
ca-pub-3339664392515615.js
55 ms
zrt_lookup.html
55 ms
show_ads_impl.js
73 ms
__utm.gif
35 ms
zs_nav-s.jpg
41 ms
zs_nav.jpg
36 ms
zs_undrl.gif
35 ms
zs_hr.jpg
33 ms
zs_clock.png
35 ms
sb_delicious.gif
40 ms
sb_digg.gif
46 ms
sb_furl.gif
39 ms
sb_magnolia.gif
53 ms
sb_reddit.gif
55 ms
sb_spurl.gif
52 ms
sb_stumble.gif
55 ms
sb_technorati.gif
55 ms
sb_google.gif
53 ms
zs_sitemap.gif
56 ms
zs_mail.gif
58 ms
zs_feed.gif
56 ms
ads
208 ms
osd.js
6 ms
m_js_controller.js
25 ms
abg.js
35 ms
favicon
60 ms
googlelogo_color_112x36dp.png
56 ms
nessie_icon_thin_arrow_big_white.png
34 ms
s
13 ms
x_button_blue2.png
7 ms
deathdate.info 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
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
deathdate.info 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
Browser errors were logged to the console
deathdate.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Deathdate.info 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 Deathdate.info 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.
deathdate.info
Open Graph data is detected on the main page of Death Date. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: