Tools & Wizards About Us
kingdom.konjiki.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

kingdom.konjiki.jp

KINGDOM-ゲーム攻略・交流・PSP活用サイト-

Page Load Speed

10 sec in total

First Response

577 ms

Resources Loaded

9.2 sec

Page Rendered

234 ms

kingdom.konjiki.jp screenshot

About Website

Welcome to kingdom.konjiki.jp homepage info - get ready to check KINGDOM Konjiki best content for Japan right away, or after learning these important things about kingdom.konjiki.jp

ゲーム攻略、PSP改造解説等のコンテンツを揃えています。

Visit kingdom.konjiki.jp

Key Findings

We analyzed Kingdom.konjiki.jp page load time and found that the first response time was 577 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

kingdom.konjiki.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

3/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

kingdom.konjiki.jp

577 ms

body.txt

343 ms

commercial.css

320 ms

encount

350 ms

fire

352 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Kingdom.konjiki.jp, 12% (22 requests) were made to Asumi.shinobi.jp and 5% (9 requests) were made to Ecx.images-amazon.com. The less responsive or slowest element that took the longest time to load (615 ms) relates to the external source Ad.ad-arata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.3 kB (45%)

Content Size

373.1 kB

After Optimization

203.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kingdom.konjiki.jp main page is 373.1 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. 40% of websites need less resources to load. Javascripts take 270.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 26.1 kB

  • Original 36.4 kB
  • After minification 32.5 kB
  • After compression 10.3 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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 26.1 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 341 B

  • Original 60.3 kB
  • After minification 60.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. KINGDOM Konjiki images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 137.8 kB

  • Original 270.2 kB
  • After minification 267.2 kB
  • After compression 132.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 137.8 kB or 51% of the original size.

CSS Optimization

-83%

Potential reduce by 5.1 kB

  • Original 6.2 kB
  • After minification 4.4 kB
  • After compression 1.1 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. Kingdom.konjiki.jp needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 133 (80%)

Requests Now

166

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kingdom.konjiki.jp

kingdom.konjiki.jp

577 ms

body.txt

body.txt

343 ms

commercial.css

commercial.css

320 ms

encount

encount

350 ms

fire

fire

352 ms

0534044

0534044

567 ms

show_ads.js

show_ads.js

4 ms

default.js

default.js

549 ms

fire

fire

350 ms

fire

fire

363 ms

shiro_haikei.gif

shiro_haikei.gif

373 ms

1.13.17

1.13.17

313 ms

track

track

183 ms

ajs.php

ajs.php

26 ms

track

track

176 ms

track

track

174 ms

lg.php

lg.php

20 ms

track

track

175 ms

track

track

317 ms

track

track

320 ms

track

track

330 ms

0534044

0534044

571 ms

compass.js

compass.js

10 ms

match.aspx

match.aspx

20 ms

cookie_enabled_get_apac.html

cookie_enabled_get_apac.html

375 ms

sync

sync

175 ms

ad

ad

588 ms

trac.js

trac.js

160 ms

0534044

0534044

385 ms

ca-pub-0124296284532576.js

ca-pub-0124296284532576.js

132 ms

zrt_lookup.html

zrt_lookup.html

33 ms

show_ads_impl.js

show_ads_impl.js

62 ms

table_haikei.JPG

table_haikei.JPG

394 ms

mf_post.js

mf_post.js

348 ms

0_plain.css

0_plain.css

366 ms

cm

cm

176 ms

cm

cm

190 ms

ads

ads

25 ms

osd.js

osd.js

8 ms

140x25-b-amzn.gif

140x25-b-amzn.gif

22 ms

161 ms

61degefmFqL._SL60_.jpg

61degefmFqL._SL60_.jpg

18 ms

61KW2S0idPL._SL60_.jpg

61KW2S0idPL._SL60_.jpg

19 ms

61pAN5H7gUL._SL60_.jpg

61pAN5H7gUL._SL60_.jpg

21 ms

41FXZeRlZyL._SL60_.jpg

41FXZeRlZyL._SL60_.jpg

17 ms

61Om0kFnuEL._SL60_.jpg

61Om0kFnuEL._SL60_.jpg

19 ms

41ZoWC0a2KL._SL60_.jpg

41ZoWC0a2KL._SL60_.jpg

19 ms

160 ms

ap-search-go-btn.gif

ap-search-go-btn.gif

12 ms

searchbox-logo-126x32.gif

searchbox-logo-126x32.gif

11 ms

cookiesync

cookiesync

370 ms

track

track

183 ms

ajs.php

ajs.php

21 ms

track

track

176 ms

lg.php

lg.php

17 ms

match.aspx

match.aspx

15 ms

track

track

174 ms

track

track

175 ms

track

track

176 ms

116bb2c944a522f53ddfb96064b197d6

116bb2c944a522f53ddfb96064b197d6

368 ms

ic

ic

334 ms

ADTECH;cfp=1;rndc=1458236112;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1458236112578

ADTECH;cfp=1;rndc=1458236112;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1458236112578

349 ms

1.0.1.js

1.0.1.js

157 ms

track

track

183 ms

ads.js

ads.js

36 ms

sync

sync

9 ms

pixel

pixel

18 ms

generic

generic

11 ms

track

track

177 ms

track

track

174 ms

mapuser

mapuser

294 ms

mapuser

mapuser

293 ms

generic

generic

5 ms

mapuser

mapuser

613 ms

mapuser

mapuser

300 ms

mapuser

mapuser

296 ms

adcomp_pc.js

adcomp_pc.js

19 ms

sspcore_spot.js

sspcore_spot.js

50 ms

mapuser

mapuser

416 ms

ssp_spot.ashx

ssp_spot.ashx

294 ms

1.0.0.js

1.0.0.js

157 ms

0.gif

0.gif

162 ms

mapuser

mapuser

5 ms

adcore.js

adcore.js

19 ms

adcore_pc.js

adcore_pc.js

34 ms

sync

sync

201 ms

adcore_pc_inline.js

adcore_pc_inline.js

19 ms

ad_spot.aspx

ad_spot.aspx

317 ms

usermatch

usermatch

20 ms

pixel.htm

pixel.htm

44 ms

al.gif

al.gif

177 ms

pr.gif

pr.gif

332 ms

link.gif

link.gif

338 ms

track

track

186 ms

embed.js

embed.js

615 ms

track

track

178 ms

usermatch

usermatch

24 ms

casale

casale

16 ms

pixel

pixel

21 ms

gr

gr

20 ms

Vurq0cAoJZQAACPFXtsAAAE3%26969

Vurq0cAoJZQAACPFXtsAAAE3%26969

53 ms

blank.html

blank.html

14 ms

mapuser

mapuser

152 ms

ddc.htm

ddc.htm

35 ms

crum

crum

40 ms

rum

rum

39 ms

rum

rum

37 ms

pixel

pixel

73 ms

crum

crum

47 ms

Pug

Pug

48 ms

rtset

rtset

48 ms

u.php

u.php

118 ms

91 ms

mapuser

mapuser

27 ms

um

um

205 ms

pixel

pixel

19 ms

rum

rum

19 ms

pixel.htm

pixel.htm

32 ms

cs

cs

28 ms

tap.php

tap.php

12 ms

merge

merge

13 ms

sd

sd

10 ms

bd

bd

65 ms

xrefid.xgi

xrefid.xgi

9 ms

bd

bd

62 ms

crum

crum

72 ms

ddc.htm

ddc.htm

36 ms

m

m

70 ms

116bb2c944a522f53ddfb96064b197d6

116bb2c944a522f53ddfb96064b197d6

198 ms

rum

rum

48 ms

lr.gif

lr.gif

20 ms

sync

sync

373 ms

sync

sync

334 ms

push_sync

push_sync

303 ms

sync

sync

120 ms

pixel.gif

pixel.gif

65 ms

crum

crum

10 ms

NAX8118499038005118003

NAX8118499038005118003

35 ms

style.css

style.css

155 ms

ad_creative.ashx

ad_creative.ashx

67 ms

js1

js1

339 ms

ib

ib

186 ms

sync

sync

192 ms

1.1.0.js

1.1.0.js

156 ms

cookiesync

cookiesync

323 ms

js

js

495 ms

receive_sync

receive_sync

153 ms

mapuser

mapuser

149 ms

delivery

delivery

156 ms

jstag

jstag

10 ms

acj

acj

16 ms

ri

ri

6 ms

imp

imp

195 ms

a1033892.js

a1033892.js

363 ms

sync

sync

10 ms

jsk

jsk

376 ms

js1

js1

339 ms

push_sync

push_sync

153 ms

pixel

pixel

17 ms

sync

sync

5 ms

gl0

gl0

184 ms

sync

sync

191 ms

acs

acs

190 ms

js

js

521 ms

acs

acs

343 ms

306 ms

cs

cs

163 ms

cs

cs

167 ms

cs

cs

188 ms

acs

acs

181 ms

cs

cs

171 ms

yads.js

yads.js

517 ms

gcs

gcs

380 ms

yads_vimps-1.4.1.js

yads_vimps-1.4.1.js

486 ms

tag

tag

577 ms

gcs

gcs

381 ms

gcs

gcs

353 ms

f5134b98d8a0db7051110c23094cfb90

f5134b98d8a0db7051110c23094cfb90

24 ms

yads-iframe.html

yads-iframe.html

163 ms

tag

tag

333 ms

oi

oi

401 ms

RestoreXidToMediaStorage.html

RestoreXidToMediaStorage.html

36 ms

bd

bd

33 ms

Accessibility Review

kingdom.konjiki.jp accessibility score

73

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

kingdom.konjiki.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kingdom.konjiki.jp SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kingdom.konjiki.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kingdom.konjiki.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.

Social Sharing Optimization

kingdom.konjiki.jp

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