Access gekijourei.jp. 映画『劇場霊』オフィシャルサイト - Gekijourei.jp

gekijourei.jp screenshot

22

Performance

Renders faster than
40% of other websites
56

Accessibility

Visual factors better than
that of 23% of websites
92

Best Practices

More advanced features
available than in
81% of websites
86

SEO

Google-friendlier than
60% of websites

First Response

505 ms

Resources Loaded

18.7 sec

Page Rendered

1.3 sec

gekijourei.jp screenshot

About Website

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

『女優霊』から20年―新たなる恐怖の幕が開く映画『劇場霊』11月21日（土）全国ロードショー

Visit gekijourei.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

gekijourei.jp

505 ms

screen.css

614 ms

line-button.js

529 ms

80717.js

601 ms

text.jpg

656 ms

Our browser made a total of 188 requests to load all elements on the main page. We found that 82% of them (154 requests) were addressed to the original Gekijourei.jp, 3% (6 requests) were made to Google.com and 3% (5 requests) were made to Secure.eiga.com. The less responsive or slowest element that took the longest time to load (8 sec) belongs to the original domain Gekijourei.jp.

Content Size

8.4 MB

After Optimization

7.6 MB

In fact, the total size of Gekijourei.jp main page is 8.4 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 7.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 118.5 kB

Original 131.4 kB
After minification 129.1 kB
After compression 12.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 118.5 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 44.7 kB

Original 7.4 MB
After minification 7.4 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. Gekijourei images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 623.9 kB

Original 836.9 kB
After minification 632.3 kB
After compression 213.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 623.9 kB or 75% of the original size.

CSS Optimization

-78%

Potential reduce by 15.1 kB

Original 19.5 kB
After minification 19.5 kB
After compression 4.3 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. Gekijourei.jp needs all CSS files to be minified and compressed as it can save up to 15.1 kB or 78% of the original size.

Requests Now

186

After Optimization

147

The browser has sent 186 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gekijourei. 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 as a result speed up the page load time.

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Search Engine Optimization Advices

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

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

gekijourei.jp

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