Tools & Wizards About Us
ja.chordwiki.org screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

ja.chordwiki.org

ChordWiki : コード譜共有サイト 〜無料の歌詞とコードをシェアしよう

Page Load Speed

5.6 sec in total

First Response

1.1 sec

Resources Loaded

4.3 sec

Page Rendered

187 ms

ja.chordwiki.org screenshot

About Website

Visit ja.chordwiki.org now to see the best up-to-date Ja Chord Wiki content for Japan and also check out these interesting facts you probably never knew about ja.chordwiki.org

歌詞付きのギターコード譜をWikiで共有するサイトです。J-POP、アニソン、VOCALOIDオリジナル等さまざまなジャンルの曲を多数掲載。弾き語りに便利なコードダイヤグラム表示・自動スクロール・移調機能あり。

Visit ja.chordwiki.org

Key Findings

We analyzed Ja.chordwiki.org page load time and found that the first response time was 1.1 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ja.chordwiki.org performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,990 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.218

57/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

ja.chordwiki.org

1076 ms

ja.chordwiki.org

747 ms

style.css

525 ms

pushnateWorker.js

1042 ms

adsbygoogle.js

33 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 15% of them (16 requests) were addressed to the original Ja.chordwiki.org, 11% (11 requests) were made to Apis.google.com and 8% (8 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source B.hatena.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.0 kB (33%)

Content Size

401.9 kB

After Optimization

270.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ja.chordwiki.org main page is 401.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. 65% of websites need less resources to load. Images take 170.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 53.1 kB

  • Original 71.0 kB
  • After minification 70.4 kB
  • After compression 17.9 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 53.1 kB or 75% of the original size.

Image Optimization

-15%

Potential reduce by 26.5 kB

  • Original 170.7 kB
  • After minification 144.3 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. Obviously, Ja Chord Wiki needs image optimization as it can save up to 26.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 30.1 kB

  • Original 132.3 kB
  • After minification 129.4 kB
  • After compression 102.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 30.1 kB or 23% of the original size.

CSS Optimization

-80%

Potential reduce by 22.3 kB

  • Original 27.9 kB
  • After minification 21.8 kB
  • After compression 5.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. Ja.chordwiki.org needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

97

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ja Chord Wiki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ja.chordwiki.org

ja.chordwiki.org

1076 ms

ja.chordwiki.org

ja.chordwiki.org

747 ms

style.css

style.css

525 ms

pushnateWorker.js

pushnateWorker.js

1042 ms

adsbygoogle.js

adsbygoogle.js

33 ms

count.js

count.js

557 ms

ChordWiki

ChordWiki

69 ms

ChordwikiNewEntries

ChordwikiNewEntries

85 ms

ChordWiki-notes

ChordWiki-notes

107 ms

ChordWikiBBS

ChordWikiBBS

108 ms

ChordWikiList

ChordWikiList

109 ms

ranking.js

ranking.js

557 ms

Chordwiki-setlist

Chordwiki-setlist

149 ms

Chordwiki-rated

Chordwiki-rated

110 ms

bookmark_button.js

bookmark_button.js

1277 ms

query_renderer.js

query_renderer.js

551 ms

search_keyword.js

search_keyword.js

556 ms

tagtrend.js

tagtrend.js

569 ms

analytics.js

analytics.js

57 ms

cse.js

cse.js

92 ms

collect

collect

14 ms

collect

collect

62 ms

jsapi

jsapi

41 ms

default+ja.css

default+ja.css

4 ms

default.css

default.css

19 ms

default+ja.I.js

default+ja.I.js

19 ms

default.css

default.css

31 ms

logo.jpg

logo.jpg

890 ms

addfriends_ja.png

addfriends_ja.png

1074 ms

button-only@2x.png

button-only@2x.png

493 ms

rss.png

rss.png

581 ms

mail.png

mail.png

625 ms

jasrac.png

jasrac.png

627 ms

mixiservicelogo.jpg

mixiservicelogo.jpg

627 ms

ca-pub-6362118305215071.js

ca-pub-6362118305215071.js

27 ms

zrt_lookup.html

zrt_lookup.html

38 ms

show_ads_impl.js

show_ads_impl.js

110 ms

buzzboost-pwrd.gif

buzzboost-pwrd.gif

116 ms

star_10_s.gif

star_10_s.gif

782 ms

star_2_s.gif

star_2_s.gif

1190 ms

star_8_s.gif

star_8_s.gif

1204 ms

widgets.js

widgets.js

170 ms

sdk.js

sdk.js

612 ms

plusone.js

plusone.js

162 ms

async-ads.js

async-ads.js

117 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

61 ms

small-logo.png

small-logo.png

37 ms

clear.gif

clear.gif

36 ms

pla

pla

26 ms

ads

ads

347 ms

osd.js

osd.js

41 ms

ads

ads

632 ms

ads

ads

620 ms

621 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

74 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

109 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

59 ms

fastbutton

fastbutton

119 ms

follow

follow

214 ms

postmessageRelay

postmessageRelay

128 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

103 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

103 ms

syndication

syndication

426 ms

344782481792327680

344782481792327680

631 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

91 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

81 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

453 ms

api.js

api.js

74 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

376 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

392 ms

rs=AGLTcCMMqqsIc6OcjXFVuYh2RauPSc-8kA

rs=AGLTcCMMqqsIc6OcjXFVuYh2RauPSc-8kA

54 ms

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

62 ms

rs=AGLTcCN05VjrlPNeensBYNDoaJhUsds2ZQ

rs=AGLTcCN05VjrlPNeensBYNDoaJhUsds2ZQ

106 ms

s_0Re36KCtSs_194689081.html

s_0Re36KCtSs_194689081.html

383 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

336 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

355 ms

m_js_controller.js

m_js_controller.js

209 ms

abg.js

abg.js

260 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

248 ms

270 ms

5171746271700867932

5171746271700867932

228 ms

xd_arbiter.php

xd_arbiter.php

552 ms

reset.css

reset.css

244 ms

entry-button.css

entry-button.css

337 ms

a.js;p=11177200956839;a=11177200932861;cache=7235426131211541

a.js;p=11177200956839;a=11177200932861;cache=7235426131211541

269 ms

creative_add_on.js

creative_add_on.js

368 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

88 ms

x_button_blue2.png

x_button_blue2.png

52 ms

s

s

79 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

125 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

124 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

5 ms

PAPlus_OliviaMunn_FSH_728x90.jpg

PAPlus_OliviaMunn_FSH_728x90.jpg

231 ms

adchoices.png

adchoices.png

248 ms

bbtn-l_v3.png

bbtn-l_v3.png

205 ms

LXlP1dBG_normal.jpg

LXlP1dBG_normal.jpg

101 ms

ChordWiki-logo-square-300_normal.jpg

ChordWiki-logo-square-300_normal.jpg

102 ms

l7aictZy_normal.jpg

l7aictZy_normal.jpg

102 ms

7LMqJf1C_normal.png

7LMqJf1C_normal.png

100 ms

4ScjxRiC_normal.jpeg

4ScjxRiC_normal.jpeg

100 ms

3dccbbcd-182e-4c1e-b693-527404be5ee7_normal.png

3dccbbcd-182e-4c1e-b693-527404be5ee7_normal.png

102 ms

dz-2tR0-_normal.jpg

dz-2tR0-_normal.jpg

102 ms

aXPA61Cv_normal.jpg

aXPA61Cv_normal.jpg

103 ms

Accessibility Review

ja.chordwiki.org accessibility score

89

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

Best Practices

ja.chordwiki.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ja.chordwiki.org SEO score

94

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Ja.chordwiki.org 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 Ja.chordwiki.org 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

ja.chordwiki.org

Open Graph data is detected on the main page of Ja Chord Wiki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: