Access jocr.jp. ラジオ関西 AM558 FM91.1

jocr.jp screenshot

24

Performance

Renders faster than
43% of other websites
80

Accessibility

Visual factors better than
that of 50% of websites
75

Best Practices

More advanced features
available than in
36% of websites
100

SEO

Google-friendlier than
95% of websites

First Response

508 ms

Resources Loaded

10.3 sec

Page Rendered

649 ms

jocr.jp screenshot

About Website

Click here to check amazing Jocr content for Japan. Otherwise, check out these important facts you probably never knew about jocr.jp

海の見える放送局ラジオ関西のホームページ

Visit jocr.jp

Key Findings

We analyzed Jocr.jp page load time and found that the first response time was 508 ms and then it took 11 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.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.129

82/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

index.html

508 ms

jocr.css

330 ms

index.css

341 ms

widget_detail.css

352 ms

jquery.min.js

32 ms

Our browser made a total of 171 requests to load all elements on the main page. We found that 77% of them (131 requests) were addressed to the original Jocr.jp, 4% (7 requests) were made to Pagead2.googlesyndication.com and 4% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Jocr.jp.

Content Size

1.6 MB

After Optimization

1.3 MB

In fact, the total size of Jocr.jp 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 32.1 kB

Original 42.7 kB
After minification 37.1 kB
After compression 10.6 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 5.5 kB, which is 13% 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 32.1 kB or 75% of the original size.

Image Optimization

-13%

Potential reduce by 165.4 kB

Original 1.3 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. Obviously, Jocr needs image optimization as it can save up to 165.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 79.3 kB

Original 201.7 kB
After minification 199.8 kB
After compression 122.4 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 79.3 kB or 39% of the original size.

CSS Optimization

-80%

Potential reduce by 26.0 kB

Original 32.4 kB
After minification 20.3 kB
After compression 6.4 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. Jocr.jp needs all CSS files to be minified and compressed as it can save up to 26.0 kB or 80% of the original size.

Requests Now

170

After Optimization

123

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

High

Links do not have a discernible name

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

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

N/A
Encoding

SHIFT_JIS

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

jocr.jp

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