Access skybus.jp. 【公式】SKY BUS(スカイバス)

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value26.9 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.788

5/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

skybus.jp

931 ms

jquery-1.7.1.min.js

2103 ms

jquery.nivo.slider.js

1800 ms

jquery.Pc2Sp.js

1333 ms

default.css

1358 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 44% of them (59 requests) were addressed to the original Skybus.jp, 20% (26 requests) were made to Pbs.twimg.com and 6% (8 requests) were made to Abs.twimg.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Skybus.jp.

Content Size

1.5 MB

After Optimization

929.4 kB

In fact, the total size of Skybus.jp main page is 1.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. 65% of websites need less resources to load. Images take 709.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.1 kB

Original 19.6 kB
After minification 17.9 kB
After compression 5.4 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 14.1 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 32.8 kB

Original 709.9 kB
After minification 677.1 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. SKY BUS images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 282.4 kB

Original 469.6 kB
After minification 454.7 kB
After compression 187.2 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 282.4 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 274.2 kB

Original 333.8 kB
After minification 325.5 kB
After compression 59.6 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. Skybus.jp needs all CSS files to be minified and compressed as it can save up to 274.2 kB or 82% of the original size.

Requests Now

128

After Optimization

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

Accessibility Issues

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.

High

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

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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 the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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.

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

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

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

N/A
Encoding

UTF-8

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

skybus.jp

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

【公式】SKY BUS(スカイバス)｜2階建て東京観光バス

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

skybus.jp

jquery-1.7.1.min.js

jquery.nivo.slider.js

jquery.Pc2Sp.js

default.css

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

skybus.jp

jquery-1.7.1.min.js

jquery.nivo.slider.js

jquery.Pc2Sp.js

default.css

light.css

dark.css

bar.css

nivo-slider.css

default.css

style.js

widgets.js

back2.jpg

ue2.jpg

menu_back_02.gif

font_size.gif

l.gif

m.gif

s.gif

jpn.gif

eng.gif

koria.gif

china.gif

linebutton_88x20.png

hop_logo.gif

hop_catch.gif

hop_skytree.gif

hop_odaiba.gif

hop_roppongi.gif

root_map.gif

sky_logo.gif

skybus_catch.gif

t01.gif

t02.gif

t03.gif

n01.gif

daiya.jpg

duck.gif

duck_catch.gif

d01.gif

d02.gif

tel.gif

instagram_image.gif