Access onsen.ag. インターネットラジオステーション＜音泉＞

onsen.ag screenshot

5

Performance

Renders faster than
21% of other websites
76

Accessibility

Visual factors better than
that of 43% of websites
83

Best Practices

More advanced features
available than in
56% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

499 ms

Resources Loaded

18.5 sec

Page Rendered

325 ms

onsen.ag screenshot

About Website

Visit onsen.ag now to see the best up-to-date Onsen content for Japan and also check out these interesting facts you probably never knew about onsen.ag

インターネットラジオステーション＜音泉＞はアニメ・ゲーム・声優系を中心としたラジオを配信するサイトです。24時間毎日いつでも好きな時、好きな番組がカンタンに聴けます！移動時や作業中におすすめのスマートフォンアプリでも配信中！音泉プレミアムサポーターだけが楽しめるアプリ限定番組は必聴です！

Visit onsen.ag

Key Findings

We analyzed Onsen.ag page load time and found that the first response time was 499 ms and then it took 18.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value23.0 s

0/100

25%

SI (Speed Index)

Value20.2 s

0/100

10%

TBT (Total Blocking Time)

Value9,820 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.48

18/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

onsen.ag

499 ms

www.onsen.ag

1100 ms

common.css

341 ms

common_in.css

351 ms

mainplayer.css

380 ms

Our browser made a total of 203 requests to load all elements on the main page. We found that 91% of them (185 requests) were addressed to the original Onsen.ag, 2% (4 requests) were made to Platform.twitter.com and 2% (4 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Onsen.ag.

Content Size

4.8 MB

After Optimization

4.1 MB

In fact, the total size of Onsen.ag main page is 4.8 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. 50% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 111.8 kB

Original 130.9 kB
After minification 122.2 kB
After compression 19.1 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 111.8 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 446.9 kB

Original 4.5 MB
After minification 4.0 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. Onsen images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 107.5 kB

Original 148.7 kB
After minification 107.9 kB
After compression 41.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 107.5 kB or 72% of the original size.

CSS Optimization

-81%

Potential reduce by 52.9 kB

Original 65.6 kB
After minification 54.0 kB
After compression 12.8 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. Onsen.ag needs all CSS files to be minified and compressed as it can save up to 52.9 kB or 81% of the original size.

Requests Now

200

After Optimization

138

The browser has sent 200 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onsen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 12 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-*] attributes do not match their roles

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

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

Missing source maps for large first-party JavaScript

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

UTF-8

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

onsen.ag

Open Graph data is detected on the main page of Onsen. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: