Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

sugizaki-highwaybus.com

杉崎高速バス - 夜行バス、乗合バスはSUGIZAKI・トラベルサポートへ -

Page Load Speed

15.2 sec in total

First Response

3.6 sec

Resources Loaded

11.4 sec

Page Rendered

253 ms

sugizaki-highwaybus.com screenshot

About Website

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

夜行バス、乗合バスはSUGIZAKI・トラベルサポートへ「杉崎高速バス」

Visit sugizaki-highwaybus.com

Key Findings

We analyzed Sugizaki-highwaybus.com page load time and found that the first response time was 3.6 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

sugizaki-highwaybus.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

sugizaki-highwaybus.com

3579 ms

main.css

597 ms

jquery-1.11.2.min.js

988 ms

jquery.page-scroller-309.js

513 ms

jquery.easing.1.3.js

604 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 98% of them (90 requests) were addressed to the original Sugizaki-highwaybus.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Sugizaki-highwaybus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 355.5 kB (14%)

Content Size

2.5 MB

After Optimization

2.2 MB

In fact, the total size of Sugizaki-highwaybus.com main page is 2.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. 30% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 31.2 kB

  • Original 36.8 kB
  • After minification 32.8 kB
  • After compression 5.6 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 4.0 kB, which is 11% 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 31.2 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 120.2 kB

  • Original 2.2 MB
  • After minification 2.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. Sugizaki Highwaybus images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 157.5 kB

  • Original 233.2 kB
  • After minification 219.1 kB
  • After compression 75.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 157.5 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 46.5 kB

  • Original 56.1 kB
  • After minification 50.5 kB
  • After compression 9.5 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. Sugizaki-highwaybus.com needs all CSS files to be minified and compressed as it can save up to 46.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

90

After Optimization

74

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

Accessibility Review

sugizaki-highwaybus.com accessibility score

49

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

[aria-hidden="true"] elements contain focusable descendents

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

[id] attributes on active, focusable elements are not unique

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

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.

Best Practices

sugizaki-highwaybus.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

sugizaki-highwaybus.com SEO score

82

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sugizaki-highwaybus.com 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 Sugizaki-highwaybus.com main page’s claimed encoding is euc-jp. 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 Sugizaki Highwaybus. 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: