5.1 sec in total
531 ms
4.2 sec
453 ms
Visit tokyodisneyresort.jp now to see the best up-to-date Tokyodisneyresort content for Japan and also check out these interesting facts you probably never knew about tokyodisneyresort.jp
東京ディズニーリゾート・オフィシャルウェブサイトへようこそ。東京ディズニーランド、東京ディズニーシーのアトラクションなどの情報から、チケット、運営カレンダー、ホテルの予約・購入まで、ゲストの皆さんのかけがえのない思い出づくりをサポートします。
Visit tokyodisneyresort.jpWe analyzed Tokyodisneyresort.jp page load time and found that the first response time was 531 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tokyodisneyresort.jp performance score
531 ms
53 ms
97 ms
450 ms
36 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 56% of them (73 requests) were addressed to the original Tokyodisneyresort.jp, 6% (8 requests) were made to Platform.twitter.com and 6% (8 requests) were made to Plugins.mixi.jp. The less responsive or slowest element that took the longest time to load (767 ms) relates to the external source Plugins.mixi.jp.
Page size can be reduced by 1.3 MB (43%)
2.9 MB
1.7 MB
In fact, the total size of Tokyodisneyresort.jp main page is 2.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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 52.5 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 52.5 kB or 78% of the original size.
Potential reduce by 79.1 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. Tokyodisneyresort images are well optimized though.
Potential reduce by 677.8 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 677.8 kB or 68% of the original size.
Potential reduce by 449.0 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. Tokyodisneyresort.jp needs all CSS files to be minified and compressed as it can save up to 449.0 kB or 85% of the original size.
Number of requests can be reduced by 73 (58%)
126
53
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyodisneyresort. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
tokyodisneyresort.jp
531 ms
top.html
53 ms
reset.css
97 ms
common.css
450 ms
blogparts.css
36 ms
local.css
12 ms
jquery-ui-1.10.3.custom.css
35 ms
modernizr.min.js
10 ms
DLPO.js
17 ms
p_tdr_header.js
687 ms
jquery.min.js
29 ms
jquery.tmpl.min.js
22 ms
utilities.js
30 ms
globalnavi_sub.js
38 ms
common.js
36 ms
u.js
652 ms
lodash.legacy.min.js
70 ms
flipsnap.min.js
67 ms
update_informations.js
42 ms
jquery.easing.1.3.js
43 ms
emergencyinfos.js
54 ms
simpleslider.js
59 ms
simplepointer.js
92 ms
fadeslideshow.js
69 ms
carousel.js
488 ms
carouselbuild.js
79 ms
top.js
77 ms
jquery-ui-1.10.3.custom.min.js
90 ms
jquery.ui.datepicker-ja.js
116 ms
xdate.js
110 ms
calendar.anniversary.js
95 ms
top.carousel.js
95 ms
blogparts.js
124 ms
logo.png
36 ms
icon_blog.png
57 ms
icon_twitter.png
45 ms
icon_youtube.png
15 ms
icon_fb.png
37 ms
icon_line.png
12 ms
icon_Instagram.png
48 ms
bnr_kids.jpg
27 ms
bn_01.png
50 ms
bn_02.png
71 ms
bn_03.png
123 ms
bn_04.png
77 ms
bn_05.png
56 ms
bnr_eticket_m.png
56 ms
bnr_vp_m.png
103 ms
title_social.png
90 ms
bg_global_header_rpt.png
177 ms
head.png
525 ms
bg_nav_border.png
47 ms
ajax-loader.gif
162 ms
widgets.js
8 ms
icons_link.png
283 ms
arrow_right_w.png
109 ms
all.js
25 ms
plugins.js
403 ms
btns.png
463 ms
Knoqi57egUo
129 ms
like.php
165 ms
s_retargeting.js
572 ms
conversion.js
52 ms
50 ms
xd_arbiter.php
31 ms
xd_arbiter.php
47 ms
www-embed-player-vflQrT_sR.css
64 ms
www-embed-player.js
84 ms
base.js
148 ms
vpc6VNjRPXV.js
20 ms
LVx-xkvaJ0b.png
20 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
31 ms
ad_status.js
36 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
48 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
48 ms
44 ms
gtm.js
33 ms
559 ms
608 ms
553 ms
551 ms
619 ms
46 ms
data_10.json
46 ms
analytics.js
36 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
52 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
57 ms
feed
528 ms
favorite.pl
354 ms
icons.png
42 ms
bg_nav_border_s.png
45 ms
title.png
77 ms
82379eadd00d027b16e29ef31adc5056-276x199.jpg
224 ms
0d0b3fa73edfa167730be916d33f3339-276x199.jpg
369 ms
48326439146e1392ff38fd60f6daf54d-276x199.jpg
494 ms
linkid.js
27 ms
ec.js
30 ms
syndication
123 ms
496549779841638400
288 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
20 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
29 ms
like.php
61 ms
xd_arbiter.php
27 ms
collect
28 ms
collect
82 ms
vpc6VNjRPXV.js
9 ms
mixi_check_entry.css
49 ms
json.js
317 ms
underscore-string-1.3.3-2.0.0-compress.js
321 ms
namespace-brook-compress.js
320 ms
prototype-effects-1.6.1-1.8.3-compress.js
488 ms
mixi.js
334 ms
favorite.production.js
337 ms
jquery-1.7.1.min-noconflict-compress.js
767 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
____tw_logo6_normal.jpg
138 ms
142_pc_visual_name.jpg
686 ms
12439389_899390370160251_8777282279961190624_n.jpg
33 ms
icon_l.png
20 ms
icon_s.png
40 ms
icon_m.png
22 ms
icon_a.png
42 ms
icon_t.png
210 ms
icon_r.png
33 ms
jot.html
3 ms
comment001.gif
7 ms
favorite_button004.png
168 ms
comment_content_top001.gif
32 ms
tdr_header.css
563 ms
collect
3 ms
tokyodisneyresort.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyodisneyresort.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 Tokyodisneyresort.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.
tokyodisneyresort.jp
Open Graph data is detected on the main page of Tokyodisneyresort. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: