Tools & Wizards About Us
kantobus.info screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

kantobus.info

運賃・経路－関東自動車株式会社

Page Load Speed

8.6 sec in total

First Response

652 ms

Resources Loaded

7.8 sec

Page Rendered

199 ms

kantobus.info screenshot

About Website

Click here to check amazing Kantobus content for Japan. Otherwise, check out these important facts you probably never knew about kantobus.info

栃木県のバス(路線バス･空港/高速バス･貸切バス)サービス、契約輸送･ラッピングバス･中刷り広告のご案内。関東自動車ホームページ。

Visit kantobus.info

Key Findings

We analyzed Kantobus.info page load time and found that the first response time was 652 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

kantobus.info performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

kantobus.info

652 ms

kantobus.info

754 ms

bootstrap.css

907 ms

common.css

1083 ms

jquery.fancybox.css

958 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 25% of them (21 requests) were addressed to the original Kantobus.info, 49% (41 requests) were made to Kantobus.co.jp and 8% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Kantobus.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.7 kB (33%)

Content Size

1.1 MB

After Optimization

752.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kantobus.info main page is 1.1 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 822.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 40.3 kB

  • Original 51.2 kB
  • After minification 50.4 kB
  • After compression 10.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. 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 40.3 kB or 79% of the original size.

Image Optimization

-37%

Potential reduce by 308.2 kB

  • Original 822.2 kB
  • After minification 513.9 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, Kantobus needs image optimization as it can save up to 308.2 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 14.0 kB

  • Original 219.1 kB
  • After minification 218.2 kB
  • After compression 205.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-33%

Potential reduce by 11.1 kB

  • Original 33.7 kB
  • After minification 33.2 kB
  • After compression 22.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. Kantobus.info needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (35%)

Requests Now

80

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 80 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 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kantobus.info

kantobus.info

652 ms

kantobus.info

kantobus.info

754 ms

bootstrap.css

bootstrap.css

907 ms

common.css

common.css

1083 ms

jquery.fancybox.css

jquery.fancybox.css

958 ms

route.css

route.css

955 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1472 ms

jquery.cookie.js

jquery.cookie.js

960 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

1587 ms

common.js

common.js

1609 ms

js

js

58 ms

calendar.css

calendar.css

184 ms

busget.css

busget.css

369 ms

calendar.js

calendar.js

550 ms

map_select.js

map_select.js

553 ms

route_find.js

route_find.js

566 ms

element.js

element.js

43 ms

line-button.js

line-button.js

231 ms

developers.line.biz

developers.line.biz

869 ms

calendar.png

calendar.png

187 ms

button_find.png

button_find.png

212 ms

route_map_image.png

route_map_image.png

377 ms

gicon.single.png

gicon.single.png

186 ms

gicon.plural.png

gicon.plural.png

212 ms

gicon.single.landmark.png

gicon.single.landmark.png

370 ms

gicon.plural.landmark.png

gicon.plural.landmark.png

368 ms

gicon.single.cocktail.png

gicon.single.cocktail.png

422 ms

gicon.plural.cocktail.png

gicon.plural.cocktail.png

423 ms

gicon.single.gyoza.png

gicon.single.gyoza.png

551 ms

gicon.plural.gyoza.png

gicon.plural.gyoza.png

553 ms

button_find_map.png

button_find_map.png

565 ms

h_help.png

h_help.png

574 ms

logo.png

logo.png

186 ms

btn-menu.png

btn-menu.png

169 ms

nav_route.png

nav_route.png

1192 ms

nav_airport.png

nav_airport.png

527 ms

nav_highway.png

nav_highway.png

527 ms

nav_charter.png

nav_charter.png

1221 ms

nav_contract.png

nav_contract.png

1413 ms

nav_ropeway.png

nav_ropeway.png

1424 ms

nav_eco-clean.png

nav_eco-clean.png

1015 ms

nav_ad.png

nav_ad.png

1513 ms

nav_tour.png

nav_tour.png

1508 ms

nav_company.png

nav_company.png

2200 ms

nav_recruit.png

nav_recruit.png

2396 ms

fontsize.png

fontsize.png

1901 ms

pttl.png

pttl.png

2127 ms

kankyo_teiki_side.png

kankyo_teiki_side.png

2193 ms

side-bnr01.jpg

side-bnr01.jpg

2744 ms

side-bnr02.jpg

side-bnr02.jpg

2934 ms

side-bnr03.jpg

side-bnr03.jpg

3264 ms

side-bnr04.jpg

side-bnr04.jpg

3029 ms

inquiry-tel05.gif

inquiry-tel05.gif

2903 ms

inquiry.png

inquiry.png

2899 ms

pagetop.png

pagetop.png

3513 ms

nav_home.png

nav_home.png

4125 ms

bus.png

bus.png

3469 ms

footer-logo.png

footer-logo.png

4244 ms

arrow_under.png

arrow_under.png

582 ms

bg-pttl.jpg

bg-pttl.jpg

4570 ms

icon-home-company.png

icon-home-company.png

3792 ms

arrow01.png

arrow01.png

3912 ms

arrow04.png

arrow04.png

3985 ms

bg-w.png

bg-w.png

4316 ms

anime.gif

anime.gif

4723 ms

arrow02.png

arrow02.png

4502 ms

like.php

like.php

197 ms

widgets.js

widgets.js

22 ms

cse.js

cse.js

53 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

19 ms

settings

settings

144 ms

cse.js

cse.js

47 ms

cse_element__ja.js

cse_element__ja.js

10 ms

default+ja.css

default+ja.css

59 ms

default.css

default.css

57 ms

async-ads.js

async-ads.js

38 ms

branding.png

branding.png

13 ms

clear.png

clear.png

11 ms

nav_logo114.png

nav_logo114.png

27 ms

egn1bxb8juf.js

egn1bxb8juf.js

46 ms

FEppCFCt76d.png

FEppCFCt76d.png

46 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

6 ms

embeds

embeds

30 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

24 ms

Accessibility Review

kantobus.info accessibility score

68

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kantobus.info best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kantobus.info SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: