5.2 sec in total
926 ms
3.9 sec
340 ms
Click here to check amazing Kantobus content for Japan. Otherwise, check out these important facts you probably never knew about kantobus.info
栃木県のバス(路線バス・空港/高速バス・貸切バス)サービス、契約輸送・ラッピングバス・中刷り広告のご案内。関東自動車ホームページ。
Visit kantobus.infoWe analyzed Kantobus.info page load time and found that the first response time was 926 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
kantobus.info performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value9.4 s
0/100
25%
Value8.5 s
17/100
10%
Value700 ms
42/100
30%
Value0.053
98/100
15%
Value11.1 s
20/100
10%
926 ms
676 ms
1007 ms
708 ms
708 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 21% of them (20 requests) were addressed to the original Kantobus.info, 40% (38 requests) were made to Kantobus.co.jp and 11% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Kantobus.co.jp.
Page size can be reduced by 312.2 kB (31%)
1.0 MB
700.6 kB
In fact, the total size of Kantobus.info main page is 1.0 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. 55% of websites need less resources to load. Images take 482.2 kB which makes up the majority of the site volume.
Potential reduce by 41.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 41.6 kB or 78% of the original size.
Potential reduce by 25.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. Kantobus images are well optimized though.
Potential reduce by 165.4 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 165.4 kB or 44% of the original size.
Potential reduce by 79.3 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. Kantobus.info needs all CSS files to be minified and compressed as it can save up to 79.3 kB or 80% of the original size.
Number of requests can be reduced by 39 (42%)
92
53
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kantobus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
kantobus.info
926 ms
bootstrap.css
676 ms
common.css
1007 ms
jquery.fancybox.css
708 ms
route.css
708 ms
jquery-1.7.2.min.js
1444 ms
jquery.cookie.js
730 ms
jquery.fancybox.pack.js
1009 ms
common.js
1056 ms
calendar.css
340 ms
busget.css
351 ms
calendar.js
517 ms
map_select.js
379 ms
route_find.js
398 ms
element.js
36 ms
line-button.js
471 ms
line-button.js
525 ms
analytics.js
35 ms
calendar.png
193 ms
logo.png
173 ms
btn-menu.png
197 ms
nav_route.png
173 ms
nav_airport.png
183 ms
nav_highway.png
201 ms
nav_charter.png
182 ms
nav_contract.png
339 ms
nav_ad.png
338 ms
nav_company.png
377 ms
nav_recruit.png
378 ms
fontsize.png
379 ms
pttl.png
391 ms
kankyo_teiki_side.png
544 ms
side-bnr01.jpg
686 ms
side-bnr02.jpg
546 ms
side-bnr03.jpg
703 ms
side-bnr04.jpg
552 ms
inquiry-tel.gif
577 ms
inquiry.png
686 ms
pagetop.png
701 ms
nav_home.png
730 ms
bus.png
756 ms
footer-logo.png
850 ms
button_find.png
177 ms
route_map_image.png
576 ms
gicon.single.png
213 ms
gicon.plural.png
186 ms
gicon.single.landmark.png
214 ms
gicon.plural.landmark.png
369 ms
gicon.single.cocktail.png
372 ms
gicon.plural.cocktail.png
369 ms
gicon.single.gyoza.png
453 ms
gicon.plural.gyoza.png
452 ms
button_find_map.png
538 ms
h_help.png
539 ms
translateelement.css
80 ms
main.js
135 ms
linkid.js
55 ms
bg-pttl.jpg
1424 ms
icon-home-company.png
998 ms
arrow01.png
793 ms
arrow04.png
826 ms
bg-w.png
1006 ms
anime.gif
930 ms
arrow02.png
968 ms
arrow_under.png
464 ms
collect
3 ms
collect
76 ms
widgets.js
114 ms
cse.js
50 ms
cse.js
144 ms
element_main.js
59 ms
like.php
197 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
249 ms
translate_24dp.png
54 ms
l
49 ms
cleardot.gif
83 ms
jsapi
77 ms
googlelogo_color_68x28dp.png
9 ms
te_ctrl3.gif
18 ms
loading.gif
29 ms
default+ja.css
12 ms
default+ja.I.js
83 ms
qeKvIRsJabD.js
231 ms
LVx-xkvaJ0b.png
246 ms
te_bk.gif
18 ms
default.css
5 ms
async-ads.js
45 ms
google_custom_search_watermark.gif
33 ms
small-logo.png
37 ms
search_box_icon.png
37 ms
clear.png
37 ms
nav_logo114.png
36 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
52 ms
jot
84 ms
82x20.png
176 ms
kantobus.info 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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
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.
kantobus.info 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
Browser errors were logged to the console
kantobus.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kantobus.info 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 Kantobus.info 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.
kantobus.info
Open Graph description is not detected on the main page of Kantobus. 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: