Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

jocr.jp

ラジオ関西 AM558 FM91.1

Page Load Speed

25.7 sec in total

First Response

1.1 sec

Resources Loaded

23.9 sec

Page Rendered

699 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 1.1 sec and then it took 24.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

jocr.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value33.3 s

0/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

jocr.jp

1084 ms

js

66 ms

style.min.css

621 ms

normalize.css

611 ms

base.css

728 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 88% of them (115 requests) were addressed to the original Jocr.jp, 3% (4 requests) were made to Api.popin.cc and 2% (3 requests) were made to Log.popin.cc. The less responsive or slowest element that took the longest time to load (8.7 sec) belongs to the original domain Jocr.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 473.3 kB (6%)

Content Size

7.9 MB

After Optimization

7.4 MB

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

HTML Optimization

-84%

Potential reduce by 88.0 kB

  • Original 104.9 kB
  • After minification 85.0 kB
  • After compression 16.9 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 19.9 kB, which is 19% 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 88.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 30.4 kB

  • Original 7.2 MB
  • After minification 7.1 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. Jocr images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 347.8 kB

  • Original 535.2 kB
  • After minification 469.0 kB
  • After compression 187.3 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 347.8 kB or 65% of the original size.

CSS Optimization

-15%

Potential reduce by 6.9 kB

  • Original 45.7 kB
  • After minification 45.5 kB
  • After compression 38.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. Jocr.jp needs all CSS files to be minified and compressed as it can save up to 6.9 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (33%)

Requests Now

129

After Optimization

87

The browser has sent 129 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 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

jocr.jp accessibility score

82

Accessibility Issues

ARIA

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.

Impact

Issue

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.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

Best Practices

jocr.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jocr.jp SEO score

100

Search Engine Optimization Advices

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

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

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