11.7 sec in total
744 ms
9.2 sec
1.7 sec
Visit kntr.jp now to see the best up-to-date Kntr content for Japan and also check out these interesting facts you probably never knew about kntr.jp
ケータイ国盗り合戦はケータイやスマホの位置情報を使って遊ぶ空前絶後のモバイルスタンプラリーです。全600国の完全制覇をめざして、日本中におでかけしよう!
Visit kntr.jpWe analyzed Kntr.jp page load time and found that the first response time was 744 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kntr.jp performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value13.8 s
0/100
25%
Value9.1 s
14/100
10%
Value400 ms
68/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
744 ms
152 ms
298 ms
554 ms
719 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Kntr.jp, 8% (9 requests) were made to Pc.kntr.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Pcimg.kntr.jp.
Page size can be reduced by 376.0 kB (13%)
2.9 MB
2.6 MB
In fact, the total size of Kntr.jp main page is 2.9 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. 60% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 57.4 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 11.4 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 57.4 kB or 84% of the original size.
Potential reduce by 58.4 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. Kntr images are well optimized though.
Potential reduce by 212.3 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 212.3 kB or 70% of the original size.
Potential reduce by 47.9 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. Kntr.jp needs all CSS files to be minified and compressed as it can save up to 47.9 kB or 85% of the original size.
Number of requests can be reduced by 26 (22%)
117
91
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kntr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pc.kntr.jp
744 ms
sns.css
152 ms
pr.css
298 ms
pc_append.css
554 ms
modernizr-2.5.3.min.js
719 ms
jquery-1.9.1.min.js
573 ms
response.js
532 ms
jquery.flickgal.js
531 ms
jquery.cookie.js
388 ms
skrollr.min.js
741 ms
parapara.js
908 ms
overlay.js
900 ms
align2.js
865 ms
functions.js
894 ms
line-button.js
374 ms
platform.js
67 ms
sdk.js
159 ms
skroller_init.js
1045 ms
analytics.js
22 ms
loading_035_2.gif
20 ms
pic_fun_link.png
375 ms
cloud.png
171 ms
title.png
335 ms
building.png
330 ms
mnt_green.png
364 ms
mnt_yerrow.png
466 ms
f_title.png
499 ms
chara2.png
681 ms
arrow.gif
344 ms
seacat.png
694 ms
yama_left.png
696 ms
yama_right.png
712 ms
what_btn.png
820 ms
3step_btn.png
846 ms
content_btn.png
1008 ms
app_btn.png
1105 ms
guide_btn.png
1014 ms
btn_topnav_blog.png
1047 ms
icon_app_small.png
1150 ms
icon_google_small.png
1197 ms
qr.png
1352 ms
title_content1.png
1440 ms
img_about1.png
1614 ms
img_about2.png
1613 ms
title_content2.png
1513 ms
step1.png
1673 ms
step2.png
1581 ms
step3.png
1954 ms
title_content3.png
1861 ms
img_content1.png
2273 ms
img_content2.png
2108 ms
apple.png
2114 ms
android.png
2008 ms
rord1.png
2298 ms
collect
27 ms
rord2.png
2257 ms
119 ms
xd_arbiter.php
132 ms
xd_arbiter.php
259 ms
loading_035_2.gif
307 ms
sand2.png
3101 ms
stone.gif
2324 ms
tono_walk03.png
2141 ms
f_start.png
2291 ms
tono_push2.png
2317 ms
f_push.png
2286 ms
tono_2.png
2427 ms
f_touitsu.png
2347 ms
f_2nd.png
2450 ms
f_next.png
2280 ms
f_new.png
2380 ms
f_final.png
2412 ms
train.png
2269 ms
cloud2.png
2288 ms
footer_siro2.png
2444 ms
seiha.png
2299 ms
ashiba2.png
2413 ms
tono.png
2388 ms
jii.png
2176 ms
hime.png
2290 ms
btn_trigger.png
2463 ms
logo_l.png
2322 ms
title_menu.png
2263 ms
title_topsp.png
2246 ms
title1.png
2182 ms
img_sp1.png
2157 ms
title2.png
2402 ms
title_step.png
2310 ms
arrow_prev.png
2154 ms
arrow_next.png
2140 ms
step1.png
2126 ms
step2.png
1981 ms
step3.png
2196 ms
title3.png
2065 ms
img_taka.png
2457 ms
img_jouka.png
2134 ms
title_modal.png
1962 ms
scroll.png
1988 ms
bn_modal_i.png
1861 ms
bn_modal_a.png
2059 ms
logo_mapion.png
2141 ms
sp.css
230 ms
bg_pattern1.png
152 ms
plugins.js
295 ms
bookmark_button.js
332 ms
green_top.png
191 ms
green_middle.png
350 ms
machi.png
656 ms
sea.gif
452 ms
grass2.png
852 ms
bridge.png
334 ms
bridge-gard.png
524 ms
bg_topnav.png
957 ms
modal_02.png
1563 ms
bg_roadbottom.png
151 ms
bg_topcontent.png
1437 ms
bg_step.png
295 ms
tono_walk.png
441 ms
kntr.jp accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
kntr.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kntr.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Kntr.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 Kntr.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.
kntr.jp
Open Graph data is detected on the main page of Kntr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: