10.4 sec in total
657 ms
9.4 sec
426 ms
Visit kanto.me now to see the best up-to-date Kanto content for Japan and also check out these interesting facts you probably never knew about kanto.me
「GMOとくとくBB」はGMOインターネットグループ株式会社が運営しているインターネットサービスプロバイダーです。ドコモ光、auひかり、GMO光アクセスなどの光回線やWiMAXなどのインターネットサービスをおトクな価格と充実したサポートサービスで提供いたします。
Visit kanto.meWe analyzed Kanto.me page load time and found that the first response time was 657 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kanto.me performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value7.0 s
6/100
25%
Value15.7 s
0/100
10%
Value4,070 ms
1/100
30%
Value0.23
54/100
15%
Value24.6 s
0/100
10%
657 ms
1330 ms
1420 ms
2460 ms
967 ms
Our browser made a total of 214 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Kanto.me, 52% (112 requests) were made to Gmobb.jp and 6% (13 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Gmobb.jp.
Page size can be reduced by 612.9 kB (27%)
2.3 MB
1.7 MB
In fact, the total size of Kanto.me main page is 2.3 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 39.8 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 39.8 kB or 75% of the original size.
Potential reduce by 198.7 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, Kanto needs image optimization as it can save up to 198.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 255.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 255.9 kB or 64% of the original size.
Potential reduce by 118.6 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. Kanto.me needs all CSS files to be minified and compressed as it can save up to 118.6 kB or 84% of the original size.
Number of requests can be reduced by 88 (44%)
202
114
The browser has sent 202 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
kanto.me
657 ms
gmobb.jp
1330 ms
base.css
1420 ms
this.css
2460 ms
iepngfix.js
967 ms
jquery.js
2623 ms
drpdwn.js
1969 ms
script02.js
652 ms
support_top_scrollers.js
816 ms
index_b.js
981 ms
countdown.js
1137 ms
plusone.js
103 ms
script.js
192 ms
bookmark_button.js
322 ms
platform.js
74 ms
init.js
399 ms
pixel.js
50 ms
conversion.js
49 ms
script.js
33 ms
service_navi.css
167 ms
countdown.css
157 ms
cb=gapi.loaded_0
57 ms
plusone.js
58 ms
upgrade_img01.png
1262 ms
button-only.gif
207 ms
gmologo.png
50 ms
tl.php
388 ms
main_bg01_hiru.gif
193 ms
hdi_banner.gif
191 ms
gnavi_sub02_ttl01.gif
193 ms
topB_lead.png
364 ms
wimax2_main.jpg
529 ms
docomohikari_mainImg01.jpg
662 ms
fletsv6_main.jpg
687 ms
norikae_sec01.png
1157 ms
au_mainImg01.png
516 ms
wimax2plus-refacarat_mainImg01.jpg
897 ms
shokai_mainImg01.jpg
1183 ms
topB_ico_navi01.gif
695 ms
topB_ico_navi02.gif
893 ms
topB_ttl_camp.gif
892 ms
serviceInfo_ttl01.gif
894 ms
serviceInfo_ttl02.gif
1053 ms
srvclnp_mbl03.png
1074 ms
serviceInfo_ttl10.gif
1080 ms
srvclnp_mbl10.png
1074 ms
serviceInfo_ttl03.gif
1234 ms
srvclnp_flts01.png
1235 ms
serviceInfo_ttl08.gif
1237 ms
srvclnp_flts04.png
1238 ms
serviceInfo_ttl09.png
1314 ms
srvclnp_docomohikari01.png
1326 ms
serviceInfo_ttl04.gif
1380 ms
srvclnp_ea01.png
1387 ms
serviceInfo_ttl06.gif
1387 ms
srvclnp_kip01.png
1390 ms
serviceInfo_ttl05.gif
1486 ms
srvclnp_gaku01.png
1480 ms
order_btn01.png
1543 ms
srvcbnr05.png
1548 ms
srvcbnr06.png
1548 ms
ft_bnr_cala.gif
1552 ms
tl.php
374 ms
internet_for_everyone.png
97 ms
analytics.js
23 ms
ft_bnr_yap.gif
1610 ms
like.php
169 ms
widgets.js
167 ms
collect
90 ms
ft_bnr_ptown.gif
1486 ms
ft_bnr_photo.gif
1525 ms
ft_bnr_freeml.gif
1532 ms
cb=gapi.loaded_1
26 ms
fastbutton
117 ms
collect
130 ms
qeKvIRsJabD.js
221 ms
LVx-xkvaJ0b.png
225 ms
241 ms
postmessageRelay
123 ms
tag.js
179 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
34 ms
ft_bnr_kumapon.gif
1357 ms
ga-audiences
80 ms
3193398744-postmessagerelay.js
23 ms
rpc:shindig_random.js
38 ms
cb=gapi.loaded_0
5 ms
ft_bnr_tea.gif
1215 ms
reset.css
11 ms
entry-button.css
12 ms
bnr_yuutai.jpg
1271 ms
button-counter.gif
5 ms
pixel
152 ms
banne_173_62.gif
1194 ms
placard_GMO_234x60.gif
1193 ms
dot_tokyo_234x60.gif
1193 ms
pixel
96 ms
Pug
97 ms
sync.ad-stir.com
393 ms
sync
95 ms
sync
535 ms
is
852 ms
119 ms
180 ms
blade_track_jp.js
443 ms
tag.js
283 ms
cb=gapi.loaded_2
52 ms
subscribe_embed
197 ms
upgrade_img01_ov.png
1367 ms
pixel
38 ms
sd
29 ms
footerstyle.css
86 ms
b_Line.gif
995 ms
wimax2plus_refacarat_986x69.png
1010 ms
main_bg02.gif
1057 ms
logo.png
1140 ms
250 ms
100 ms
20 ms
26 ms
www-subscribe-embed-vflTum1sJ.css
117 ms
www-subscribe-embed.js
135 ms
global_header_link_bg01_hiru.png
980 ms
global_header_bullet01.gif
979 ms
callback_img01.png
973 ms
gnavi_bg.png
972 ms
tag
39 ms
gnavi_bg_hiru.gif
953 ms
www-hitchhiker-vflvB63an.png
29 ms
topA_bg02.png
1032 ms
adfunnel
151 ms
cb=gapi.loaded_0
8 ms
mapuser
149 ms
topA_camp14.png
970 ms
topA_camp27.png
982 ms
topA_camp17.png
982 ms
topA_camp05.png
992 ms
cb=gapi.loaded_3
7 ms
cookie_enabled_get.html
1275 ms
border_3.gif
15 ms
subscribe_embed
69 ms
spacer.gif
11 ms
border_3.gif
25 ms
bubbleSprite_3.png
6 ms
bubbleDropR_3.png
5 ms
bubbleDropB_3.png
5 ms
topA_camp11.png
948 ms
topA_camp30.png
1043 ms
xrost
151 ms
www-subscribe-embed-card-vflqARhQ4.css
9 ms
www-subscribe-embed-card.js
8 ms
topA_camp07.png
1015 ms
countdown_bgtop.gif
996 ms
serviceInfo_bg01.png
996 ms
serviceInfo_bg02.png
1009 ms
serviceInfo_bg10.png
935 ms
serviceInfo_bg03.png
1046 ms
serviceInfo_bg07.png
1007 ms
serviceInfo_bg08.png
1002 ms
serviceInfo_bg04.png
1023 ms
serviceInfo_bg06.png
1009 ms
serviceInfo_bg05.png
935 ms
order_bg01.png
1030 ms
arrow-order-green.png
1008 ms
trnsfr_bg01.png
1001 ms
lsticn02.gif
1017 ms
pnt_bg01.png
1001 ms
sprtbnr01.png
963 ms
sftymrk.png
1014 ms
usfly_bg01.png
1008 ms
usfly_lnk01.png
1004 ms
usfly_lnk02.png
1002 ms
usfly_lnk03.png
1004 ms
favcnts_bg01.png
989 ms
lsticn01.png
998 ms
news_bg01.png
1010 ms
lsticn04.gif
992 ms
footer_txt.gif
1001 ms
ft_bnrs_ttl.png
1009 ms
ft_bnrs_base.png
1014 ms
main_bg03_hiru.gif
992 ms
pagetop_bg.gif
985 ms
sw_footer_open.png
998 ms
sw_footer.png
1000 ms
icow_twitter.gif
1010 ms
icow_fb02.gif
1038 ms
srvclnp_docomohikari01_ov.png
991 ms
order_btn01_ov.png
971 ms
wimax2plus_refacarat_986x69_ov.png
996 ms
topA_camp14_ov.png
991 ms
bl_track.cgi
374 ms
sync.html
411 ms
sync.html
423 ms
sync.html
646 ms
self.html
158 ms
idsync
612 ms
set
312 ms
pixel
62 ms
cs.html
399 ms
oct.js
57 ms
ya.js
359 ms
ids.gif
247 ms
adsct
82 ms
adsct
52 ms
ids.gif
269 ms
ids.gif
157 ms
pb.js
1408 ms
336 ms
356 ms
ids.gif
228 ms
d.js
162 ms
sync.js
233 ms
ids.gif
182 ms
ids.gif
158 ms
kanto.me accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
kanto.me 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
Missing source maps for large first-party JavaScript
kanto.me 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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanto.me can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Kanto.me 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.
kanto.me
Open Graph data is detected on the main page of Kanto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: