12.4 sec in total
536 ms
9.5 sec
2.4 sec
Click here to check amazing CAPTAINSDEAD content for Japan. Otherwise, check out these important facts you probably never knew about captainsdead.com
Forsale Lander
Visit captainsdead.comWe analyzed Captainsdead.com page load time and found that the first response time was 536 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
captainsdead.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value4.3 s
42/100
25%
Value4.5 s
73/100
10%
Value2,290 ms
5/100
30%
Value0
100/100
15%
Value10.4 s
24/100
10%
536 ms
92 ms
106 ms
234 ms
141 ms
Our browser made a total of 187 requests to load all elements on the main page. We found that 12% of them (22 requests) were addressed to the original Captainsdead.com, 11% (20 requests) were made to Ecx.images-amazon.com and 7% (13 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source S.ytimg.com.
Page size can be reduced by 1.6 MB (40%)
4.2 MB
2.5 MB
In fact, the total size of Captainsdead.com main page is 4.2 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 89.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 89.5 kB or 78% of the original size.
Potential reduce by 120.0 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. CAPTAINSDEAD images are well optimized though.
Potential reduce by 911.6 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 911.6 kB or 65% of the original size.
Potential reduce by 522.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. Captainsdead.com needs all CSS files to be minified and compressed as it can save up to 522.6 kB or 63% of the original size.
Number of requests can be reduced by 92 (54%)
169
77
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAPTAINSDEAD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
captainsdead.com
536 ms
wp-emoji-release.min.js
92 ms
twentysixteen.css
106 ms
css
234 ms
genericons.css
141 ms
style.css
110 ms
jetpack.css
134 ms
jquery.js
181 ms
jquery-migrate.min.js
180 ms
buttons.js
203 ms
q
205 ms
adsbygoogle.js
188 ms
devicepx-jetpack.js
154 ms
gprofiles.js
183 ms
wpgroho.js
146 ms
skip-link-focus-fix.js
151 ms
functions.js
151 ms
wp-embed.min.js
149 ms
e-201611.js
144 ms
caleb-1024x1024.jpg
467 ms
708 ms
729 ms
cca71e340e19683642b3507345f4d98b
464 ms
dtKpHJSVUd8
717 ms
7ArKJ5k1Vnc
1181 ms
pbCGhmrwuFU
2064 ms
1015 ms
1038 ms
IQ187y5sH3E
2078 ms
1009 ms
974 ms
eliza.jpg
251 ms
tortoise.png
979 ms
Neil+Young++Crazy+Horse.jpg
252 ms
25_lizphair_lg.jpg
251 ms
Paul+Westerberg+25575610.gif
342 ms
Ringo-Deathstarr-new.jpg
255 ms
blazes-1024x1021.jpg
340 ms
jewels.jpg
339 ms
RFda8w1V0eDZheqfcyQ4EBa1RVmPjeKy21_GQJaLlJI.woff
1764 ms
ZvcMqxEwPfh2qDWBPxn6nhGYIVA-f1n-gQW6IKoy_-M.woff
2222 ms
ZvcMqxEwPfh2qDWBPxn6njPY4jw7fdqC-GX3uhj9onc.woff
2566 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
2581 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
2564 ms
So5lHxHT37p2SS4-t60SlISNse2zJAGBOX1vGC0HDBk.woff
2565 ms
EYh7Vl4ywhowqULgRdYwIMr_TVbVq9Kr5jxArfkA4r0.woff
2939 ms
EYh7Vl4ywhowqULgRdYwIJlz6iQBFPof_L1ddMkCdfk.woff
2765 ms
Genericons.svg
251 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
7 ms
sdk.js
434 ms
embed.spotify.com
2256 ms
getad
751 ms
json
750 ms
ca-pub-0221352983731846.js
1725 ms
zrt_lookup.html
1704 ms
show_ads_impl.js
309 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
2618 ms
widget-0511d506.css
577 ms
widget-d9304090.js
1575 ms
www-embed-player-vflRGs1ko.css
2140 ms
www-embed-player.js
2433 ms
base.js
3561 ms
ads
1859 ms
osd.js
1620 ms
ads
1671 ms
2056 ms
amznassocview.js
1478 ms
q
930 ms
q
1110 ms
q
1307 ms
q
1300 ms
hovercard.css
478 ms
services.css
860 ms
getAllAppDefault.esi
686 ms
xd_arbiter.php
692 ms
xd_arbiter.php
1357 ms
g.gif
815 ms
css
540 ms
spb.2ba359a.css
1463 ms
md.2ba359a.js
1676 ms
getSegment.php
644 ms
checkOAuth.esi
296 ms
page.php
1073 ms
%7B%22adViewability%22:[%7B%22above_the_fold%22:%20false,%20%22topPos%22:%201.5752380952380953,%20%22leftPos%22:%200.6797619047619048%7D]%7D&cb=6814538
114 ms
13628426538216848509
1263 ms
abg.js
2011 ms
m_js_controller.js
2039 ms
googlelogo_color_112x36dp.png
2024 ms
13385613206255327016
2023 ms
search-widget-sprite.png
930 ms
loader._V1387883855_.gif
355 ms
t.dhj
1047 ms
logo-200x120-177df3dd.png
622 ms
json
320 ms
ir
601 ms
602 ms
61YSiYTJBHL._SL160_.jpg
592 ms
pOm-b7lJL8q.css
1877 ms
FAHeNGXgPup.js
2004 ms
YvxwM8R7ol8.js
2349 ms
ihptErjAmMX.js
2348 ms
json
339 ms
1095 ms
51wRPhJivWL._SL160_.jpg
900 ms
41Isdetu1jL._SL160_.jpg
900 ms
51ZIWCF0d5L._SL160_.jpg
1089 ms
61ujIIMyW7L._SL160_.jpg
1066 ms
51yFqSQ7dhL._SL160_.jpg
1049 ms
51ENctTSxaL._SL160_.jpg
1070 ms
51Cofu-wz6L._SL160_.jpg
1068 ms
51HGuoYiOZL._SL160_.jpg
1068 ms
51yGCNhmUHL._SL160_.jpg
1071 ms
41KqCrQ2fuL._SL160_.jpg
1070 ms
51ARMgbPO6L._SL160_.jpg
1071 ms
51rLz1VhD6L._SL160_.jpg
1074 ms
61iF4fwUthL._SL160_.jpg
1737 ms
51CtmBFO6uL._SL160_.jpg
1074 ms
51aGM8vETPL._SL160_.jpg
1079 ms
51H8x07Fd7L._SL160_.jpg
1080 ms
51FqgGeD7wL._SL160_.jpg
1078 ms
41uL4tOQsvL._SL160_.jpg
1152 ms
51eRn36WYpL._SL160_.jpg
1152 ms
analytics.js
1914 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
1283 ms
ad_status.js
1337 ms
ga.js
1689 ms
single-sound-cd67be80.js
913 ms
error-698b3c1d.js
905 ms
x_button_blue2.png
885 ms
c0a1d2565f49f52556dc406cfc8ab6d35a82f7aa
1693 ms
all.js
972 ms
proxima_nova_regular_1.woff
1361 ms
proxima_nova_thin_1.woff
1370 ms
proxima_nova_semibold_1.woff
1584 ms
spoticon_38d8b3d1a7647c3696de8982a0d8d7dd.svg
1705 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
617 ms
buttons.ab966a004186897711de4a5ed256c924.css
202 ms
t.dhj
204 ms
cm
627 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
328 ms
st.1188278743c14064d5e8ae56c8ada29c.js
500 ms
s
843 ms
redir.html
1973 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
819 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
816 ms
beacon.js
1203 ms
10678687_743894018981083_1837303205462120361_n.jpg
1103 ms
229131_199242816779542_3986150_n.jpg
1100 ms
1237019_1522360608066226_181857506939722944_n.jpg
1825 ms
12346591_924223164279578_2396206693740220635_n.jpg
1836 ms
12243187_553203688179456_2296951678522548882_n.jpg
1844 ms
486215_564242486938472_1581465321_n.jpg
1844 ms
12809537_10204052074701304_1311401493274015309_n.jpg
1842 ms
74604_1752478818030_5625789_n.jpg
1839 ms
12806255_10153233120797820_4456773098707632752_n.jpg
1844 ms
wL6VQj7Ab77.png
691 ms
s7jcwEQH7Sx.png
690 ms
logo_grey-377f1b9e.png
720 ms
collect
1423 ms
hbpix
1152 ms
s-3271.xgi
403 ms
1097 ms
__utm.gif
820 ms
__utm.gif
1051 ms
__utm.gif
1055 ms
__utm.gif
1111 ms
__utm.gif
1111 ms
__utm.gif
1106 ms
744 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
458 ms
2981
745 ms
405 ms
__utm.gif
380 ms
__utm.gif
377 ms
xrefid.xgi
325 ms
R9a_DtVRZgv.js
303 ms
cUDgRFxaoIk.js
304 ms
0JBr1QHp8Gi.js
294 ms
kDOzhTr2W91.js
348 ms
ga-audiences
349 ms
iframe.html
238 ms
__utm.gif
172 ms
__utm.gif
203 ms
__utm.gif
202 ms
__utm.gif
204 ms
collect
24 ms
xd_arbiter.php
15 ms
captainsdead.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
captainsdead.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
captainsdead.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Captainsdead.com 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 Captainsdead.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.
captainsdead.com
Open Graph description is not detected on the main page of CAPTAINSDEAD. 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: