Tools & Wizards About Us
kotobus-express.jp screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

kotobus-express.jp

高速夜行バス｜香川･徳島・高知・愛媛～東京・名古屋・博多｜コトバス

Page Load Speed

6.3 sec in total

First Response

528 ms

Resources Loaded

5.1 sec

Page Rendered

647 ms

kotobus-express.jp screenshot

About Website

Welcome to kotobus-express.jp homepage info - get ready to check Kotobus Express best content for Japan right away, or after learning these important things about kotobus-express.jp

香川・高知・愛媛・徳島発の四国と東京・大阪・名古屋・福岡への高速バス・夜行バスを検索、予約ができます。琴平バス（コトバス）グループの新日本ツーリストで快適バスに泊まりませんか？

Visit kotobus-express.jp

Key Findings

We analyzed Kotobus-express.jp page load time and found that the first response time was 528 ms 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.

Performance Metrics

kotobus-express.jp performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value39.9 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value1.233

1/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

kotobus-express.jp

528 ms

kotobus-express.jp

1062 ms

base.css

522 ms

index.css

703 ms

colorbox.css

530 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 76% of them (78 requests) were addressed to the original Kotobus-express.jp, 12% (12 requests) were made to Eexpress.jp and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kotobus-express.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 482.5 kB (15%)

Content Size

3.2 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kotobus-express.jp main page is 3.2 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. 80% 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 87.6 kB

  • Original 100.2 kB
  • After minification 78.2 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 21.9 kB, which is 22% 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 87.6 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 161.9 kB

  • Original 2.7 MB
  • After minification 2.5 MB

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. Kotobus Express images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 150.1 kB

  • Original 269.1 kB
  • After minification 232.4 kB
  • After compression 119.0 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 150.1 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 82.9 kB

  • Original 102.6 kB
  • After minification 84.2 kB
  • After compression 19.8 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. Kotobus-express.jp needs all CSS files to be minified and compressed as it can save up to 82.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (40%)

Requests Now

92

After Optimization

55

  • Images
  • JavaScript
  • CSS

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kotobus Express. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kotobus-express.jp

kotobus-express.jp

528 ms

kotobus-express.jp

kotobus-express.jp

1062 ms

base.css

base.css

522 ms

index.css

index.css

703 ms

colorbox.css

colorbox.css

530 ms

jquery.js

jquery.js

882 ms

jquery.base.js

jquery.base.js

530 ms

jquery.tile.js

jquery.tile.js

535 ms

jquery.bxslider.js

jquery.bxslider.js

700 ms

jquery.colorbox.js

jquery.colorbox.js

899 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

56 ms

jquery-ui.custom.min.js

jquery-ui.custom.min.js

59 ms

jquery-ui-i18n.js

jquery-ui-i18n.js

61 ms

jkmegamenu.js

jkmegamenu.js

61 ms

chiikiList.js

chiikiList.js

60 ms

kenList.js

kenList.js

62 ms

kenFromToMap.js

kenFromToMap.js

61 ms

kenToshiMap.js

kenToshiMap.js

62 ms

dtProps.js

dtProps.js

743 ms

holidayList.js

holidayList.js

63 ms

busSearchCommon2.js

busSearchCommon2.js

61 ms

sach_cal_sdt.js

sach_cal_sdt.js

705 ms

sach_cal_fdt.js

sach_cal_fdt.js

711 ms

templates.css

templates.css

358 ms

notosansjapanese.css

notosansjapanese.css

31 ms

css

css

49 ms

img_logo.svg

img_logo.svg

1080 ms

img_sl_01.png

img_sl_01.png

405 ms

img_sl_02.png

img_sl_02.png

531 ms

img_sl_03.png

img_sl_03.png

610 ms

img_sl_04.png

img_sl_04.png

404 ms

img_sl_011.png

img_sl_011.png

768 ms

line.jpg

line.jpg

529 ms

bnr_cp_wada.gif

bnr_cp_wada.gif

610 ms

bnr_cp_special.gif

bnr_cp_special.gif

610 ms

bnr_cp_510.gif

bnr_cp_510.gif

730 ms

bnr_cp_721.gif

bnr_cp_721.gif

730 ms

bnr_cp_point.gif

bnr_cp_point.gif

773 ms

img_cert_iso39001.svg

img_cert_iso39001.svg

768 ms

01.jpg

01.jpg

775 ms

01.jpg

01.jpg

885 ms

01.jpg

01.jpg

889 ms

bnr_gp_junpai.png

bnr_gp_junpai.png

945 ms

bnr_gp_vacation.png

bnr_gp_vacation.png

949 ms

bnr_gp_tour.png

bnr_gp_tour.png

950 ms

bnr_gp_udontaxi.png

bnr_gp_udontaxi.png

951 ms

bnr_gp_kotori.png

bnr_gp_kotori.png

1064 ms

sns_facebook.svg

sns_facebook.svg

1086 ms

sns_twitter.svg

sns_twitter.svg

1088 ms

sns_line.svg

sns_line.svg

1125 ms

2024_yashima_ikkaku_1-thumb-640x640-3351.jpg

2024_yashima_ikkaku_1-thumb-640x640-3351.jpg

1548 ms

7100b8c5b6e8208aa2ac2b603a66bb01bbed62d8-thumb-720x720-3335.jpg

7100b8c5b6e8208aa2ac2b603a66bb01bbed62d8-thumb-720x720-3335.jpg

1739 ms

2024_yashima_makura_45-thumb-720x720-3310.jpg

2024_yashima_makura_45-thumb-720x720-3310.jpg

1570 ms

2024_yashima_69-thumb-640x640-3280.jpg

2024_yashima_69-thumb-640x640-3280.jpg

1744 ms

img_cert_pmark.png

img_cert_pmark.png

1258 ms

img_logo_group.svg

img_logo_group.svg

1304 ms

btn_pagetop.svg

btn_pagetop.svg

1424 ms

gtm.js

gtm.js

311 ms

bg_header.png

bg_header.png

1062 ms

bg_chk_blue.png

bg_chk_blue.png

1118 ms

icon_mypage_pc.svg

icon_mypage_pc.svg

1124 ms

nav_home.svg

nav_home.svg

1121 ms

nav_timetable.svg

nav_timetable.svg

1122 ms

nav_campaign.svg

nav_campaign.svg

1235 ms

nav_seat.svg

nav_seat.svg

1240 ms

nav_park.svg

nav_park.svg

1295 ms

nav_guide.svg

nav_guide.svg

1297 ms

arr_01.svg

arr_01.svg

1300 ms

icon_sb_pref.png

icon_sb_pref.png

1250 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

259 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

355 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

381 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

545 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

467 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

468 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

467 ms

icon_sb_calendar.png

icon_sb_calendar.png

1355 ms

img_sl_01.jpg

img_sl_01.jpg

1362 ms

img_sl_02.jpg

img_sl_02.jpg

1240 ms

img_sl_03.jpg

img_sl_03.jpg

1242 ms

img_sl_04.jpg

img_sl_04.jpg

1417 ms

tag.js

tag.js

276 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

142 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

290 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

125 ms

img_sl_011.jpg

img_sl_011.jpg

1192 ms

bg_campaign.png

bg_campaign.png

1137 ms

icon_rt_pin.png

icon_rt_pin.png

1137 ms

icon_rt_seat.png

icon_rt_seat.png

1067 ms

icon_rt_search.png

icon_rt_search.png

1171 ms

icon_rt_calendar.png

icon_rt_calendar.png

1175 ms

payment.svg

payment.svg

1110 ms

park.svg

park.svg

1111 ms

baggage.svg

baggage.svg

1079 ms

cancel.svg

cancel.svg

1086 ms

facility.svg

facility.svg

1183 ms

point.svg

point.svg

1189 ms

bg_quality.png

bg_quality.png

1834 ms

arr_03.svg

arr_03.svg

1133 ms

bg_aboutus.jpg

bg_aboutus.jpg

1252 ms

arr_02.svg

arr_02.svg

1086 ms

btn_cp_prev.png

btn_cp_prev.png

1183 ms

btn_cp_next.png

btn_cp_next.png

1191 ms

Accessibility Review

kotobus-express.jp accessibility score

90

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

kotobus-express.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kotobus-express.jp SEO score

86

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

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kotobus-express.jp 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 Kotobus-express.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.

Social Sharing Optimization

kotobus-express.jp

Open Graph description is not detected on the main page of Kotobus Express. 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: