Tools & Wizards About Us
disneymobile.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

disneymobile.jp

ディズニー公式｜Disney.jp

Page Load Speed

8.2 sec in total

First Response

407 ms

Resources Loaded

6.9 sec

Page Rendered

862 ms

disneymobile.jp screenshot

About Website

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

ディズニーの公式サイト。映画、ブルーレイ・オンデマンド、音楽、イベント・ライブ、パーク＆リゾート、モバイル、ゲーム、キャラクター、ショッピングなどディズニーの最新情報をお届けします。 － ディズニー公式｜Disney.jp

Visit disneymobile.jp

Key Findings

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

Performance Metrics

disneymobile.jp performance score

0

Network Requests Diagram

disneymobile.jp

407 ms

mobile.html

1252 ms

satelliteLib-fb71f34918a64257e056487a84d25f1f5729d732.js

86 ms

main.css

481 ms

jquery.js

607 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Disneymobile.jp, 87% (53 requests) were made to Disney.co.jp and 3% (2 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Disney.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (34%)

Content Size

4.1 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 83.6 kB

  • Original 94.9 kB
  • After minification 66.9 kB
  • After compression 11.3 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 28.0 kB, which is 30% 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 83.6 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 136.7 kB

  • Original 2.6 MB
  • After minification 2.5 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. Disney Mobile images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 768.7 kB

  • Original 957.1 kB
  • After minification 614.1 kB
  • After compression 188.4 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 768.7 kB or 80% of the original size.

CSS Optimization

-89%

Potential reduce by 421.8 kB

  • Original 473.0 kB
  • After minification 375.4 kB
  • After compression 51.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. Disneymobile.jp needs all CSS files to be minified and compressed as it can save up to 421.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (24%)

Requests Now

58

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

disneymobile.jp

disneymobile.jp

407 ms

mobile.html

mobile.html

1252 ms

satelliteLib-fb71f34918a64257e056487a84d25f1f5729d732.js

satelliteLib-fb71f34918a64257e056487a84d25f1f5729d732.js

86 ms

main.css

main.css

481 ms

jquery.js

jquery.js

607 ms

utils.js

utils.js

646 ms

granite.js

granite.js

216 ms

jquery.js

jquery.js

473 ms

main.js

main.js

564 ms

master.css

master.css

821 ms

modules.css

modules.css

983 ms

news.css

news.css

935 ms

recommend_movie_auto.css

recommend_movie_auto.css

760 ms

mobile.css

mobile.css

1030 ms

common.js

common.js

1240 ms

sprite.png

sprite.png

221 ms

bnr_shopping_02.jpg

bnr_shopping_02.jpg

342 ms

bnr_shopping_05.jpg

bnr_shopping_05.jpg

263 ms

bnr_shopping_03.jpg

bnr_shopping_03.jpg

246 ms

bnr_shopping_04.jpg

bnr_shopping_04.jpg

238 ms

bnr_ticket_160229_01.jpg

bnr_ticket_160229_01.jpg

466 ms

bnr_fan_151021.jpg

bnr_fan_151021.jpg

466 ms

bnr_ticket_160229_02.jpg

bnr_ticket_160229_02.jpg

456 ms

bnr_ticket_160311.jpg

bnr_ticket_160311.jpg

1199 ms

bnr_park_151225_01.jpg

bnr_park_151225_01.jpg

739 ms

bnr_park_151225_02.jpg

bnr_park_151225_02.jpg

564 ms

bnr_park_160105_01.jpg

bnr_park_160105_01.jpg

689 ms

bnr_park_150701.jpg

bnr_park_150701.jpg

962 ms

bnr_movie_151113_01.jpg

bnr_movie_151113_01.jpg

690 ms

bnr_movie_160224_01.jpg

bnr_movie_160224_01.jpg

776 ms

bnr_movie_151110_01.jpg

bnr_movie_151110_01.jpg

959 ms

bnr_tv_05.jpg

bnr_tv_05.jpg

963 ms

bnr_tv_08.jpg

bnr_tv_08.jpg

962 ms

bnr_tv_03.jpg

bnr_tv_03.jpg

1034 ms

bnr_tb_09.jpg

bnr_tb_09.jpg

1124 ms

bnr_mobile_13.jpg

bnr_mobile_13.jpg

1103 ms

bnr_mobile_12.jpg

bnr_mobile_12.jpg

1235 ms

bnr_mobile_14.jpg

bnr_mobile_14.jpg

1159 ms

bnr_mobile_04.jpg

bnr_mobile_04.jpg

1235 ms

bnr_member_05.jpg

bnr_member_05.jpg

1466 ms

bnr_member_03.jpg

bnr_member_03.jpg

1371 ms

bnr_member_02.jpg

bnr_member_02.jpg

1361 ms

logo-header-mobile.png

logo-header-mobile.png

1400 ms

1454032394361.jpg

1454032394361.jpg

2992 ms

1454032394361.png

1454032394361.png

1635 ms

1454032394361.jpg

1454032394361.jpg

2541 ms

1454032394361.jpg

1454032394361.jpg

2325 ms

1446086408714.jpg

1446086408714.jpg

3722 ms

1446086408714.png

1446086408714.png

1883 ms

1446086408714.jpg

1446086408714.jpg

3245 ms

s_retargeting.js

s_retargeting.js

617 ms

conversion.js

conversion.js

35 ms

s-code-contents-8915052bb13339d2cabb793e91bc4da29eafeede.js

s-code-contents-8915052bb13339d2cabb793e91bc4da29eafeede.js

51 ms

1446086408714.png

1446086408714.png

1904 ms

1446086408714.jpg

1446086408714.jpg

3742 ms

1446086408714.png

1446086408714.png

2313 ms

1452748549587.jpg

1452748549587.jpg

3297 ms

1444708415952.png

1444708415952.png

2501 ms

s24524805764667

s24524805764667

9 ms

155 ms

47 ms

SEO Factors

disneymobile.jp SEO score

0

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

disneymobile.jp

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