6.3 sec in total
727 ms
5.3 sec
245 ms
Welcome to notdeadyet.jp homepage info - get ready to check Notdeadyet best content for Japan right away, or after learning these important things about notdeadyet.jp
notdeadyet.jp is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, notdeadyet.jp has it all. We hope you find...
Visit notdeadyet.jpWe analyzed Notdeadyet.jp page load time and found that the first response time was 727 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
notdeadyet.jp performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value8.0 s
3/100
25%
Value5.9 s
48/100
10%
Value120 ms
97/100
30%
Value0.011
100/100
15%
Value8.1 s
41/100
10%
727 ms
500 ms
358 ms
705 ms
52 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 35% of them (35 requests) were addressed to the original Notdeadyet.jp, 23% (23 requests) were made to Static.xx.fbcdn.net and 18% (18 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 139.9 kB (13%)
1.1 MB
957.5 kB
In fact, the total size of Notdeadyet.jp main page is 1.1 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. Images take 964.0 kB which makes up the majority of the site volume.
Potential reduce by 7.1 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 7.1 kB or 65% of the original size.
Potential reduce by 34.2 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. Notdeadyet images are well optimized though.
Potential reduce by 64.8 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 64.8 kB or 79% of the original size.
Potential reduce by 33.8 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. Notdeadyet.jp needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 85% of the original size.
Number of requests can be reduced by 51 (53%)
97
46
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Notdeadyet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
notdeadyet.jp
727 ms
common.css
500 ms
style.css
358 ms
prettyPhoto.css
705 ms
jquery.min.js
52 ms
jquery.prettyPhoto.js
907 ms
index.js
372 ms
scrollsmoothly.js
557 ms
plusone.js
53 ms
sha1.js
533 ms
oauth.js
941 ms
twitter.js
659 ms
cb=gapi.loaded_0
22 ms
bg.png
1639 ms
logo.png
550 ms
trailer.png
180 ms
news_bg.png
172 ms
news-text_bg.png
189 ms
twitter.png
195 ms
gnav01.png
343 ms
gnav02.png
357 ms
gnav03.png
384 ms
gnav04.png
390 ms
gnav05.png
506 ms
gnav06.png
532 ms
gnav07.png
571 ms
gnav08.png
577 ms
release.png
834 ms
credit01.png
709 ms
credit02.png
731 ms
award.gif
1186 ms
pagatop.png
805 ms
lower_logo.png
884 ms
contact.png
925 ms
fnews_heading.png
992 ms
fnews_twitter.png
998 ms
fnews_facebook.png
1120 ms
user_timeline.json
123 ms
nav_bg.png
1103 ms
widgets.js
18 ms
cb=gapi.loaded_1
8 ms
fastbutton
68 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
16 ms
postmessageRelay
41 ms
likebox.php
605 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
15 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
18 ms
3193398744-postmessagerelay.js
32 ms
rpc:shindig_random.js
37 ms
like.php
158 ms
cb=gapi.loaded_0
3 ms
jot
111 ms
qeKvIRsJabD.js
300 ms
LVx-xkvaJ0b.png
339 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
29 ms
qeKvIRsJabD.js
122 ms
kyEKgjk51ZE.css
132 ms
xgj7bXhJNEH.css
171 ms
Czh0gDTFcBt.css
176 ms
N-k91nHCZS2.css
213 ms
ZeuPykSxSED.css
219 ms
q68gy-v_YMF.js
211 ms
FJmpeSpHpjS.js
217 ms
0wM5s1Khldu.js
217 ms
1bNoFZUdlYZ.js
217 ms
njO1TPvGzoR.js
253 ms
1QuX41zDRrx.js
257 ms
Oagsvfb4VWi.js
291 ms
LTv6ZK-5zxz.js
331 ms
1FCa-btixu2.js
299 ms
10402652_801908056500553_4367835908533789417_n.jpg
330 ms
safe_image.php
576 ms
safe_image.php
1248 ms
safe_image.php
1452 ms
safe_image.php
2673 ms
10313217_801895386501820_3736950921311903844_n.jpg
415 ms
12191589_1642524259348158_3554496569924372345_n.jpg
436 ms
12321390_1686231601652233_1169638033645527681_n.jpg
438 ms
11088397_815401491871411_2623537620106398546_n.jpg
441 ms
12794376_656635064474760_3443351575713005095_n.jpg
441 ms
11057496_797747090307316_1015820858122324638_n.jpg
446 ms
12189901_928192220592284_502995704269106498_n.jpg
487 ms
11130278_435764876583714_3109774326109607390_n.jpg
477 ms
734883_408707312542023_2133861599_n.jpg
533 ms
1497066_541795305980169_8476938119957528273_n.jpg
480 ms
12278925_1652503738366224_1368017406552149790_n.jpg
481 ms
12742842_526818704158903_9006149127517121354_n.jpg
566 ms
12646986_912657632137103_3549912386628584985_n.jpg
516 ms
524321_103623253119750_1369840498_n.jpg
521 ms
10336612_858788544187060_52748926885277522_n.jpg
700 ms
11205586_858794717519776_6335957393399324289_n.jpg
565 ms
11036038_858794757519772_5608831439566360278_n.jpg
589 ms
wL6VQj7Ab77.png
57 ms
s7jcwEQH7Sx.png
58 ms
QDwYpIaRyfG.png
57 ms
K00K-UgnsKu.png
57 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
79 ms
notdeadyet.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
notdeadyet.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
notdeadyet.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Notdeadyet.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Notdeadyet.jp 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.
notdeadyet.jp
Open Graph description is not detected on the main page of Notdeadyet. 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: