Tools & Wizards About Us
tokyu.bus-location.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

tokyu.bus-location.jp

東急バスナビ｜ＰＣ版

Page Load Speed

5 sec in total

First Response

523 ms

Resources Loaded

4.3 sec

Page Rendered

153 ms

tokyu.bus-location.jp screenshot

About Website

Welcome to tokyu.bus-location.jp homepage info - get ready to check Tokyu Bus Location best content for Japan right away, or after learning these important things about tokyu.bus-location.jp

東急バスのバスナビゲーション。バス接近表示情報を、運行情報と併せてリアルタイムで検索できます。

Visit tokyu.bus-location.jp

Key Findings

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

Performance Metrics

tokyu.bus-location.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

13/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.479

18/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

tokyu.bus-location.jp

523 ms

navi

362 ms

jquery.js

851 ms

jquery.popupwindow.js

343 ms

default.js

343 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 112.7 kB (71%)

Content Size

159.9 kB

After Optimization

47.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyu.bus-location.jp main page is 159.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 95.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.0 kB

  • Original 9.7 kB
  • After minification 8.1 kB
  • After compression 2.7 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 1.6 kB, which is 17% 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 7.0 kB or 72% of the original size.

Image Optimization

-7%

Potential reduce by 339 B

  • Original 5.0 kB
  • After minification 4.7 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. Tokyu Bus Location images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 62.9 kB

  • Original 95.6 kB
  • After minification 92.8 kB
  • After compression 32.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 62.9 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 42.5 kB

  • Original 49.5 kB
  • After minification 33.5 kB
  • After compression 7.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. Tokyu.bus-location.jp needs all CSS files to be minified and compressed as it can save up to 42.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (14%)

Requests Now

36

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyu.bus-location.jp

tokyu.bus-location.jp

523 ms

navi

navi

362 ms

jquery.js

jquery.js

851 ms

jquery.popupwindow.js

jquery.popupwindow.js

343 ms

default.js

default.js

343 ms

set.css

set.css

344 ms

default.css

default.css

345 ms

header.css

header.css

343 ms

footer.css

footer.css

345 ms

enhance.css

enhance.css

346 ms

layout.css

layout.css

511 ms

bg_body.gif

bg_body.gif

343 ms

header_logo.gif

header_logo.gif

343 ms

header_ill.gif

header_ill.gif

346 ms

header_tokyubus.gif

header_tokyubus.gif

344 ms

img_ptt01.gif

img_ptt01.gif

346 ms

bg_gnavi.gif

bg_gnavi.gif

348 ms

gnavi_01.gif

gnavi_01.gif

680 ms

gnavi_02.gif

gnavi_02.gif

684 ms

drnavi2_01.gif

drnavi2_01.gif

687 ms

drnavi2_02.gif

drnavi2_02.gif

687 ms

drnavi2_03.gif

drnavi2_03.gif

687 ms

gnavi_03.gif

gnavi_03.gif

686 ms

drnavi3_01.gif

drnavi3_01.gif

1016 ms

title_rosen.gif

title_rosen.gif

1024 ms

btn_rosen01.gif

btn_rosen01.gif

1025 ms

btn_rosen02.gif

btn_rosen02.gif

1026 ms

btn_rosen03.gif

btn_rosen03.gif

1026 ms

title_sekkin.gif

title_sekkin.gif

1028 ms

bg_sekkin.gif

bg_sekkin.gif

1354 ms

btn_sekkin01.gif

btn_sekkin01.gif

1364 ms

img_ptt03.png

img_ptt03.png

1365 ms

title_info.gif

title_info.gif

1367 ms

sidetitle_other.gif

sidetitle_other.gif

1366 ms

i_arrow.gif

i_arrow.gif

1368 ms

sidebtn_guide.gif

sidebtn_guide.gif

1692 ms

sidetitle_mobile.gif

sidetitle_mobile.gif

1704 ms

img_qrcode.gif

img_qrcode.gif

1705 ms

Accessibility Review

tokyu.bus-location.jp accessibility score

65

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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.

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

<object> elements do not have alternate text

Best Practices

tokyu.bus-location.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tokyu.bus-location.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Tokyu.bus-location.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 Tokyu.bus-location.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

tokyu.bus-location.jp

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