Access ybs.jp. YBS山梨放送

ybs.jp screenshot

11

Performance

Renders faster than
24% of other websites
84

Accessibility

Visual factors better than
that of 56% of websites
83

Best Practices

More advanced features
available than in
55% of websites
89

SEO

Google-friendlier than
66% of websites

First Response

1.2 sec

Resources Loaded

11.5 sec

Page Rendered

162 ms

ybs.jp screenshot

About Website

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

YBS山梨放送公式ホームページ。日本テレビ系列局。番組案内、県内ニュース、アナウンサーとイベントの紹介、ライブカメラなど。

Visit ybs.jp

Key Findings

We analyzed Ybs.jp page load time and found that the first response time was 1.2 sec and then it took 11.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)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.6 s

0/100

25%

SI (Speed Index)

Value29.4 s

0/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value1.798

0/100

15%

TTI (Time to Interactive)

Value49.2 s

0/100

10%

ybs.jp

1236 ms

normal.css

748 ms

jquery.js

1327 ms

jquery.marquee.js

381 ms

jquery.droppy.js

381 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 90% of them (132 requests) were addressed to the original Ybs.jp, 2% (3 requests) were made to Google.com and 2% (3 requests) were made to Ads.adjust-net.jp. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Ybs.jp.

Content Size

1.1 MB

After Optimization

812.2 kB

In fact, the total size of Ybs.jp main page is 1.1 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 779.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 69.9 kB

Original 85.5 kB
After minification 81.8 kB
After compression 15.5 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 69.9 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 28.9 kB

Original 779.2 kB
After minification 750.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. Ybs images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 126.9 kB

Original 169.6 kB
After minification 131.6 kB
After compression 42.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 126.9 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 19.2 kB

Original 22.9 kB
After minification 15.8 kB
After compression 3.7 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. Ybs.jp needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 84% of the original size.

Requests Now

140

After Optimization

108

The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ybs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 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

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

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

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

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

ybs.jp

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