Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

buste.in

バス停検索

Page Load Speed

2.7 sec in total

First Response

595 ms

Resources Loaded

1.9 sec

Page Rendered

183 ms

buste.in screenshot

About Website

Click here to check amazing Buste content for Japan. Otherwise, check out these important facts you probably never knew about buste.in

路線バス、高速バスの乗り場情報などを掲載

Visit buste.in

Key Findings

We analyzed Buste.in page load time and found that the first response time was 595 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

buste.in performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

buste.in

595 ms

base.css

406 ms

dc.js

31 ms

bg_main_h2.gif

355 ms

bustei_ss01.jpg

631 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 71% of them (5 requests) were addressed to the original Buste.in, 29% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (875 ms) belongs to the original domain Buste.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.6 kB (11%)

Content Size

105.7 kB

After Optimization

94.1 kB

In fact, the total size of Buste.in main page is 105.7 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. Only 10% of websites need less resources to load. Images take 73.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.3 kB

  • Original 13.4 kB
  • After minification 12.8 kB
  • After compression 3.1 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 10.3 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 73.4 kB
  • After minification 73.4 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. Buste images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 27 B

  • Original 17.1 kB
  • After minification 17.1 kB
  • After compression 17.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

-73%

Potential reduce by 1.3 kB

  • Original 1.8 kB
  • After minification 868 B
  • After compression 480 B

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. Buste.in needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buste. According to our analytics all requests are already optimized.

Accessibility Review

buste.in accessibility score

95

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

Best Practices

buste.in best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

buste.in SEO score

93

Search Engine Optimization Advices

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

    N/A

  • Encoding

    SHIFT_JIS

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

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