6.6 sec in total
1.7 sec
4.1 sec
808 ms
Click here to check amazing Death content. Otherwise, check out these important facts you probably never knew about death.io
Take control of your digital death, your unique legacy and all end of life planning. We give you the tools and information to get death in order.
Visit death.ioWe analyzed Death.io page load time and found that the first response time was 1.7 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
death.io performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value13.6 s
0/100
25%
Value10.4 s
8/100
10%
Value6,520 ms
0/100
30%
Value0.128
82/100
15%
Value22.4 s
1/100
10%
1712 ms
88 ms
135 ms
387 ms
56 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 36% of them (28 requests) were addressed to the original Death.io, 13% (10 requests) were made to C0.wp.com and 10% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Death.io.
Page size can be reduced by 103.3 kB (2%)
6.5 MB
6.4 MB
In fact, the total size of Death.io main page is 6.5 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.8 MB which makes up the majority of the site volume.
Potential reduce by 60.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 60.2 kB or 78% of the original size.
Potential reduce by 37.1 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. Death images are well optimized though.
Potential reduce by 3.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Death.io has all CSS files already compressed.
Number of requests can be reduced by 42 (58%)
73
31
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Death. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
death.io
1712 ms
js
88 ms
gtm.js
135 ms
wp-emoji-release.min.js
387 ms
color-picker.min.css
56 ms
style.min.css
54 ms
912fe.css
573 ms
jetpack.css
94 ms
jquery.js
97 ms
jquery-migrate.min.js
93 ms
5753e.js
439 ms
3b239.js
381 ms
0e602.js
379 ms
css
97 ms
email-decode.min.js
44 ms
devicepx-jetpack.js
66 ms
imagesloaded.min.js
44 ms
masonry.min.js
45 ms
jquery.masonry.min.js
49 ms
2db90.js
460 ms
ae8ba.js
652 ms
1877a.js
672 ms
twitter-timeline.min.js
52 ms
wp-embed.min.js
52 ms
e-202403.js
66 ms
js
63 ms
analytics.js
39 ms
collect
50 ms
collect
37 ms
ga-audiences
34 ms
css
13 ms
DEATHiO_logo-1WhiteWide400px.png
621 ms
tRPdfai3igs
181 ms
n5j5p3TnAo4
610 ms
Astronaut-Mem-smaller.png
1088 ms
Iternal-Devices-Screens.png
1351 ms
Iternal-white-transparent.png
1035 ms
DeathLogo.png
1041 ms
Storyhead300green-150x150.png
1047 ms
DigitalDeathLogo1Green-150x150.png
1086 ms
tools-for-motivation-301199-unsplash-e1522942484466.jpg
1388 ms
Screenshot-2020-04-03-at-02.17.47-300x97.png
1381 ms
Phone-Angle-1-e1587554422264.png
1603 ms
david-pisnoy-542340-unsplash-e1530616260939.jpg
1431 ms
matus-kovacovsky-248993-unsplash.jpg
609 ms
caspar-rubin-680342-unsplash-e1545153038731.jpg
711 ms
xiaoxiao-sun-455472-unsplash-e1533555048798.jpg
606 ms
Lato.ttf
715 ms
icomoon.ttf
561 ms
squared-icomoon.woff
637 ms
widgets.js
354 ms
fbevents.js
117 ms
collect
24 ms
likebox.php
331 ms
admin-ajax.php
1075 ms
www-player.css
15 ms
www-embed-player.js
59 ms
base.js
84 ms
ad_status.js
615 ms
07R8eGzDB3q.css
607 ms
S-jgxi6wsFP.js
621 ms
Cn_OgNtBsi4.js
619 ms
ru8zNtgW1u3.js
649 ms
WDd6AOxHz0q.js
655 ms
Gnm9vzFr_bN.js
653 ms
p55HfXW__mM.js
647 ms
MKv6dd4Y7ScI2r12JDuH_6cRH5RlWjwOe1eCzKxNtUM.js
244 ms
embed.js
198 ms
id
18 ms
Create
51 ms
Create
191 ms
304973390_524528939543890_4534218368621905038_n.png
134 ms
UXtr_j2Fwe-.png
115 ms
GenerateIT
98 ms
GenerateIT
14 ms
widgets.js
23 ms
in.js
61 ms
death.io 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
Links do not have a discernible name
death.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
death.io 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Death.io 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 Death.io 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.
death.io
Open Graph data is detected on the main page of Death. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: