Tools & Wizards About Us
ikanji.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ikanji.jp

Japanese Kanji Dictionary｜An introduction to the visual classification and the number of strokes, radical by Japanese kanji list of 6,400 or more char...

Page Load Speed

5.4 sec in total

First Response

534 ms

Resources Loaded

4.7 sec

Page Rendered

145 ms

ikanji.jp screenshot

About Website

Click here to check amazing I Kanji content for Russia. Otherwise, check out these important facts you probably never knew about ikanji.jp

An introduction to the visual classification and the number of strokes, radical by Japanese kanji list of 6,400 or more characters

Visit ikanji.jp

Key Findings

We analyzed Ikanji.jp page load time and found that the first response time was 534 ms and then it took 4.8 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

ikanji.jp performance score

0

Network Requests Diagram

ikanji.jp

534 ms

en.ikanji.jp

463 ms

en.ikanji.jp

772 ms

default.css

150 ms

yuga.js

297 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ikanji.jp, 59% (33 requests) were made to En.ikanji.jp and 11% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source En.ikanji.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.7 kB (36%)

Content Size

781.3 kB

After Optimization

502.6 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-84%

Potential reduce by 135.7 kB

  • Original 160.8 kB
  • After minification 150.8 kB
  • After compression 25.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 135.7 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 15 B

  • Original 1.2 kB
  • After minification 1.1 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. I Kanji images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 142.9 kB

  • Original 619.3 kB
  • After minification 619.3 kB
  • After compression 476.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 142.9 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (57%)

Requests Now

53

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ikanji.jp

ikanji.jp

534 ms

en.ikanji.jp

en.ikanji.jp

463 ms

en.ikanji.jp

en.ikanji.jp

772 ms

default.css

default.css

150 ms

yuga.js

yuga.js

297 ms

common.js

common.js

438 ms

jquery.js

jquery.js

876 ms

modernizr-transitions.js

modernizr-transitions.js

437 ms

jquery.masonry.min.js

jquery.masonry.min.js

448 ms

jquery-ui.js

jquery-ui.js

1176 ms

jquery.tinyscrollbar.min.js

jquery.tinyscrollbar.min.js

453 ms

masonry.css

masonry.css

586 ms

jquery.cookie.js

jquery.cookie.js

586 ms

top.css

top.css

597 ms

adsbygoogle.js

adsbygoogle.js

47 ms

jquery.pageslide.min.js

jquery.pageslide.min.js

598 ms

common.css

common.css

588 ms

form.css

form.css

588 ms

layout.css

layout.css

601 ms

contents.css

contents.css

606 ms

table.css

table.css

738 ms

list.css

list.css

738 ms

analytics.js

analytics.js

13 ms

collect

collect

12 ms

js

js

58 ms

012.jpg

012.jpg

576 ms

bg_loading.gif

bg_loading.gif

162 ms

bg_header.png

bg_header.png

602 ms

logo.png

logo.png

188 ms

icon_search.png

icon_search.png

161 ms

bg_subNavi.png

bg_subNavi.png

187 ms

icon_arrow03_wh2.gif

icon_arrow03_wh2.gif

306 ms

bg_sideTab.png

bg_sideTab.png

439 ms

001.png

001.png

757 ms

btn_more.png

btn_more.png

315 ms

show_ads_impl.js

show_ads_impl.js

75 ms

bg_goTop.gif

bg_goTop.gif

414 ms

collect

collect

62 ms

bg_dot_side.gif

bg_dot_side.gif

359 ms

zrt_lookup.html

zrt_lookup.html

43 ms

ads

ads

301 ms

ads

ads

413 ms

001.png

001.png

687 ms

reactive_library.js

reactive_library.js

48 ms

ca-pub-7993682101835904

ca-pub-7993682101835904

72 ms

load_preloaded_resource.js

load_preloaded_resource.js

41 ms

icon.png

icon.png

8 ms

abg_lite.js

abg_lite.js

41 ms

window_focus.js

window_focus.js

120 ms

qs_click_protection.js

qs_click_protection.js

45 ms

ufs_web_display.js

ufs_web_display.js

24 ms

d4128ee657a8b8f36370500b7756be30.js

d4128ee657a8b8f36370500b7756be30.js

40 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

116 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

116 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

33 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

112 ms

SEO Factors

ikanji.jp SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ikanji.jp 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 Ikanji.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

ikanji.jp

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