Tools & Wizards About Us
yasakabus.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

yasakabus.com

ヤサカバス−オフィシャルホームページへようこそ

Page Load Speed

3.6 sec in total

First Response

580 ms

Resources Loaded

2.9 sec

Page Rendered

140 ms

yasakabus.com screenshot

About Website

Welcome to yasakabus.com homepage info - get ready to check Yasakabus best content for Japan right away, or after learning these important things about yasakabus.com

京都・洛西の路線バス、ヤサカバスのオフィシャルサイトです。バス路線図や、時刻表・運賃表等を掲載。その他天然ガス・ノンステップバスなどの車輌紹介や、沿線風景(桂坂・洛西・JR向日町等)の紹介など。

Visit yasakabus.com

Key Findings

We analyzed Yasakabus.com page load time and found that the first response time was 580 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

yasakabus.com performance score

0

Network Requests Diagram

yasakabus.com

580 ms

f_left.html

289 ms

f_top.html

481 ms

f_main.html

579 ms

bg.gif

383 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to Yasakabus.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Yasakabus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 738 B (2%)

Content Size

46.0 kB

After Optimization

45.3 kB

  • HTML
  • Images

In fact, the total size of Yasakabus.com main page is 46.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 44.5 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 738 B

  • Original 1.5 kB
  • After minification 1.4 kB
  • After compression 729 B

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 738 B or 50% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 18 (72%)

Requests Now

25

After Optimization

7

  • AJAX
  • Images

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

Network Requests Diagram

yasakabus.com

yasakabus.com

580 ms

f_left.html

f_left.html

289 ms

f_top.html

f_top.html

481 ms

f_main.html

f_main.html

579 ms

bg.gif

bg.gif

383 ms

bg_01.gif

bg_01.gif

296 ms

bus_02.jpg

bus_02.jpg

917 ms

obi.gif

obi.gif

429 ms

top_3.jpg

top_3.jpg

854 ms

b_01.gif

b_01.gif

477 ms

line_02.gif

line_02.gif

502 ms

b_02.gif

b_02.gif

560 ms

b_03.gif

b_03.gif

813 ms

b_04.gif

b_04.gif

797 ms

b_05.gif

b_05.gif

869 ms

b_08.gif

b_08.gif

902 ms

b_06.gif

b_06.gif

1104 ms

b_07.gif

b_07.gif

1174 ms

b_08over.gif

b_08over.gif

156 ms

b_07over.gif

b_07over.gif

291 ms

b_06over.gif

b_06over.gif

289 ms

b_05over.gif

b_05over.gif

292 ms

b_04over.gif

b_04over.gif

310 ms

b_03over.gif

b_03over.gif

369 ms

b_02over.gif

b_02over.gif

491 ms

b_01over.gif

b_01over.gif

625 ms

Accessibility Review

yasakabus.com accessibility score

33

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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

yasakabus.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

yasakabus.com SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    X-SJIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yasakabus.com 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 Yasakabus.com main page’s claimed encoding is x-sjis. 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

yasakabus.com

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