Tools & Wizards About Us
hungergames.jp screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

hungergames.jp

角川映画

Page Load Speed

6.1 sec in total

First Response

764 ms

Resources Loaded

5 sec

Page Rendered

307 ms

hungergames.jp screenshot

About Website

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

映画『ハンガー・ゲーム FINAL： レボリューション』オフィシャルサイト　4.13(水) ブルーレイ＆DVD発売！

Visit hungergames.jp

Key Findings

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

Performance Metrics

hungergames.jp performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

hungergames.jp

764 ms

sp.js

294 ms

reset.css

296 ms

common.css

338 ms

top.css

345 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 91% of them (42 requests) were addressed to the original Hungergames.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Hungergames.jp.

Page Optimization Overview & Recommendations

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

Content Size

916.4 kB

After Optimization

857.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hungergames.jp main page is 916.4 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. 20% of websites need less resources to load. Images take 845.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.3 kB

  • Original 8.4 kB
  • After minification 6.5 kB
  • After compression 2.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 2.0 kB, which is 23% 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 6.3 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 13.7 kB

  • Original 845.4 kB
  • After minification 831.7 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. Hungergames images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-76%

Potential reduce by 7.3 kB

  • Original 9.6 kB
  • After minification 6.6 kB
  • After compression 2.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. Hungergames.jp needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (25%)

Requests Now

44

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hungergames.jp

hungergames.jp

764 ms

sp.js

sp.js

294 ms

reset.css

reset.css

296 ms

common.css

common.css

338 ms

top.css

top.css

345 ms

videoplayer.css

videoplayer.css

358 ms

css

css

26 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1123 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

583 ms

jquery.imagesloaded.min.js

jquery.imagesloaded.min.js

440 ms

preloader.js

preloader.js

508 ms

videoplayer.js

videoplayer.js

685 ms

init.js

init.js

533 ms

loader.gif

loader.gif

177 ms

top.jpg

top.jpg

3208 ms

navi_bg.png

navi_bg.png

293 ms

home_on.jpg

home_on.jpg

190 ms

trailer_off.jpg

trailer_off.jpg

176 ms

trailer_on.jpg

trailer_on.jpg

155 ms

story_off.jpg

story_off.jpg

301 ms

story_on.jpg

story_on.jpg

346 ms

cast_off.jpg

cast_off.jpg

347 ms

cast_on.jpg

cast_on.jpg

376 ms

staff_off.jpg

staff_off.jpg

438 ms

staff_on.jpg

staff_on.jpg

446 ms

theater_off.jpg

theater_off.jpg

517 ms

theater_on.jpg

theater_on.jpg

518 ms

tw_off.jpg

tw_off.jpg

561 ms

tw_on.jpg

tw_on.jpg

583 ms

fb_off.jpg

fb_off.jpg

590 ms

fb_on.jpg

fb_on.jpg

687 ms

logo.png

logo.png

1371 ms

day.png

day.png

747 ms

imax3d.png

imax3d.png

873 ms

bddvd_off.png

bddvd_off.png

1175 ms

bddvd_on.png

bddvd_on.png

1203 ms

catch.png

catch.png

938 ms

3.jpg

3.jpg

1019 ms

banner2.png

banner2.png

1118 ms

banner3.png

banner3.png

1159 ms

copy.png

copy.png

1304 ms

analytics.js

analytics.js

35 ms

loading.jpg

loading.jpg

1280 ms

collect

collect

48 ms

collect

collect

72 ms

navi_bg.jpg

navi_bg.jpg

177 ms

Accessibility Review

hungergames.jp accessibility score

93

Accessibility Issues

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

Best Practices

hungergames.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

hungergames.jp SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hungergames.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Hungergames.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

hungergames.jp

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