7.2 sec in total
1.5 sec
5.1 sec
538 ms
Welcome to kanone.biz homepage info - get ready to check Kanone best content for Japan right away, or after learning these important things about kanone.biz
Visit kanone.bizWe analyzed Kanone.biz page load time and found that the first response time was 1.5 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kanone.biz performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.6 s
60/100
25%
Value3.2 s
91/100
10%
Value90 ms
99/100
30%
Value0.032
100/100
15%
Value4.0 s
88/100
10%
1523 ms
434 ms
295 ms
467 ms
553 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 59% of them (85 requests) were addressed to the original Kanone.biz, 10% (14 requests) were made to Pbs.twimg.com and 6% (8 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kanone.biz.
Page size can be reduced by 295.8 kB (12%)
2.6 MB
2.3 MB
In fact, the total size of Kanone.biz main page is 2.6 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. 75% 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. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 107.6 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 107.6 kB or 84% of the original size.
Potential reduce by 22.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. Kanone images are well optimized though.
Potential reduce by 157.7 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 157.7 kB or 68% of the original size.
Potential reduce by 8.0 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. Kanone.biz needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 75% of the original size.
Number of requests can be reduced by 39 (28%)
139
100
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
kanone.biz
1523 ms
jquery-2.1.1.min.js
434 ms
jquery.simpleTicker.js
295 ms
bootstrap.css
467 ms
bootstrap.js
553 ms
xsrf-token.js
373 ms
main.css
374 ms
csshake.min.css
449 ms
main.js
568 ms
jquery.timeago.js
570 ms
platform.js
64 ms
bookmark_button.js
815 ms
analytics.js
15 ms
button-only@2x.png
389 ms
pc_back.jpg
238 ms
wall.png
365 ms
pc_head.jpg
514 ms
solo.png
237 ms
121134.png
309 ms
122305.jpg
238 ms
0041.jpg
361 ms
122345.jpg
399 ms
123230.png
595 ms
0036.jpg
1195 ms
120205.jpg
515 ms
120068.jpg
549 ms
119463.png
958 ms
124085.jpg
661 ms
123464.jpg
660 ms
123983.jpg
757 ms
121713.jpg
804 ms
123391.jpg
806 ms
122906.jpg
814 ms
favicon.ico
1302 ms
qr.gif
963 ms
fb.png
955 ms
twitter.png
969 ms
crown_1.png
1103 ms
124214.jpg
1139 ms
hatena.png
1145 ms
124357.jpg
1124 ms
124330.jpg
1249 ms
124470.jpg
1280 ms
124191.jpg
1321 ms
124507.jpg
1326 ms
124502.jpg
1341 ms
124501.jpg
1399 ms
0002.jpg
1436 ms
124503.jpg
1484 ms
124505.jpg
1497 ms
btn.js
74 ms
cb=gapi.loaded_0
23 ms
cb=gapi.loaded_1
52 ms
fastbutton
188 ms
collect
55 ms
collect
53 ms
widgets.js
203 ms
sdk.js
14 ms
postmessageRelay
200 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
33 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
60 ms
button
47 ms
glyphicons-halflings-regular.woff
1273 ms
124509.jpg
1253 ms
share_button.php
271 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
146 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
173 ms
396 ms
xd_arbiter.php
28 ms
xd_arbiter.php
64 ms
395 ms
button.css
55 ms
shared.js
57 ms
button.js
60 ms
3193398744-postmessagerelay.js
36 ms
rpc:shindig_random.js
32 ms
124508.jpg
1305 ms
cb=gapi.loaded_0
12 ms
pocket_button.png
13 ms
0012.jpg
1855 ms
124493.jpg
1274 ms
124494.jpg
1290 ms
syndication
95 ms
695894873296089089
195 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
51 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
84 ms
info.json
115 ms
qeKvIRsJabD.js
42 ms
LVx-xkvaJ0b.png
81 ms
124484.jpg
1177 ms
124481.jpg
1236 ms
124482.jpg
1237 ms
124489.png
1457 ms
reset.css
10 ms
entry-button.css
10 ms
124487.jpg
1212 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
43 ms
124488.jpg
1228 ms
bbtn-l_v3.png
3 ms
cwCgr-Cj_normal.jpg
138 ms
VOafbJgb_normal.jpg
151 ms
B4jwEVFT_normal.jpg
163 ms
8HOCIIG9_normal.jpg
171 ms
T2dwGpKw_normal.jpg
163 ms
S02CXDJb_normal.jpg
168 ms
kUuGTo5j_normal.jpg
161 ms
KNhQSVJ3_normal.jpg
176 ms
nP-awWhO_normal.jpg
187 ms
CTZxCKMWUAEBaBO.jpg:small
188 ms
CTZw0FlWwAAEF_w.jpg:small
190 ms
CTZOslxWEAASLYS.jpg:small
191 ms
CTZNzp7WcAATKK-.jpg:small
192 ms
CTZNzNOWUAEBbe9.jpg:small
252 ms
124472.jpg
1149 ms
124479.jpg
1128 ms
124477.jpg
1249 ms
124473.jpg
1223 ms
124456.jpg
1103 ms
124466.jpg
1121 ms
124453.png
1367 ms
124452.jpg
1264 ms
jot.html
28 ms
124462.jpg
1136 ms
124451.png
1244 ms
0015.jpg
1234 ms
0015.png
1252 ms
0010.jpg
1222 ms
0010.png
1169 ms
0013.jpg
1342 ms
0013.png
1219 ms
0037.jpg
1199 ms
0037.png
1254 ms
0004.jpg
1800 ms
0004.png
1200 ms
0022.jpg
1376 ms
0021.jpg
1657 ms
0021.png
1276 ms
0036.png
1279 ms
0012.png
1245 ms
0028.jpg
1335 ms
0028.png
1283 ms
kanone.biz 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.
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
<frame> or <iframe> elements do not have a title
kanone.biz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
kanone.biz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanone.biz 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Kanone.biz 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.
kanone.biz
Open Graph description is not detected on the main page of Kanone. 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: