Tools & Wizards About Us
009.ph9.jp screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

009.ph9.jp

009 RE:CYBORG （原作:サイボーグ009） 西暦2013年5月22日 Blu-ray&DVD発売

Page Load Speed

5.8 sec in total

First Response

1 sec

Resources Loaded

4.3 sec

Page Rendered

408 ms

009.ph9.jp screenshot

About Website

Click here to check amazing 009 Ph 9 content for Japan. Otherwise, check out these important facts you probably never knew about 009.ph9.jp

西暦2013年5月22日 Blu-ray&DVD発売（西暦2012年10月27日全国公開） 映画『009 RE:CYBORG』公式ウェブサイト。石ノ森章太郎『サイボーグ009』を原作に、神山健治監督が自ら脚本・監督を手がけ、2013年というリアルタイムな現代が舞台の全く新しい物語を生み出します。Official Movie Website.

Visit 009.ph9.jp

Key Findings

We analyzed 009.ph9.jp page load time and found that the first response time was 1 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

009.ph9.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

009.ph9.jp

1036 ms

styles.css

431 ms

widget.js

4 ms

plusone.js

20 ms

base.css

217 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 14% of them (11 requests) were addressed to the original 009.ph9.jp, 23% (19 requests) were made to Platform.twitter.com and 15% (12 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Ph9.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 009.ph9.jp main page is 1.3 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. 80% 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 686.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 23.2 kB

  • Original 32.5 kB
  • After minification 31.5 kB
  • After compression 9.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. 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 23.2 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 20.3 kB

  • Original 686.0 kB
  • After minification 665.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. 009 Ph 9 images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 18.4 kB

  • Original 509.6 kB
  • After minification 509.6 kB
  • After compression 491.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

-17%

Potential reduce by 14.9 kB

  • Original 86.4 kB
  • After minification 83.3 kB
  • After compression 71.5 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. 009.ph9.jp needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

79

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

009.ph9.jp

009.ph9.jp

1036 ms

styles.css

styles.css

431 ms

widget.js

widget.js

4 ms

plusone.js

plusone.js

20 ms

base.css

base.css

217 ms

design.css

design.css

433 ms

ga.js

ga.js

61 ms

bg.jpg

bg.jpg

1280 ms

cr_comment.jpg

cr_comment.jpg

1088 ms

cr_play.jpg

cr_play.jpg

1093 ms

cr_poster.jpg

cr_poster.jpg

1918 ms

009screen.jpg

009screen.jpg

2638 ms

009wallpaper.jpg

009wallpaper.jpg

2164 ms

009wallpaper02.jpg

009wallpaper02.jpg

1277 ms

ph9ch-009-disc.jpg

ph9ch-009-disc.jpg

1284 ms

ph9ch-009-yokoku02.jpg

ph9ch-009-yokoku02.jpg

1464 ms

visual.png

visual.png

880 ms

header.gif

header.gif

1082 ms

slashbg.png

slashbg.png

534 ms

feed.png

feed.png

534 ms

twitter.png

twitter.png

533 ms

facebook.png

facebook.png

534 ms

youtube.png

youtube.png

813 ms

LitZjVQQv8E

LitZjVQQv8E

118 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

22 ms

follow_button.html

follow_button.html

77 ms

__utm.gif

__utm.gif

65 ms

widgets.js

widgets.js

7 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

7 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

37 ms

subscribe_embed

subscribe_embed

97 ms

like.php

like.php

176 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

59 ms

postmessageRelay

postmessageRelay

56 ms

embeds

embeds

398 ms

www-player.css

www-player.css

25 ms

www-embed-player.js

www-embed-player.js

62 ms

base.js

base.js

109 ms

settings

settings

359 ms

www-subscribe-embed_split_v0.css

www-subscribe-embed_split_v0.css

26 ms

www-subscribe-embed_v0.js

www-subscribe-embed_v0.js

70 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

86 ms

rpc:shindig_random.js

rpc:shindig_random.js

26 ms

subscribe_button_branded_lozenge.png

subscribe_button_branded_lozenge.png

20 ms

KKhk6eugt1M.js

KKhk6eugt1M.js

342 ms

FEppCFCt76d.png

FEppCFCt76d.png

376 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

270 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

266 ms

ad_status.js

ad_status.js

203 ms

HRWvHAg5u1ehCJtdrky-PNA-CjIWhbU7xrlveGXuadw.js

HRWvHAg5u1ehCJtdrky-PNA-CjIWhbU7xrlveGXuadw.js

148 ms

embed.js

embed.js

60 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

30 ms

id

id

16 ms

Create

Create

107 ms

PH9

PH9

151 ms

cb=gapi.loaded_3

cb=gapi.loaded_3

4 ms

GenerateIT

GenerateIT

16 ms

border_3.gif

border_3.gif

5 ms

subscribe_embed

subscribe_embed

52 ms

spacer.gif

spacer.gif

6 ms

border_3.gif

border_3.gif

11 ms

bubbleSprite_3.png

bubbleSprite_3.png

10 ms

bubbleDropR_3.png

bubbleDropR_3.png

11 ms

bubbleDropB_3.png

bubbleDropB_3.png

11 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

3 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

21 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

24 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

34 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

47 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

34 ms

_buildManifest.js

_buildManifest.js

47 ms

_ssgManifest.js

_ssgManifest.js

46 ms

www-subscribe-embed-card_v0.css

www-subscribe-embed-card_v0.css

39 ms

www-subscribe-embed-card_v0.js

www-subscribe-embed-card_v0.js

39 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

11 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

11 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

11 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

25 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

26 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

24 ms

Accessibility Review

009.ph9.jp accessibility score

95

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

Best Practices

009.ph9.jp best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

009.ph9.jp SEO score

75

Search Engine Optimization Advices

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 009.ph9.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 009.ph9.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

009.ph9.jp

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