Tools & Wizards About Us
inagawa-kaidan.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

inagawa-kaidan.com

稲川淳二の怪談ナイト オフィシャルサイト

Page Load Speed

8 sec in total

First Response

1.3 sec

Resources Loaded

6.3 sec

Page Rendered

465 ms

inagawa-kaidan.com screenshot

About Website

Click here to check amazing Inagawa Kaidan content for Japan. Otherwise, check out these important facts you probably never knew about inagawa-kaidan.com

もはや夏の風物詩となった「稲川淳二の怪談ナイト」。公演日程やツアーグッズの紹介、スタッフブログなどをお届けします。

Visit inagawa-kaidan.com

Key Findings

We analyzed Inagawa-kaidan.com page load time and found that the first response time was 1.3 sec and then it took 6.8 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

inagawa-kaidan.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value31.9 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.227

55/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

Network Requests Diagram

www.inagawa-kaidan.com

1269 ms

gtm.js

77 ms

viewport-extra.min.js

58 ms

swiper.min.css

49 ms

font-awesome.min.css

41 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 55% of them (42 requests) were addressed to the original Inagawa-kaidan.com, 14% (11 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Inagawa-kaidan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.3 kB (4%)

Content Size

4.9 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inagawa-kaidan.com main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 35.2 kB

  • Original 45.9 kB
  • After minification 44.9 kB
  • After compression 10.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. 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 35.2 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 137.2 kB

  • Original 4.5 MB
  • After minification 4.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. Inagawa Kaidan images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 36.0 kB

  • Original 278.5 kB
  • After minification 278.3 kB
  • After compression 242.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 36.0 kB or 13% of the original size.

CSS Optimization

-3%

Potential reduce by 2.9 kB

  • Original 98.3 kB
  • After minification 98.3 kB
  • After compression 95.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. Inagawa-kaidan.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (58%)

Requests Now

64

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.inagawa-kaidan.com

www.inagawa-kaidan.com

1269 ms

gtm.js

gtm.js

77 ms

viewport-extra.min.js

viewport-extra.min.js

58 ms

swiper.min.css

swiper.min.css

49 ms

font-awesome.min.css

font-awesome.min.css

41 ms

all.css

all.css

41 ms

main.css

main.css

242 ms

style.min.css

style.min.css

351 ms

styles.css

styles.css

524 ms

jquery.fancybox-1.3.8.min.css

jquery.fancybox-1.3.8.min.css

667 ms

css3_black.css

css3_black.css

669 ms

index.js

index.js

673 ms

index.js

index.js

694 ms

jquery.min.js

jquery.min.js

976 ms

jquery-migrate.min.js

jquery-migrate.min.js

776 ms

jquery.fancybox-1.3.8.min.js

jquery.fancybox-1.3.8.min.js

838 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

845 ms

pagetop.js

pagetop.js

844 ms

jquery.smoothScroll.js

jquery.smoothScroll.js

865 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

972 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

1010 ms

meanmenu.css

meanmenu.css

1016 ms

jquery.meanmenu.min.js

jquery.meanmenu.min.js

1014 ms

swiper.min.js

swiper.min.js

62 ms

js

js

54 ms

analytics.js

analytics.js

18 ms

collect

collect

14 ms

reset.css

reset.css

801 ms

base.css

base.css

932 ms

common.css

common.css

948 ms

layout.css

layout.css

944 ms

top.css

top.css

952 ms

css2

css2

28 ms

sitelogo.png

sitelogo.png

588 ms

top_img01.jpg

top_img01.jpg

1176 ms

top_img02.jpg

top_img02.jpg

993 ms

top_img03.jpg

top_img03.jpg

1369 ms

top_img04.jpg

top_img04.jpg

1267 ms

bnr_mnt-online.jpg

bnr_mnt-online.jpg

686 ms

resale-no.jpg

resale-no.jpg

843 ms

topics_2023.jpg

topics_2023.jpg

1349 ms

bnr_mnt-online_small.jpg

bnr_mnt-online_small.jpg

957 ms

bnr_info.jpg

bnr_info.jpg

1128 ms

bnr_twitter.jpg

bnr_twitter.jpg

1197 ms

bnr_official-site.jpg

bnr_official-site.jpg

1306 ms

footer_site_logo.png

footer_site_logo.png

1359 ms

btn_pagetop.png

btn_pagetop.png

1398 ms

sdk.js

sdk.js

58 ms

SoPMMv63o3c

SoPMMv63o3c

182 ms

back_header.png

back_header.png

1779 ms

back_gnav.png

back_gnav.png

1821 ms

navi.png

navi.png

1521 ms

title.png

title.png

1699 ms

back_footer.jpg

back_footer.jpg

1755 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

103 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

532 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

541 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf

538 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

534 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf

550 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

614 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf

785 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

788 ms

sdk.js

sdk.js

9 ms

42 ms

www-player.css

www-player.css

25 ms

www-embed-player.js

www-embed-player.js

67 ms

base.js

base.js

132 ms

ad_status.js

ad_status.js

217 ms

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

197 ms

embed.js

embed.js

105 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

45 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

44 ms

id

id

37 ms

Create

Create

107 ms

GenerateIT

GenerateIT

15 ms

Accessibility Review

inagawa-kaidan.com accessibility score

95

Accessibility Issues

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

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

inagawa-kaidan.com 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

inagawa-kaidan.com SEO score

90

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

inagawa-kaidan.com

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