5.1 sec in total
562 ms
4.1 sec
410 ms
Visit tokyodisneyresort.co.jp now to see the best up-to-date Tokyodisneyresort content for United States and also check out these interesting facts you probably never knew about tokyodisneyresort.co.jp
東京ディズニーランド、東京ディズニーシー、東京ディズニーリゾート・オフィシャルウェブサイト(スマートフォンサイト)へようこそ。アトラクションなどのパーク内施設情報から、チケット、宿泊プラン、ホテルの予約・購入まで、皆さまのかけがえのない思い出づくりをサポートします。
Visit tokyodisneyresort.co.jpWe analyzed Tokyodisneyresort.co.jp page load time and found that the first response time was 562 ms and then it took 4.5 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.co.jp performance score
562 ms
556 ms
287 ms
26 ms
419 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Tokyodisneyresort.co.jp, 55% (72 requests) were made to Tokyodisneyresort.jp and 6% (8 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (990 ms) relates to the external source Graph.facebook.com.
Page size can be reduced by 1.6 MB (45%)
3.5 MB
1.9 MB
In fact, the total size of Tokyodisneyresort.co.jp main page is 3.5 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.5 MB which makes up the majority of the site volume.
Potential reduce by 52.6 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.6 kB or 78% of the original size.
Potential reduce by 89.0 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 687.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 687.9 kB or 67% of the original size.
Potential reduce by 772.7 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.co.jp needs all CSS files to be minified and compressed as it can save up to 772.7 kB or 85% of the original size.
Number of requests can be reduced by 72 (58%)
125
53
The browser has sent 125 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.co.jp
562 ms
www.tokyodisneyresort.co.jp
556 ms
top.html
287 ms
reset.css
26 ms
common.css
419 ms
blogparts.css
24 ms
local.css
19 ms
jquery-ui-1.10.3.custom.css
16 ms
modernizr.min.js
24 ms
DLPO.js
25 ms
p_tdr_header.js
227 ms
jquery.min.js
43 ms
jquery.tmpl.min.js
55 ms
utilities.js
22 ms
globalnavi_sub.js
22 ms
common.js
53 ms
u.js
623 ms
lodash.legacy.min.js
23 ms
flipsnap.min.js
21 ms
update_informations.js
21 ms
jquery.easing.1.3.js
28 ms
emergencyinfos.js
26 ms
simpleslider.js
31 ms
simplepointer.js
31 ms
fadeslideshow.js
35 ms
carousel.js
35 ms
carouselbuild.js
41 ms
top.js
38 ms
jquery-ui-1.10.3.custom.min.js
40 ms
jquery.ui.datepicker-ja.js
44 ms
xdate.js
43 ms
calendar.anniversary.js
58 ms
top.carousel.js
47 ms
blogparts.js
49 ms
logo.png
27 ms
icon_blog.png
6 ms
icon_twitter.png
7 ms
icon_youtube.png
8 ms
icon_fb.png
17 ms
icon_line.png
6 ms
icon_Instagram.png
14 ms
bnr_kids.jpg
140 ms
bn_01.png
12 ms
bn_02.png
19 ms
bn_03.png
18 ms
bn_04.png
21 ms
bn_05.png
26 ms
bnr_eticket_m.png
32 ms
bnr_vp_m.png
124 ms
title_social.png
49 ms
bg_global_header_rpt.png
25 ms
head.png
76 ms
bg_nav_border.png
76 ms
ajax-loader.gif
15 ms
widgets.js
87 ms
icons_link.png
62 ms
arrow_right_w.png
56 ms
all.js
54 ms
plugins.js
319 ms
Knoqi57egUo
109 ms
btns.png
437 ms
s_retargeting.js
615 ms
conversion.js
39 ms
like.php
110 ms
45 ms
xd_arbiter.php
30 ms
xd_arbiter.php
35 ms
www-embed-player-vflZsBgOl.css
15 ms
www-embed-player.js
41 ms
base.js
68 ms
vpc6VNjRPXV.js
103 ms
LVx-xkvaJ0b.png
90 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
42 ms
ad_status.js
73 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
67 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
67 ms
59 ms
gtm.js
56 ms
549 ms
572 ms
497 ms
554 ms
610 ms
data_10.json
27 ms
feed
990 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
133 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
163 ms
favorite.pl
322 ms
icons.png
272 ms
bg_nav_border_s.png
281 ms
title.png
297 ms
82379eadd00d027b16e29ef31adc5056-276x199.jpg
306 ms
0d0b3fa73edfa167730be916d33f3339-276x199.jpg
530 ms
48326439146e1392ff38fd60f6daf54d-276x199.jpg
522 ms
18 ms
analytics.js
15 ms
xd_arbiter.php
34 ms
linkid.js
15 ms
ec.js
15 ms
like.php
64 ms
collect
7 ms
collect
62 ms
vpc6VNjRPXV.js
14 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
49 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
60 ms
syndication
103 ms
496549779841638400
183 ms
mixi_check_entry.css
12 ms
json.js
294 ms
underscore-string-1.3.3-2.0.0-compress.js
295 ms
namespace-brook-compress.js
300 ms
prototype-effects-1.6.1-1.8.3-compress.js
447 ms
mixi.js
303 ms
favorite.production.js
303 ms
jquery-1.7.1.min-noconflict-compress.js
733 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
28 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
39 ms
____tw_logo6_normal.jpg
142 ms
142_pc_visual_name.jpg
421 ms
icon_l.png
10 ms
icon_s.png
9 ms
icon_m.png
11 ms
icon_a.png
8 ms
icon_t.png
7 ms
icon_r.png
11 ms
comment001.gif
6 ms
jot.html
30 ms
12809605_898902496875705_8466771175058447015_n.jpg
36 ms
favorite_button004.png
7 ms
comment_content_top001.gif
8 ms
tdr_header.css
189 ms
tokyodisneyresort.co.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.co.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.co.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.co.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: