3.4 sec in total
685 ms
2.4 sec
272 ms
Click here to check amazing Kanja content for Japan. Otherwise, check out these important facts you probably never knew about kanja.jp
病院検索・歯科医院検索でいいお医者さん、良い歯医者さんを見つけられます。気軽に症状等の医療相談ができるお医者さん・歯医者さんを見つけましょう
Visit kanja.jpWe analyzed Kanja.jp page load time and found that the first response time was 685 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
kanja.jp performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.1 s
12/100
25%
Value8.3 s
19/100
10%
Value230 ms
86/100
30%
Value0.586
11/100
15%
Value5.9 s
66/100
10%
685 ms
294 ms
587 ms
616 ms
346 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Kanja.jp, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Kanja.jp.
Page size can be reduced by 197.5 kB (51%)
390.1 kB
192.6 kB
In fact, the total size of Kanja.jp main page is 390.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. 25% of websites need less resources to load. Images take 168.6 kB which makes up the majority of the site volume.
Potential reduce by 23.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. 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 23.3 kB or 75% of the original size.
Potential reduce by 40.8 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, Kanja needs image optimization as it can save up to 40.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 67.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 67.9 kB or 60% of the original size.
Potential reduce by 65.5 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. Kanja.jp needs all CSS files to be minified and compressed as it can save up to 65.5 kB or 85% of the original size.
Number of requests can be reduced by 19 (39%)
49
30
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanja. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
kanja.jp
685 ms
import.css
294 ms
style.css
587 ms
jquery.js
616 ms
jquery.flatheights.js
346 ms
common.js
363 ms
jquery.jqtransform.js
366 ms
flatHeights.js
439 ms
cmn_reset.css
253 ms
cmn_layout.css
257 ms
cmn_style.css
440 ms
jqtransform.css
404 ms
bg_top_head.jpg
169 ms
bg_top_headLogo.jpg
300 ms
logo_top.jpg
175 ms
btn_head_smartphone.gif
191 ms
btn_head_search.gif
167 ms
tit_search_pref.jpg
186 ms
tit_search_area.jpg
299 ms
img_topMap.gif
318 ms
tit_search_kamoku.jpg
348 ms
tit_search_kamoku2nd1.gif
368 ms
bg_menu.gif
371 ms
tit_whatsnew.jpg
444 ms
noimage.jpg
447 ms
020884-log.jpg
473 ms
020766-log.jpg
519 ms
021055-log.jpg
550 ms
021093-log.jpg
552 ms
021085-log.jpg
592 ms
021058-log.jpg
594 ms
tit_onepoint.jpg
630 ms
002296-dir.jpg
692 ms
bg_btn_arrow.gif
732 ms
tit_menu.jpg
733 ms
tit_mobile.jpg
737 ms
img_qr_s_temp.jpg
740 ms
img_qr_m_temp.jpg
786 ms
tit_kyujin.jpg
864 ms
tit_login.jpg
913 ms
bg_btn_arrow2.gif
915 ms
ban_mediconavi.jpg
885 ms
ban_shikayoyakucom.jpg
887 ms
btn_footer_pagetop.gif
940 ms
bg_footer.jpg
1037 ms
line_separeter2.gif
1031 ms
ga.js
40 ms
input_text_left.gif
921 ms
input_text_right.gif
982 ms
__utm.gif
13 ms
kanja.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kanja.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
kanja.jp SEO score
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanja.jp 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 Kanja.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.
kanja.jp
Open Graph description is not detected on the main page of Kanja. 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: