Access qbus.jp. 九州のバス時刻表

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

qbus.jp

546 ms

911 ms

index.css

351 ms

importF.css

361 ms

qbus.js

361 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 88% of them (50 requests) were addressed to the original Qbus.jp, 5% (3 requests) were made to Cm.qbus.jp and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Qbus.jp.

Content Size

182.1 kB

After Optimization

98.0 kB

In fact, the total size of Qbus.jp main page is 182.1 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. Images take 92.3 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 39.8 kB

Original 45.1 kB
After minification 43.2 kB
After compression 5.3 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 39.8 kB or 88% of the original size.

Image Optimization

-27%

Potential reduce by 25.0 kB

Original 92.3 kB
After minification 67.3 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. Obviously, Qbus needs image optimization as it can save up to 25.0 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 4.4 kB

Original 25.7 kB
After minification 25.4 kB
After compression 21.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 4.4 kB or 17% of the original size.

CSS Optimization

-78%

Potential reduce by 14.9 kB

Original 19.0 kB
After minification 15.1 kB
After compression 4.2 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. Qbus.jp needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 78% of the original size.

Requests Now

After Optimization

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qbus. 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.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

High

Page is blocked from indexing

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

SHIFT_JIS

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

qbus.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

九州のバス時刻表

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

qbus.jp

index.css

importF.css

qbus.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

qbus.jp

index.css

importF.css

qbus.js

cmjs.exe

screen.css

common.css

default.css

departsf.css

cmjs.exe

cmjs.exe

analytics.js

main_title.gif

top_logo_under.gif

search_title.gif

bus_map.gif

top_img.gif

nishitetsu.jpg

kyushu.jpg

kitashiei.jpg

jr.jpg

showa.jpg

yutoku.gif

sagacity.jpg

kenei.jpg

saihi.jpg

shimatetsu.jpg

sankou_bus.jpg

kumaden.jpg

kumamoto_toshi.jpg

oitabus.jpg

oitakotsu.jpg

hitabus.jpg

kamenoi.jpg

miyazaki.jpg

kagosima.jpg

nangoku.jpg

kagoshima_siei.jpg

bn_news.gif

mobile_title.gif

mobile_qr.gif

bn_link.gif

bana_sanq_s.png

bn_atbus-de.gif