Tools & Wizards About Us
ru.ikanji.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

ru.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

8 sec in total

First Response

1.8 sec

Resources Loaded

6 sec

Page Rendered

144 ms

ru.ikanji.jp screenshot

About Website

Welcome to ru.ikanji.jp homepage info - get ready to check Ru I Kanji best content for Russia right away, or after learning these important things about ru.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 ru.ikanji.jp

Key Findings

We analyzed Ru.ikanji.jp page load time and found that the first response time was 1.8 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ru.ikanji.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

en.ikanji.jp

1795 ms

default.css

342 ms

yuga.js

345 ms

common.js

371 ms

jquery.js

524 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ru.ikanji.jp, 11% (7 requests) were made to Tpc.googlesyndication.com and 8% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source En.ikanji.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 697.8 kB (58%)

Content Size

1.2 MB

After Optimization

506.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ru.ikanji.jp main page is 1.2 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. 50% of websites need less resources to load. Images take 745.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 153.8 kB

  • Original 179.7 kB
  • After minification 169.7 kB
  • After compression 25.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 153.8 kB or 86% of the original size.

Image Optimization

-67%

Potential reduce by 496.0 kB

  • Original 745.7 kB
  • After minification 249.7 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, Ru I Kanji needs image optimization as it can save up to 496.0 kB or 67% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 43.4 kB

  • Original 262.3 kB
  • After minification 262.2 kB
  • After compression 218.9 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 43.4 kB or 17% of the original size.

CSS Optimization

-27%

Potential reduce by 4.6 kB

  • Original 16.7 kB
  • After minification 16.7 kB
  • After compression 12.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. Ru.ikanji.jp needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 27% of the original size.

Requests Breakdown

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

Requests Now

60

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.ikanji.jp

en.ikanji.jp

1795 ms

default.css

default.css

342 ms

yuga.js

yuga.js

345 ms

common.js

common.js

371 ms

jquery.js

jquery.js

524 ms

modernizr-transitions.js

modernizr-transitions.js

370 ms

jquery.masonry.min.js

jquery.masonry.min.js

370 ms

jquery-ui.js

jquery-ui.js

1212 ms

jquery.tinyscrollbar.min.js

jquery.tinyscrollbar.min.js

506 ms

masonry.css

masonry.css

515 ms

jquery.cookie.js

jquery.cookie.js

513 ms

top.css

top.css

552 ms

adsbygoogle.js

adsbygoogle.js

28 ms

jquery.pageslide.min.js

jquery.pageslide.min.js

517 ms

common.css

common.css

348 ms

form.css

form.css

365 ms

layout.css

layout.css

376 ms

contents.css

contents.css

412 ms

table.css

table.css

511 ms

list.css

list.css

520 ms

analytics.js

analytics.js

22 ms

collect

collect

94 ms

013.jpg

013.jpg

569 ms

bg_loading.gif

bg_loading.gif

363 ms

bg_header.png

bg_header.png

913 ms

logo.png

logo.png

363 ms

icon_search.png

icon_search.png

362 ms

bg_subNavi.png

bg_subNavi.png

361 ms

icon_arrow03_wh2.gif

icon_arrow03_wh2.gif

528 ms

bg_sideTab.png

bg_sideTab.png

689 ms

001.png

001.png

2361 ms

btn_more.png

btn_more.png

525 ms

zrt_lookup.html

zrt_lookup.html

242 ms

show_ads_impl.js

show_ads_impl.js

299 ms

bg_goTop.gif

bg_goTop.gif

577 ms

collect

collect

204 ms

bg_dot_side.gif

bg_dot_side.gif

357 ms

cookie.js

cookie.js

79 ms

integrator.js

integrator.js

90 ms

ads

ads

356 ms

ads

ads

624 ms

reactive_library.js

reactive_library.js

34 ms

integrator.js

integrator.js

34 ms

zrt_lookup.html

zrt_lookup.html

26 ms

css2

css2

64 ms

8840195105786152108

8840195105786152108

147 ms

load_preloaded_resource.js

load_preloaded_resource.js

59 ms

abg_lite.js

abg_lite.js

57 ms

window_focus.js

window_focus.js

72 ms

qs_click_protection.js

qs_click_protection.js

65 ms

rx_lidar.js

rx_lidar.js

79 ms

042791247ab671b2831aa311d6583330.js

042791247ab671b2831aa311d6583330.js

64 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

57 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

67 ms

icon.png

icon.png

19 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

66 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

71 ms

redir.html

redir.html

37 ms

css

css

16 ms

font

font

13 ms

font

font

15 ms

iframe.html

iframe.html

80 ms

b4aq_x9zMiku-4ayY0gQrcEuJNMSghrM2Nuaea2nyAg.js

b4aq_x9zMiku-4ayY0gQrcEuJNMSghrM2Nuaea2nyAg.js

3 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

6 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

12 ms

Accessibility Review

ru.ikanji.jp accessibility score

82

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

ru.ikanji.jp best practices score

67

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

Browser errors were logged to the console

SEO Factors

ru.ikanji.jp SEO score

67

Search Engine Optimization Advices

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 Ru.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 Ru.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

ru.ikanji.jp

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