Tools & Wizards About Us
honshi-bus.co.jp screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

honshi-bus.co.jp

本四海峡バス株式会社│明石海峡大橋／大鳴門橋を渡って、快適高速バスの旅！

Page Load Speed

5.9 sec in total

First Response

513 ms

Resources Loaded

4.8 sec

Page Rendered

650 ms

honshi-bus.co.jp screenshot

About Website

Welcome to honshi-bus.co.jp homepage info - get ready to check Honshi Bus best content for Japan right away, or after learning these important things about honshi-bus.co.jp

本四海峡バス株式会社は明石海峡大橋・大鳴門橋を渡って、本州と四国をつなぐバス会社です。快適で優雅な旅をお届けできるようみなさまを安全にお送りいたします。

Visit honshi-bus.co.jp

Key Findings

We analyzed Honshi-bus.co.jp page load time and found that the first response time was 513 ms and then it took 5.4 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

honshi-bus.co.jp performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

honshi-bus.co.jp

513 ms

www.honshi-bus.co.jp

810 ms

common.css

315 ms

imgover.js

327 ms

jquery-1.5.2.min.js

670 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that all of those requests were addressed to Honshi-bus.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Honshi-bus.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.2 kB (8%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Honshi-bus.co.jp main page is 1.5 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 33.0 kB

  • Original 41.3 kB
  • After minification 37.3 kB
  • After compression 8.3 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 33.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 4.1 kB

  • Original 1.3 MB
  • After minification 1.3 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. Honshi Bus images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 74.1 kB

  • Original 118.8 kB
  • After minification 112.3 kB
  • After compression 44.7 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 74.1 kB or 62% of the original size.

CSS Optimization

-81%

Potential reduce by 13.0 kB

  • Original 16.0 kB
  • After minification 13.4 kB
  • After compression 3.0 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. Honshi-bus.co.jp needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (12%)

Requests Now

85

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

honshi-bus.co.jp

honshi-bus.co.jp

513 ms

www.honshi-bus.co.jp

www.honshi-bus.co.jp

810 ms

common.css

common.css

315 ms

imgover.js

imgover.js

327 ms

jquery-1.5.2.min.js

jquery-1.5.2.min.js

670 ms

ecl.js

ecl.js

505 ms

base64.js

base64.js

340 ms

topics.js

topics.js

345 ms

magin.css

magin.css

473 ms

index.css

index.css

490 ms

json_topics.php

json_topics.php

178 ms

header_bk.jpg

header_bk.jpg

340 ms

logo.jpg

logo.jpg

183 ms

arrow.jpg

arrow.jpg

184 ms

trans_en.png

trans_en.png

185 ms

trans_ko.png

trans_ko.png

183 ms

trans_cn.png

trans_cn.png

334 ms

trans_tw.png

trans_tw.png

351 ms

gnavi_b.jpg

gnavi_b.jpg

350 ms

gnavi01.jpg

gnavi01.jpg

353 ms

gnavi02.jpg

gnavi02.jpg

356 ms

gnavi03.jpg

gnavi03.jpg

491 ms

gnavi04.jpg

gnavi04.jpg

501 ms

gnavi05.jpg

gnavi05.jpg

518 ms

gnavi06.jpg

gnavi06.jpg

519 ms

mainimage.jpg

mainimage.jpg

862 ms

sn_contact.jpg

sn_contact.jpg

527 ms

sn_tel01.jpg

sn_tel01.jpg

651 ms

sn_tel02.jpg

sn_tel02.jpg

663 ms

sn_mobile01.jpg

sn_mobile01.jpg

685 ms

sn_mobile02.jpg

sn_mobile02.jpg

686 ms

sn_contactbt.jpg

sn_contactbt.jpg

699 ms

sn_bnr01.jpg

sn_bnr01.jpg

818 ms

sn_bnr02.jpg

sn_bnr02.jpg

835 ms

sn_bnr03.jpg

sn_bnr03.jpg

853 ms

sn_bnr06.jpg

sn_bnr06.jpg

854 ms

sn_bnr04.jpg

sn_bnr04.jpg

871 ms

sn_bnr05.jpg

sn_bnr05.jpg

977 ms

sn_titlebk.jpg

sn_titlebk.jpg

1000 ms

sn_btbk01.jpg

sn_btbk01.jpg

1019 ms

sn_btbk02.jpg

sn_btbk02.jpg

1022 ms

sn_btbk03.jpg

sn_btbk03.jpg

1030 ms

sn_bnr07.jpg

sn_bnr07.jpg

1215 ms

index_bt01.jpg

index_bt01.jpg

1135 ms

index_bt02.jpg

index_bt02.jpg

1162 ms

index_bt03.jpg

index_bt03.jpg

1186 ms

title_bk.jpg

title_bk.jpg

1017 ms

index_newsb.jpg

index_newsb.jpg

1023 ms

norikae.jpg

norikae.jpg

1119 ms

honshiro.jpg

honshiro.jpg

1809 ms

index_bunner01.jpg

index_bunner01.jpg

1176 ms

index_bunner02.jpg

index_bunner02.jpg

1031 ms

index_bus.jpg

index_bus.jpg

1038 ms

bnr02.jpg

bnr02.jpg

1044 ms

bnr03.jpg

bnr03.jpg

1109 ms

ft_bk03.jpg

ft_bk03.jpg

1176 ms

pagetop.jpg

pagetop.jpg

1178 ms

ft_bt01.jpg

ft_bt01.jpg

1054 ms

ft_bt02.jpg

ft_bt02.jpg

1064 ms

ft_bt03.jpg

ft_bt03.jpg

1105 ms

ft_bt04.jpg

ft_bt04.jpg

1177 ms

arrow02.jpg

arrow02.jpg

1173 ms

gnavi01_on.jpg

gnavi01_on.jpg

160 ms

gnavi02_on.jpg

gnavi02_on.jpg

164 ms

gnavi03_on.jpg

gnavi03_on.jpg

169 ms

gnavi04_on.jpg

gnavi04_on.jpg

171 ms

gnavi05_on.jpg

gnavi05_on.jpg

174 ms

gnavi06_on.jpg

gnavi06_on.jpg

168 ms

sn_contactbt_on.jpg

sn_contactbt_on.jpg

318 ms

sn_bnr01_on.jpg

sn_bnr01_on.jpg

327 ms

sn_bnr02_on.jpg

sn_bnr02_on.jpg

336 ms

sn_bnr03_on.jpg

sn_bnr03_on.jpg

337 ms

sn_bnr06_on.jpg

sn_bnr06_on.jpg

340 ms

sn_bnr04_on.jpg

sn_bnr04_on.jpg

345 ms

sn_bnr05_on.jpg

sn_bnr05_on.jpg

476 ms

sn_bnr07_on.jpg

sn_bnr07_on.jpg

489 ms

index_bt01_on.jpg

index_bt01_on.jpg

503 ms

index_bt02_on.jpg

index_bt02_on.jpg

505 ms

index_bt03_on.jpg

index_bt03_on.jpg

509 ms

index_bunner01_on.jpg

index_bunner01_on.jpg

689 ms

index_bunner02_on.jpg

index_bunner02_on.jpg

792 ms

bnr02_on.jpg

bnr02_on.jpg

651 ms

bnr03_on.jpg

bnr03_on.jpg

669 ms

ft_bt01_on.jpg

ft_bt01_on.jpg

673 ms

ft_bt02_on.jpg

ft_bt02_on.jpg

679 ms

ft_bt03_on.jpg

ft_bt03_on.jpg

814 ms

ft_bt04_on.jpg

ft_bt04_on.jpg

836 ms

Accessibility Review

honshi-bus.co.jp accessibility score

88

Accessibility Issues

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

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

Links do not have a discernible name

Best Practices

honshi-bus.co.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

honshi-bus.co.jp SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Honshi-bus.co.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 Honshi-bus.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

honshi-bus.co.jp

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