Tools & Wizards About Us
discommunication.net screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

discommunication.net

黒生鉄心の奇妙な日常

Page Load Speed

30.6 sec in total

First Response

3.8 sec

Resources Loaded

25.3 sec

Page Rendered

1.5 sec

discommunication.net screenshot

About Website

Click here to check amazing Discommunication content for Japan. Otherwise, check out these important facts you probably never knew about discommunication.net

ゲームや漫画、あとはお酒などに関する雑記ブログです。

Visit discommunication.net

Key Findings

We analyzed Discommunication.net page load time and found that the first response time was 3.8 sec and then it took 26.8 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

discommunication.net performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

discommunication.net

3822 ms

discommunication.net

1305 ms

lastfm.css

327 ms

simple-amazon.css

346 ms

widget.css

350 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 28% of them (30 requests) were addressed to the original Discommunication.net, 13% (14 requests) were made to Apis.google.com and 6% (7 requests) were made to Calendar.google.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Fp.profiles.us.playstation.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.2 kB (18%)

Content Size

2.8 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Discommunication.net main page is 2.8 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 62.7 kB

  • Original 83.1 kB
  • After minification 80.7 kB
  • After compression 20.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 62.7 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 176.9 kB

  • Original 2.3 MB
  • After minification 2.1 MB

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. Discommunication images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 164.1 kB

  • Original 281.3 kB
  • After minification 270.4 kB
  • After compression 117.2 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 164.1 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 100.5 kB

  • Original 120.8 kB
  • After minification 95.3 kB
  • After compression 20.2 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. Discommunication.net needs all CSS files to be minified and compressed as it can save up to 100.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (62%)

Requests Now

102

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discommunication. 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 from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

discommunication.net

discommunication.net

3822 ms

discommunication.net

discommunication.net

1305 ms

lastfm.css

lastfm.css

327 ms

simple-amazon.css

simple-amazon.css

346 ms

widget.css

widget.css

350 ms

instapress.css

instapress.css

371 ms

jquery.fancybox.css

jquery.fancybox.css

454 ms

se-styles.css

se-styles.css

500 ms

screen.css

screen.css

541 ms

style.css

style.css

2114 ms

skin.css

skin.css

838 ms

rounded-corners.css

rounded-corners.css

633 ms

codecolorer.css

codecolorer.css

905 ms

jquery.js

jquery.js

1547 ms

jquery-migrate.min.js

jquery-migrate.min.js

871 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

1054 ms

sharebar.js

sharebar.js

1052 ms

suffusion.js

suffusion.js

1246 ms

external-tracking.min.js

external-tracking.min.js

1238 ms

rssmikle.js

rssmikle.js

21 ms

show_ads.js

show_ads.js

11 ms

widgets.js

widgets.js

108 ms

client-code.js

client-code.js

36 ms

rssmikle.js

rssmikle.js

18 ms

related.css

related.css

957 ms

instapress.js

instapress.js

1100 ms

front.js

front.js

1123 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

219 ms

ga.js

ga.js

76 ms

51oaVVGPs5L._SL160_.jpg

51oaVVGPs5L._SL160_.jpg

31 ms

23215198729_aa8e60b959_c.jpg

23215198729_aa8e60b959_c.jpg

552 ms

23215196209_e51938ea42_c.jpg

23215196209_e51938ea42_c.jpg

450 ms

tessin.kuronama_1362417629_23.jpg

tessin.kuronama_1362417629_23.jpg

390 ms

32x32.png

32x32.png

389 ms

kuronama2404.png

kuronama2404.png

19573 ms

99f8d609c37743c8c3335b803b75bac2.png

99f8d609c37743c8c3335b803b75bac2.png

380 ms

tfg.gif

tfg.gif

628 ms

search-button-gray-1.png

search-button-gray-1.png

264 ms

calgray-1.png

calgray-1.png

263 ms

logo_lastfm_crimson.png

logo_lastfm_crimson.png

263 ms

noart.gif

noart.gif

262 ms

517HSphL3EL._SL160_.jpg

517HSphL3EL._SL160_.jpg

68 ms

61YLaCSkuZL._SL160_.jpg

61YLaCSkuZL._SL160_.jpg

29 ms

61upHustmzL._SL160_.jpg

61upHustmzL._SL160_.jpg

67 ms

50df23a82f7d48a4bde3539c0b589065.png

50df23a82f7d48a4bde3539c0b589065.png

421 ms

23583138335_742f1b3688_c.jpg

23583138335_742f1b3688_c.jpg

657 ms

32x32.png

32x32.png

386 ms

32x32.png

32x32.png

384 ms

32x32.png

32x32.png

384 ms

32x32.png

32x32.png

385 ms

32x32.png

32x32.png

383 ms

1929 ms

ca-pub-6501483110788550.js

ca-pub-6501483110788550.js

259 ms

zrt_lookup.html

zrt_lookup.html

229 ms

show_ads_impl.js

show_ads_impl.js

251 ms

blockquote-l.png

blockquote-l.png

312 ms

__utm.gif

__utm.gif

110 ms

embedr-loader.js

embedr-loader.js

244 ms

embed

embed

223 ms

bulletgray.png

bulletgray.png

180 ms

border.png

border.png

232 ms

plusone.js

plusone.js

259 ms

152f0157.js

152f0157.js

884 ms

ads

ads

275 ms

osd.js

osd.js

57 ms

embed

embed

312 ms

embedr-5cfdc95dac01effa41001907e782e945.js

embedr-5cfdc95dac01effa41001907e782e945.js

226 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

98 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

95 ms

badge

badge

167 ms

postmessageRelay

postmessageRelay

83 ms

yql

yql

226 ms

02424c9533b4f8a9c4a1af88ac26fac3embedcompiled_fastui.css

02424c9533b4f8a9c4a1af88ac26fac3embedcompiled_fastui.css

25 ms

02424c9533b4f8a9c4a1af88ac26fac3embedcompiled__en.js

02424c9533b4f8a9c4a1af88ac26fac3embedcompiled__en.js

115 ms

client.js

client.js

1008 ms

rs=AGLTcCNVfC9sIDgoMYq-RsllZuxR65byLw

rs=AGLTcCNVfC9sIDgoMYq-RsllZuxR65byLw

41 ms

rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A

rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A

59 ms

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

137 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

207 ms

rpc:shindig_random.js

rpc:shindig_random.js

160 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

188 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

193 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

203 ms

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

37 ms

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw

26 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

tweet.00c2bb81d4f3f312a9a021c715a1c9dc.js

tweet.00c2bb81d4f3f312a9a021c715a1c9dc.js

167 ms

syndication

syndication

94 ms

tweets.json

tweets.json

113 ms

trackfeedbargreen.gif

trackfeedbargreen.gif

463 ms

tweet.f7130f11be9c2719286897ede16853b9.light.ltr.css

tweet.f7130f11be9c2719286897ede16853b9.light.ltr.css

31 ms

tweet.f7130f11be9c2719286897ede16853b9.light.ltr.css

tweet.f7130f11be9c2719286897ede16853b9.light.ltr.css

73 ms

3fee07c1efed93fe309e4b8de811f331_normal.png

3fee07c1efed93fe309e4b8de811f331_normal.png

282 ms

CS97znqUEAAUimP.png

CS97znqUEAAUimP.png

1215 ms

CS9-QoTVEAARjCw.png

CS9-QoTVEAARjCw.png

997 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

postmessageRelay

postmessageRelay

28 ms

logo-plus.png

logo-plus.png

42 ms

googlelogo_color_46x16dp.png

googlelogo_color_46x16dp.png

65 ms

proxy.html

proxy.html

52 ms

blank.gif

blank.gif

24 ms

menu_arrow_open.gif

menu_arrow_open.gif

23 ms

combined_v22.png

combined_v22.png

30 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

jquery.min.js

jquery.min.js

107 ms

events

events

259 ms

jot.html

jot.html

160 ms

analytics.js

analytics.js

120 ms

collect

collect

42 ms

Accessibility Review

discommunication.net accessibility score

77

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

discommunication.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

discommunication.net SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discommunication.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Discommunication.net 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.

Social Sharing Optimization

discommunication.net

Open Graph description is not detected on the main page of Discommunication. 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: