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

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

j-bus.co.jp

高速バス・夜行/深夜バスの予約なら - 発車オ～ライネット

Page Load Speed

6.3 sec in total

First Response

456 ms

Resources Loaded

5.5 sec

Page Rendered

353 ms

j-bus.co.jp screenshot

About Website

Visit j-bus.co.jp now to see the best up-to-date J Bus content for Japan and also check out these interesting facts you probably never knew about j-bus.co.jp

東京、大阪、名古屋発着をはじめ、全国400路線以上から選べる高速バス・夜行バスの予約サイト【発車オ～ライネット】。ディズニーやUSJ、空港バス、観光コース等プランも充実！コンビニ発券・クレジット決済、モバイルチケットでバス予約がとても簡単！

Visit j-bus.co.jp

Key Findings

We analyzed J-bus.co.jp page load time and found that the first response time was 456 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

j-bus.co.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.0 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.132

81/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

hon

456 ms

font-awesome.css

351 ms

jquery-ui.min.css

681 ms

common.css

685 ms

default.css

525 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original J-bus.co.jp, 4% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Secure.j-bus.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 936.8 kB (39%)

Content Size

2.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 91.2 kB

  • Original 109.3 kB
  • After minification 83.1 kB
  • After compression 18.0 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 26.2 kB, which is 24% 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 91.2 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 88.3 kB

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

JavaScript Optimization

-64%

Potential reduce by 577.8 kB

  • Original 903.1 kB
  • After minification 854.5 kB
  • After compression 325.3 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 577.8 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 179.5 kB

  • Original 216.1 kB
  • After minification 163.0 kB
  • After compression 36.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. J-bus.co.jp needs all CSS files to be minified and compressed as it can save up to 179.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (42%)

Requests Now

71

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of J 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 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hon

hon

456 ms

font-awesome.css

font-awesome.css

351 ms

jquery-ui.min.css

jquery-ui.min.css

681 ms

common.css

common.css

685 ms

default.css

default.css

525 ms

toastr.min.css

toastr.min.css

530 ms

placesearch.css

placesearch.css

562 ms

index.css

index.css

856 ms

ownmedia.css

ownmedia.css

721 ms

jbusapp.css

jbusapp.css

1036 ms

smartbanner.css

smartbanner.css

755 ms

jquery.js

jquery.js

1193 ms

jquery-ui.min.js

jquery-ui.min.js

1207 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

901 ms

jquery.cookie.js

jquery.cookie.js

944 ms

common.js

common.js

1084 ms

ifvisible.js

ifvisible.js

1251 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

1317 ms

moment.min.js

moment.min.js

1235 ms

toastr.min.js

toastr.min.js

1304 ms

encoding.min.js

encoding.min.js

1534 ms

js

js

43 ms

index.js

index.js

1371 ms

index-buslogo.js

index-buslogo.js

1411 ms

jquery.rwdImageMaps.min.js

jquery.rwdImageMaps.min.js

1430 ms

smartbanner.js

smartbanner.js

1524 ms

js

js

71 ms

js

js

91 ms

ytag.js

ytag.js

703 ms

fbevents.js

fbevents.js

384 ms

lt.js

lt.js

383 ms

logo-jbus.png

logo-jbus.png

370 ms

X_logo-handle.png

X_logo-handle.png

474 ms

icon-menu.png

icon-menu.png

369 ms

JBOBanner_full.png

JBOBanner_full.png

368 ms

mainvisual.jpg

mainvisual.jpg

427 ms

icon-tab-highway_on.png

icon-tab-highway_on.png

372 ms

icon-tab-airportline.png

icon-tab-airportline.png

428 ms

icon-tab-tours.png

icon-tab-tours.png

472 ms

icon-tab-routelist.png

icon-tab-routelist.png

427 ms

mainvisual_sp.jpg

mainvisual_sp.jpg

1415 ms

shape-arrow-03.png

shape-arrow-03.png

1411 ms

illust-tab-tours.png

illust-tab-tours.png

1408 ms

illust-tab-tours_sp.png

illust-tab-tours_sp.png

1413 ms

pic-tabsother-ticket.png

pic-tabsother-ticket.png

1414 ms

pic-tabsother-smartphone.png

pic-tabsother-smartphone.png

1413 ms

logo-jp_02.png

logo-jp_02.png

1414 ms

bnr-jbo.png

bnr-jbo.png

1414 ms

pmark.png

pmark.png

1415 ms

scrolltop.gif

scrolltop.gif

1415 ms

analytics.js

analytics.js

232 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1080 ms

photo-performance.png

photo-performance.png

1226 ms

err.gif

err.gif

1116 ms

8012017a-49fc-45fc-b9e3-39742093a9e5.js

8012017a-49fc-45fc-b9e3-39742093a9e5.js

944 ms

collect

collect

915 ms

Alert

Alert

878 ms

1901_%E5%8C%97%E9%99%B8%E9%89%84%E9%81%93.png

1901_%E5%8C%97%E9%99%B8%E9%89%84%E9%81%93.png

196 ms

2004_%E9%81%A0%E5%B7%9E%E9%89%84%E9%81%93.png

2004_%E9%81%A0%E5%B7%9E%E9%89%84%E9%81%93.png

203 ms

2801_%E7%A5%9E%E5%A7%AB%E3%83%90%E3%82%B9.png

2801_%E7%A5%9E%E5%A7%AB%E3%83%90%E3%82%B9.png

196 ms

0405_JR%E3%83%90%E3%82%B9%E6%9D%B1%E5%8C%97.png

0405_JR%E3%83%90%E3%82%B9%E6%9D%B1%E5%8C%97.png

194 ms

1312_%E5%B0%8F%E7%94%B0%E6%80%A5%E3%83%8F%E3%82%A4%E3%82%A6%E3%82%A7%E3%82%A4%E3%83%90%E3%82%B9.png

1312_%E5%B0%8F%E7%94%B0%E6%80%A5%E3%83%8F%E3%82%A4%E3%82%A6%E3%82%A7%E3%82%A4%E3%83%90%E3%82%B9.png

207 ms

0702_%E6%96%B0%E5%B8%B8%E7%A3%90%E4%BA%A4%E9%80%9A.png

0702_%E6%96%B0%E5%B8%B8%E7%A3%90%E4%BA%A4%E9%80%9A.png

372 ms

1501_%E5%B1%B1%E6%A2%A8%E4%BA%A4%E9%80%9A.png

1501_%E5%B1%B1%E6%A2%A8%E4%BA%A4%E9%80%9A.png

372 ms

2309_%E5%90%8D%E9%89%84%E3%83%90%E3%82%B9.png

2309_%E5%90%8D%E9%89%84%E3%83%90%E3%82%B9.png

384 ms

1402_%E7%A5%9E%E5%A5%88%E5%B7%9D%E4%B8%AD%E5%A4%AE%E4%BA%A4%E9%80%9A.png

1402_%E7%A5%9E%E5%A5%88%E5%B7%9D%E4%B8%AD%E5%A4%AE%E4%BA%A4%E9%80%9A.png

396 ms

3901_%E3%81%A8%E3%81%95%E3%81%A7%E3%82%93%E4%BA%A4%E9%80%9A.png

3901_%E3%81%A8%E3%81%95%E3%81%A7%E3%82%93%E4%BA%A4%E9%80%9A.png

397 ms

2202_%E6%9D%B1%E6%B5%B7%E8%87%AA%E5%8B%95%E8%BB%8A.png

2202_%E6%9D%B1%E6%B5%B7%E8%87%AA%E5%8B%95%E8%BB%8A.png

487 ms

2901_%E5%A5%88%E8%89%AF%E4%BA%A4%E9%80%9A.png

2901_%E5%A5%88%E8%89%AF%E4%BA%A4%E9%80%9A.png

548 ms

sign-success.png

sign-success.png

520 ms

sign-warning.png

sign-warning.png

535 ms

sign-danger.png

sign-danger.png

548 ms

sign-info.png

sign-info.png

667 ms

Accessibility Review

j-bus.co.jp accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

j-bus.co.jp 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

High

Page has valid source maps

SEO Factors

j-bus.co.jp SEO score

75

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 doesn't use 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 J-bus.co.jp 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 J-bus.co.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

j-bus.co.jp

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