3.9 sec in total
464 ms
2.8 sec
642 ms
Welcome to kana.cm homepage info - get ready to check Kana best content for Japan right away, or after learning these important things about kana.cm
See related links to what you are looking for.
Visit kana.cmWe analyzed Kana.cm page load time and found that the first response time was 464 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
kana.cm performance score
464 ms
36 ms
207 ms
24 ms
28 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kana.cm, 17% (15 requests) were made to Static.fc2.com and 9% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (491 ms) relates to the external source 17730849.ranking.fc2.com.
Page size can be reduced by 611.4 kB (53%)
1.2 MB
538.8 kB
In fact, the total size of Kana.cm 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 477.3 kB which makes up the majority of the site volume.
Potential reduce by 83.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. This page needs HTML code to be minified as it can gain 13.6 kB, which is 14% 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 83.9 kB or 87% of the original size.
Potential reduce by 25.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. Kana images are well optimized though.
Potential reduce by 283.0 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 283.0 kB or 59% of the original size.
Potential reduce by 218.8 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. Kana.cm needs all CSS files to be minified and compressed as it can save up to 218.8 kB or 83% of the original size.
Number of requests can be reduced by 48 (58%)
83
35
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kana. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
kana.cm
464 ms
dc6b1.css
36 ms
analyze.js
207 ms
adsbygoogle.js
24 ms
jsapi
28 ms
t13n
41 ms
widgets.js
90 ms
q
22 ms
accessory.js
491 ms
accessory.js
491 ms
anak08-22_3f6cd7d8-eb06-4033-9795-e6269dcacb42.js
190 ms
20150916210657227.jpg
69 ms
20150914154421740.jpg
464 ms
20150914151620652s.jpg
465 ms
20150913080818002s.jpg
463 ms
20150913073205474.jpg
71 ms
20150913071906113.jpg
78 ms
20150906233701607.jpg
90 ms
t13n
63 ms
cm
264 ms
ca-pub-4840616509814237.js
43 ms
zrt_lookup.html
50 ms
show_ads_impl.js
95 ms
22 ms
transliteration.css
14 ms
transliteration.I.js
16 ms
100 ms
ads
224 ms
11.gif
48 ms
osd.js
38 ms
cover-selection-assoc-a-JP-728x90.jpg
42 ms
260 ms
inputtools.js
28 ms
4.gif
14 ms
like.php
175 ms
6.gif
62 ms
like.php
221 ms
2.gif
45 ms
like.php
144 ms
like.php
143 ms
abg.js
51 ms
8.gif
49 ms
wy1X4hBW7e7.js
219 ms
LVx-xkvaJ0b.png
227 ms
like.php
115 ms
like.php
116 ms
ads
227 ms
videoseries
112 ms
like.php
78 ms
q
319 ms
json
308 ms
rank1.gif
20 ms
counter.php
279 ms
rank2.gif
22 ms
rank3.gif
17 ms
rank4.gif
21 ms
rank5.gif
31 ms
rank6.gif
20 ms
rank7.gif
21 ms
rank8.gif
21 ms
rank9.gif
37 ms
rank10.gif
37 ms
www-embed-player-vflfNyN_r.css
27 ms
www-embed-player.js
48 ms
base.js
104 ms
000000_new_ico.gif
121 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
43 ms
ad_status.js
87 ms
counter_js.php
85 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
71 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
71 ms
q
419 ms
q
417 ms
q
419 ms
q
428 ms
counter_js.php
80 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
128 ms
css
29 ms
aps-adserving.min.js
18 ms
search-widget-sprite.png
171 ms
loader._V1391506999_.gif
53 ms
ps-spr-1-mobile-jp.png
17 ms
aps-base.min.css
15 ms
ps-spr-2-mobile-jp.png
15 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
46 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
101 ms
930913056.json
333 ms
jot.html
32 ms
kana.cm SEO score
N/A
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kana.cm can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Kana.cm main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
kana.cm
Open Graph description is not detected on the main page of Kana. 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: