Tools & Wizards About Us
t-cn.gr.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

t-cn.gr.jp

豊田市コンサートホール・能楽堂｜豊田市文化振興財団

Page Load Speed

7.5 sec in total

First Response

1.5 sec

Resources Loaded

5.5 sec

Page Rendered

544 ms

t-cn.gr.jp screenshot

About Website

Welcome to t-cn.gr.jp homepage info - get ready to check T Cn best content for Japan right away, or after learning these important things about t-cn.gr.jp

豊田市文化振興財団 豊田市コンサートホール・能楽堂/愛知県の音楽チケット情報　オーケストラ・クラシック・能楽・狂言

Visit t-cn.gr.jp

Key Findings

We analyzed T-cn.gr.jp page load time and found that the first response time was 1.5 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

t-cn.gr.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value22.8 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value1,910 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

www.t-cn.gr.jp

1455 ms

js

66 ms

style.css

177 ms

slick.css

351 ms

slick-theme.css

513 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 76% of them (57 requests) were addressed to the original T-cn.gr.jp, 7% (5 requests) were made to Youtube.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain T-cn.gr.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.4 kB (3%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of T-cn.gr.jp main page is 2.5 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 49.0 kB

  • Original 60.2 kB
  • After minification 49.1 kB
  • After compression 11.2 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 11.2 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 49.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 5.5 kB

  • Original 2.1 MB
  • After minification 2.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. T Cn images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 6.9 kB

  • Original 218.9 kB
  • After minification 218.9 kB
  • After compression 212.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 9.9 kB

  • Original 93.7 kB
  • After minification 92.9 kB
  • After compression 83.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. T-cn.gr.jp needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (38%)

Requests Now

71

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of T Cn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.t-cn.gr.jp

www.t-cn.gr.jp

1455 ms

js

js

66 ms

style.css

style.css

177 ms

slick.css

slick.css

351 ms

slick-theme.css

slick-theme.css

513 ms

style.min.css

style.min.css

539 ms

pagenavi-css.css

pagenavi-css.css

540 ms

jquery.min.js

jquery.min.js

31 ms

common.js

common.js

550 ms

slick.min.js

slick.min.js

676 ms

slidescript.js

slidescript.js

676 ms

wp-embed.min.js

wp-embed.min.js

718 ms

sdk.js

sdk.js

29 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

184 ms

h7u6K9wQENw

h7u6K9wQENw

215 ms

logo.png

logo.png

192 ms

icon1b.png

icon1b.png

193 ms

img1.jpg

img1.jpg

192 ms

img2.jpg

img2.jpg

193 ms

icon2b.png

icon2b.png

507 ms

icon3b.png

icon3b.png

508 ms

icon4b.png

icon4b.png

508 ms

img3.jpg

img3.jpg

509 ms

img4.jpg

img4.jpg

509 ms

img5.jpg

img5.jpg

510 ms

img6.jpg

img6.jpg

582 ms

search.gif

search.gif

583 ms

slide-img1.jpg

slide-img1.jpg

1783 ms

slide-img2.jpg

slide-img2.jpg

1423 ms

slide-img3.jpg

slide-img3.jpg

1463 ms

icon-linkg.png

icon-linkg.png

597 ms

0908_%E7%8B%82%E8%A8%80%E3%81%A5%E3%81%8F%E3%81%97-1200x706.jpg

0908_%E7%8B%82%E8%A8%80%E3%81%A5%E3%81%8F%E3%81%97-1200x706.jpg

1200 ms

0928_%E3%83%99%E3%83%AB%E3%83%AA%E3%83%B3%E3%83%90%E3%83%AD%E3%83%83%E3%82%AF-1200x706.jpg

0928_%E3%83%99%E3%83%AB%E3%83%AA%E3%83%B3%E3%83%90%E3%83%AD%E3%83%83%E3%82%AF-1200x706.jpg

1364 ms

240408%E8%B1%8A%E7%94%B0%E5%B8%82%E3%82%B3%E3%83%B3%E3%82%B5%E3%83%BC%E3%83%88%E3%83%9B%E3%83%BC%E3%83%AB%E6%A0%A1%E4%BA%86A4T_%E5%AE%9A%E6%9C%9F%E6%BC%94%E5%A5%8F%E4%BC%9A_41_o-01-215x300.jpg

240408%E8%B1%8A%E7%94%B0%E5%B8%82%E3%82%B3%E3%83%B3%E3%82%B5%E3%83%BC%E3%83%88%E3%83%9B%E3%83%BC%E3%83%AB%E6%A0%A1%E4%BA%86A4T_%E5%AE%9A%E6%9C%9F%E6%BC%94%E5%A5%8F%E4%BC%9A_41_o-01-215x300.jpg

955 ms

%E5%8B%99%E5%B7%9D%E6%85%A7%E6%82%9F-300x200.jpg

%E5%8B%99%E5%B7%9D%E6%85%A7%E6%82%9F-300x200.jpg

1138 ms

240824%E3%82%8F%E3%81%8F%E3%82%8F%E3%81%8F%E8%83%BD%E6%A5%BD%E4%BD%93%E9%A8%93omote-212x300.jpg

240824%E3%82%8F%E3%81%8F%E3%82%8F%E3%81%8F%E8%83%BD%E6%A5%BD%E4%BD%93%E9%A8%93omote-212x300.jpg

1322 ms

IMG_6351-300x200.jpg

IMG_6351-300x200.jpg

1375 ms

0706%E8%83%BD%E7%8B%82%E8%A8%80%E8%AC%9B%E5%BA%A7%E2%91%A0%E2%91%A1omote-213x300.jpg

0706%E8%83%BD%E7%8B%82%E8%A8%80%E8%AC%9B%E5%BA%A7%E2%91%A0%E2%91%A1omote-213x300.jpg

1505 ms

%E8%86%8F%E8%96%AC%E7%85%89%EF%BC%88%E8%8C%82%E5%B1%B1%E5%AE%B6%EF%BC%89-300x200.jpg

%E8%86%8F%E8%96%AC%E7%85%89%EF%BC%88%E8%8C%82%E5%B1%B1%E5%AE%B6%EF%BC%89-300x200.jpg

1536 ms

%E3%82%AA%E3%83%AB%E3%82%AC%E3%83%B3%E8%AC%9B%E5%BA%A7omote-212x300.jpg

%E3%82%AA%E3%83%AB%E3%82%AC%E3%83%B3%E8%AC%9B%E5%BA%A7omote-212x300.jpg

1547 ms

240131_ks_00267-300x200.jpg

240131_ks_00267-300x200.jpg

1595 ms

icon-logo.jpg

icon-logo.jpg

1640 ms

facility1.jpg

facility1.jpg

1867 ms

facility1-icon.png

facility1-icon.png

1708 ms

facility2.jpg

facility2.jpg

1722 ms

facility2-icon.png

facility2-icon.png

1768 ms

facility3.jpg

facility3.jpg

1714 ms

facility4-icon.png

facility4-icon.png

1774 ms

Oswald-Regular.ttf

Oswald-Regular.ttf

1750 ms

guide1-icon.png

guide1-icon.png

1793 ms

guide2-icon.png

guide2-icon.png

1797 ms

sdk.js

sdk.js

9 ms

38 ms

guide3-icon.png

guide3-icon.png

1809 ms

banner1.jpg

banner1.jpg

1862 ms

banner2.jpg

banner2.jpg

1863 ms

banner4.jpg

banner4.jpg

1874 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

53 ms

ad_status.js

ad_status.js

228 ms

ZaJ5Zq4tt7_ULyGuxTZ9nk1-N-rwPqn235jhFLf1Hr0.js

ZaJ5Zq4tt7_ULyGuxTZ9nk1-N-rwPqn235jhFLf1Hr0.js

177 ms

embed.js

embed.js

89 ms

organ3_02-300x223.jpg

organ3_02-300x223.jpg

1611 ms

noh_p4.gif

noh_p4.gif

1621 ms

noh_butai-300x184.gif

noh_butai-300x184.gif

1671 ms

banner3.jpg

banner3.jpg

1726 ms

logo-bunshin.png

logo-bunshin.png

1717 ms

AIdro_lAkx3FcwNuuoYRxHLCudRoZg5Ox-9OtO7hD5pP6F__6w=s68-c-k-c0x00ffffff-no-rj

AIdro_lAkx3FcwNuuoYRxHLCudRoZg5Ox-9OtO7hD5pP6F__6w=s68-c-k-c0x00ffffff-no-rj

226 ms

ajax-loader.gif

ajax-loader.gif

1714 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

152 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

153 ms

id

id

33 ms

Create

Create

44 ms

GenerateIT

GenerateIT

15 ms

Accessibility Review

t-cn.gr.jp accessibility score

74

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

t-cn.gr.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

t-cn.gr.jp SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

t-cn.gr.jp

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