Access 489.fm. さくら高速バス　|　高速バス・夜行バス予約

489.fm screenshot

32

Performance

Renders faster than
52% of other websites
63

Accessibility

Visual factors better than
that of 28% of websites
75

Best Practices

More advanced features
available than in
36% of websites
93

SEO

Google-friendlier than
84% of websites

First Response

511 ms

Resources Loaded

15.4 sec

Page Rendered

337 ms

489.fm screenshot

About Website

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

高速バス・夜行バス・深夜バス予約のさくら高速バス（株式会社さくら観光）。コンセント付き、女性専用車や3列シート、格安〜高級まで豊富な便数・バスタイプからお好きな高速バス・夜行バスをお選びください。座席指定はもちろん、キャンセル待ちもできる高速バス予約サイト。青森・盛岡・山形・仙台・福島・会津・金沢・富山・名古屋・京都・大阪−東京・横浜間の人気路線もラインナップ。便ごとの安全装備も掲載！

Visit 489.fm

Key Findings

We analyzed 489.fm page load time and found that the first response time was 511 ms and then it took 15.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.25

50/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

489.fm

511 ms

www.489.fm

786 ms

import.css

309 ms

calendar.css

327 ms

common.js

329 ms

Our browser made a total of 212 requests to load all elements on the main page. We found that 96% of them (203 requests) were addressed to the original 489.fm, 1% (2 requests) were made to Google-analytics.com and 1% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain 489.fm.

Content Size

1.6 MB

After Optimization

1.3 MB

In fact, the total size of 489.fm main page is 1.6 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 75.0 kB

Original 88.7 kB
After minification 72.9 kB
After compression 13.7 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 15.8 kB, which is 18% 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 75.0 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 34.4 kB

Original 1.2 MB
After minification 1.2 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. 489 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 150.8 kB

Original 234.3 kB
After minification 222.7 kB
After compression 83.5 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 150.8 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 46.1 kB

Original 56.0 kB
After minification 51.1 kB
After compression 9.9 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. 489.fm needs all CSS files to be minified and compressed as it can save up to 46.1 kB or 82% of the original size.

Requests Now

210

After Optimization

134

The browser has sent 210 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 489. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 7 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 the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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.

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

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 489.fm 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 489.fm 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

489.fm

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