Tools & Wizards About Us
geigeki.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

geigeki.jp

東京芸術劇場

Page Load Speed

4.2 sec in total

First Response

703 ms

Resources Loaded

3.4 sec

Page Rendered

178 ms

geigeki.jp screenshot

About Website

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

東京芸術劇場オフィシャルウェブサイト。公演情報、チケット、施設の紹介、アクセスなど。

Visit geigeki.jp

Key Findings

We analyzed Geigeki.jp page load time and found that the first response time was 703 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

geigeki.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.519

15/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

geigeki.jp

703 ms

gtm.js

64 ms

common.css

205 ms

minimalist.css

354 ms

lang.css

397 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 70% of them (58 requests) were addressed to the original Geigeki.jp, 6% (5 requests) were made to Google.com and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Geigeki.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 46.9 kB

  • Original 60.2 kB
  • After minification 52.1 kB
  • After compression 13.3 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 8.1 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 46.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 1.2 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. Geigeki images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 21.2 kB

  • Original 245.4 kB
  • After minification 239.7 kB
  • After compression 224.2 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

-62%

Potential reduce by 21.9 kB

  • Original 35.5 kB
  • After minification 29.9 kB
  • After compression 13.6 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. Geigeki.jp needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (48%)

Requests Now

82

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geigeki.jp

geigeki.jp

703 ms

gtm.js

gtm.js

64 ms

common.css

common.css

205 ms

minimalist.css

minimalist.css

354 ms

lang.css

lang.css

397 ms

top_v3.css

top_v3.css

388 ms

skin.css

skin.css

388 ms

cal.css

cal.css

391 ms

ge_ch.css

ge_ch.css

399 ms

jquery.min.js

jquery.min.js

14 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

704 ms

rollover.js

rollover.js

573 ms

jquery.droppy.js

jquery.droppy.js

573 ms

cal.js

cal.js

575 ms

popup.js

popup.js

590 ms

s3Slider.js

s3Slider.js

594 ms

tab.js

tab.js

773 ms

lang.js

lang.js

775 ms

google-search.js

google-search.js

782 ms

ytag.js

ytag.js

1015 ms

destination

destination

69 ms

uwt.js

uwt.js

14 ms

adsct

adsct

166 ms

adsct

adsct

194 ms

adsct

adsct

194 ms

adsct

adsct

120 ms

js

js

38 ms

js

js

77 ms

logo.gif

logo.gif

254 ms

btn_visit_off.jpg

btn_visit_off.jpg

252 ms

rent_off.jpg

rent_off.jpg

252 ms

bnr_kifu_kyousan.jpg

bnr_kifu_kyousan.jpg

254 ms

TMF2023.jpg

TMF2023.jpg

390 ms

banner_tominfes_2023.jpg

banner_tominfes_2023.jpg

390 ms

g_menu01_off.jpg

g_menu01_off.jpg

388 ms

g_menu02_off.jpg

g_menu02_off.jpg

390 ms

g_menu03_off.jpg

g_menu03_off.jpg

396 ms

lunch_156.jpg

lunch_156.jpg

778 ms

top_key.jpg

top_key.jpg

1074 ms

top_key.jpg

top_key.jpg

933 ms

top_key.jpg

top_key.jpg

751 ms

top_key.jpg

top_key.jpg

1120 ms

top_key.jpg

top_key.jpg

780 ms

top_key_2.jpg

top_key_2.jpg

939 ms

top_key_2.jpg

top_key_2.jpg

1167 ms

e327_39.jpg

e327_39.jpg

976 ms

c284-9_39.jpg

c284-9_39.jpg

1119 ms

c284-10_39.jpg

c284-10_39.jpg

1125 ms

c292_39_2.jpg

c292_39_2.jpg

1171 ms

t364_39_2.jpg

t364_39_2.jpg

1251 ms

c291_39_2.jpg

c291_39_2.jpg

1305 ms

movie06.jpg

movie06.jpg

1308 ms

movie09.jpg

movie09.jpg

1312 ms

movie02.jpg

movie02.jpg

1362 ms

movie03.jpg

movie03.jpg

1366 ms

ch_button01_off.jpg

ch_button01_off.jpg

1427 ms

ch_button02_off.jpg

ch_button02_off.jpg

1490 ms

ch_button03_off.jpg

ch_button03_off.jpg

1494 ms

x_logo.svg

x_logo.svg

1498 ms

facebook_logo.svg

facebook_logo.svg

1556 ms

instagram_logo.svg

instagram_logo.svg

1561 ms

youtube_logo.svg

youtube_logo.svg

1603 ms

all.js

all.js

129 ms

fbevents.js

fbevents.js

96 ms

cse.js

cse.js

200 ms

geigeki_ch.png

geigeki_ch.png

1488 ms

mo06_on.jpg

mo06_on.jpg

1491 ms

analytics.js

analytics.js

108 ms

mo09_off.jpg

mo09_off.jpg

1438 ms

mo02_off.jpg

mo02_off.jpg

1504 ms

mo03_off.jpg

mo03_off.jpg

1508 ms

all.js

all.js

72 ms

prev-vertical.png

prev-vertical.png

1525 ms

collect

collect

49 ms

146 ms

next-vertical.png

next-vertical.png

1477 ms

cse_element__ja.js

cse_element__ja.js

32 ms

default+ja.css

default+ja.css

101 ms

minimalist.css

minimalist.css

107 ms

collect

collect

90 ms

async-ads.js

async-ads.js

43 ms

branding.png

branding.png

20 ms

clear.png

clear.png

26 ms

Accessibility Review

geigeki.jp accessibility score

96

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 input fields do not have accessible names

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

geigeki.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

geigeki.jp SEO score

83

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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

geigeki.jp

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