Access kyodotokai.co.jp. キョードー東海オフィシャルウェブサイト [KYODO TOKAI OFFICIAL WEB SITE] 愛知/岐阜/三重/静岡/名古屋を中心としたコンサート、演劇、ミュージカルはこちら

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value41.2 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.494

17/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

kyodotokai.co.jp

4404 ms

default.css

323 ms

layout.css

643 ms

base.js

341 ms

jsapi

27 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 77% of them (75 requests) were addressed to the original Kyodotokai.co.jp, 5% (5 requests) were made to Google.com and 4% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (10.9 sec) belongs to the original domain Kyodotokai.co.jp.

Content Size

8.0 MB

After Optimization

6.9 MB

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

HTML Optimization

-88%

Potential reduce by 164.7 kB

Original 187.3 kB
After minification 146.2 kB
After compression 22.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 41.1 kB, which is 22% 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 164.7 kB or 88% of the original size.

Image Optimization

-7%

Potential reduce by 545.0 kB

Original 7.3 MB
After minification 6.7 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. KYODO TOKAI images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 400.0 kB

Original 531.5 kB
After minification 404.8 kB
After compression 131.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 400.0 kB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 35.1 kB

Original 42.4 kB
After minification 37.8 kB
After compression 7.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. Kyodotokai.co.jp needs all CSS files to be minified and compressed as it can save up to 35.1 kB or 83% of the original size.

Requests Now

After Optimization

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KYODO TOKAI. 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 5 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 input fields do not have accessible names

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 experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

N/A
Language Claimed

JA
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kyodotokai.co.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Kyodotokai.co.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 description is not detected on the main page of KYODO TOKAI. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

キョードー東海オフィシャルウェブサイト [KYODO TOKAI OFFICIAL WEB SITE] 愛知/岐阜/三重/静岡/名古屋を中心としたコンサート、演劇、ミュージカルはこちら

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

kyodotokai.co.jp

default.css

layout.css

base.js

jsapi

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

{{url}}

Accessibility Review

Accessibility Issues

Best Practices

Areas of Improvement

SEO Factors

Search Engine Optimization Advices

Language and Encoding

Language Detected

Language Claimed

Encoding

Social Sharing Optimization

{{og_title}}