Tools & Wizards About Us
kanji.org screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

kanji.org

Kanji Dictionary Publishing Society - Kanji dictionaries for learning Japanese

Page Load Speed

2.9 sec in total

First Response

550 ms

Resources Loaded

2 sec

Page Rendered

284 ms

kanji.org screenshot

About Website

Welcome to kanji.org homepage info - get ready to check Kanji best content right away, or after learning these important things about kanji.org

Kanji and Japanese dictionary for learning kanji and Japanese, especially the New Japanese-English Character Dictionary for learning Japanese and kanji effectively and The Kodansha Kanji Learner's Dic...

Visit kanji.org

Key Findings

We analyzed Kanji.org page load time and found that the first response time was 550 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

kanji.org performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

kanji.org

550 ms

yellow_s.gif

336 ms

kanjijiten.gif

337 ms

kdpsjap.gif

347 ms

japanese.gif

348 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 74% of them (14 requests) were addressed to the original Kanji.org, 11% (2 requests) were made to Cjk.org and 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Kanji.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.6 kB (43%)

Content Size

277.5 kB

After Optimization

157.9 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-76%

Potential reduce by 16.4 kB

  • Original 21.6 kB
  • After minification 18.0 kB
  • After compression 5.2 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.7 kB, which is 17% 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 16.4 kB or 76% of the original size.

Image Optimization

-43%

Potential reduce by 103.1 kB

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

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • Images
  • JavaScript

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanji. According to our analytics all requests are already optimized.

Network Requests Diagram

kanji.org

kanji.org

550 ms

yellow_s.gif

yellow_s.gif

336 ms

kanjijiten.gif

kanjijiten.gif

337 ms

kdpsjap.gif

kdpsjap.gif

347 ms

japanese.gif

japanese.gif

348 ms

exptextb.jpg

exptextb.jpg

355 ms

KKLD_cover_250.jpg

KKLD_cover_250.jpg

660 ms

KKD_cover_250.jpg

KKD_cover_250.jpg

670 ms

usagecover_vert239.jpg

usagecover_vert239.jpg

850 ms

kanji_synonyms_small.jpg

kanji_synonyms_small.jpg

1031 ms

ikkld_140.png

ikkld_140.png

693 ms

kug_140x140.png

kug_140x140.png

851 ms

synonyms_140x140.png

synonyms_140x140.png

1176 ms

instant_icon_140x140.png

instant_icon_140x140.png

1185 ms

jackdoar.gif

jackdoar.gif

381 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

12 ms

jackdoar.gif

jackdoar.gif

678 ms

jackdoar.gif

jackdoar.gif

418 ms

Accessibility Review

kanji.org accessibility score

57

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

kanji.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

kanji.org SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanji.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kanji.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

kanji.org

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