Tools & Wizards About Us
inunekoningen2.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

inunekoningen2.com

映画『犬と猫と人間2-動物たちの大震災』公式サイト

Page Load Speed

3.5 sec in total

First Response

606 ms

Resources Loaded

2.7 sec

Page Rendered

186 ms

inunekoningen2.com screenshot

About Website

Welcome to inunekoningen2.com homepage info - get ready to check Inunekoningen 2 best content right away, or after learning these important things about inunekoningen2.com

映画『犬と猫と人間2-動物たちの大震災』公式サイト

Visit inunekoningen2.com

Key Findings

We analyzed Inunekoningen2.com page load time and found that the first response time was 606 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

inunekoningen2.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

inunekoningen2.com

606 ms

rest.css

191 ms

index.css

333 ms

jquery-1.8.2.min.js

575 ms

jquery.automaticRollover.js

388 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 59% of them (41 requests) were addressed to the original Inunekoningen2.com, 30% (21 requests) were made to Platform.twitter.com and 7% (5 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Inunekoningen2.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.1 kB (31%)

Content Size

280.8 kB

After Optimization

193.7 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Inunekoningen2.com main page is 280.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 181.9 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-13%

Potential reduce by 23.4 kB

  • Original 181.9 kB
  • After minification 158.5 kB

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. Obviously, Inunekoningen 2 needs image optimization as it can save up to 23.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 61.8 kB

  • Original 95.8 kB
  • After minification 94.4 kB
  • After compression 34.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 61.8 kB or 65% of the original size.

CSS Optimization

-61%

Potential reduce by 1.9 kB

  • Original 3.1 kB
  • After minification 2.5 kB
  • After compression 1.2 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. Inunekoningen2.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (65%)

Requests Now

69

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inunekoningen2.com

inunekoningen2.com

606 ms

rest.css

rest.css

191 ms

index.css

index.css

333 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

575 ms

jquery.automaticRollover.js

jquery.automaticRollover.js

388 ms

widgets.js

widgets.js

45 ms

index_main.gif

index_main.gif

1145 ms

menu_bg.png

menu_bg.png

213 ms

menu_news_off.gif

menu_news_off.gif

169 ms

menu_intro_off.gif

menu_intro_off.gif

191 ms

menu_staff_off.gif

menu_staff_off.gif

372 ms

menu_cast_off.gif

menu_cast_off.gif

384 ms

menu_facts_off.gif

menu_facts_off.gif

387 ms

menu_comments_off.gif

menu_comments_off.gif

383 ms

menu_trailer_off.gif

menu_trailer_off.gif

395 ms

menu_theater_off.gif

menu_theater_off.gif

544 ms

menu_contact_off.gif

menu_contact_off.gif

580 ms

index_title_logo.png

index_title_logo.png

763 ms

index_main_copy.png

index_main_copy.png

774 ms

index_story_copy.png

index_story_copy.png

784 ms

index_roadshow2.png

index_roadshow2.png

872 ms

index_beling.gif

index_beling.gif

774 ms

banner_merumaga2.gif

banner_merumaga2.gif

954 ms

banner_inuneko.jpg

banner_inuneko.jpg

962 ms

banner_inuneko_txt.gif

banner_inuneko_txt.gif

961 ms

bannew_workshop.jpg

bannew_workshop.jpg

980 ms

index_jyouei.png

index_jyouei.png

1038 ms

banner_fb.gif

banner_fb.gif

1146 ms

banner_oendan.jpg

banner_oendan.jpg

1154 ms

banner_inuneko2.jpg

banner_inuneko2.jpg

1153 ms

index_banner_txt.png

index_banner_txt.png

1177 ms

follow_director.png

follow_director.png

1203 ms

follo_producer.png

follo_producer.png

1449 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

142 ms

like.php

like.php

187 ms

menu_news_on.gif

menu_news_on.gif

1272 ms

menu_intro_on.gif

menu_intro_on.gif

1278 ms

menu_staff_on.gif

menu_staff_on.gif

1279 ms

menu_cast_on.gif

menu_cast_on.gif

1307 ms

menu_facts_on.gif

menu_facts_on.gif

1303 ms

menu_comments_on.gif

menu_comments_on.gif

1462 ms

menu_trailer_on.gif

menu_trailer_on.gif

1469 ms

menu_theater_on.gif

menu_theater_on.gif

1469 ms

menu_contact_on.gif

menu_contact_on.gif

1467 ms

settings

settings

72 ms

Ae7SCMH5XFP.js

Ae7SCMH5XFP.js

24 ms

FEppCFCt76d.png

FEppCFCt76d.png

24 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

21 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

41 ms

embeds

embeds

22 ms

embeds

embeds

54 ms

embeds

embeds

74 ms

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

50 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

61 ms

search

search

74 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

22 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

43 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

46 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

44 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

73 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

77 ms

_buildManifest.js

_buildManifest.js

86 ms

_ssgManifest.js

_ssgManifest.js

87 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

23 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

42 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

27 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

56 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

25 ms

Accessibility Review

inunekoningen2.com accessibility score

65

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

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

Best Practices

inunekoningen2.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inunekoningen2.com SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inunekoningen2.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 Inunekoningen2.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

inunekoningen2.com

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