10.2 sec in total
501 ms
8.8 sec
817 ms
Visit enjoytokyo.jp now to see the best up-to-date Enjoytokyo content for Japan and also check out these interesting facts you probably never knew about enjoytokyo.jp
おでかけ大好き編集部が、今都内で話題のイベントやおでかけ先をイチ早く提案します。東京メトロとレッツエンジョイ東京の共同運営サイトです。
Visit enjoytokyo.jpWe analyzed Enjoytokyo.jp page load time and found that the first response time was 501 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
enjoytokyo.jp performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value6.7 s
7/100
25%
Value51.3 s
0/100
10%
Value29,240 ms
0/100
30%
Value0.013
100/100
15%
Value70.7 s
0/100
10%
501 ms
476 ms
1605 ms
200 ms
321 ms
Our browser made a total of 240 requests to load all elements on the main page. We found that 72% of them (173 requests) were addressed to the original Enjoytokyo.jp, 5% (13 requests) were made to Gp.enjoytokyo.jp and 3% (7 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Enjoytokyo.jp.
Page size can be reduced by 5.0 MB (25%)
20.1 MB
15.0 MB
In fact, the total size of Enjoytokyo.jp main page is 20.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. 85% 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 16.0 MB which makes up the majority of the site volume.
Potential reduce by 132.1 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 22.1 kB, which is 13% 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 132.1 kB or 81% of the original size.
Potential reduce by 2.0 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. Obviously, Enjoytokyo needs image optimization as it can save up to 2.0 MB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 65% of the original size.
Potential reduce by 1.7 MB
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. Enjoytokyo.jp needs all CSS files to be minified and compressed as it can save up to 1.7 MB or 86% of the original size.
Number of requests can be reduced by 82 (35%)
232
150
The browser has sent 232 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enjoytokyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
enjoytokyo.jp
501 ms
publisher.php
476 ms
www.enjoytokyo.jp
1605 ms
3198880830.js
200 ms
imgnavi_top.css
321 ms
sp_switcher.css
326 ms
jquery-1.5.1.min.js
970 ms
jquery.exfixed-1.3.2.js
532 ms
imgnavi.js
357 ms
leftnavi.js
477 ms
style.js
484 ms
socialbookmark_letsimg.js
533 ms
jquery.gncookie.js
527 ms
gnavi_uarea.css
951 ms
btb_right_170.css
804 ms
btb_detail_center.css
706 ms
DD_belatedPNG.js
709 ms
let_index.js
884 ms
heightLine.js
886 ms
jquery-1.9.0.min.js
1445 ms
jquery.ah-placeholder.js
1060 ms
style_header_201503.js
1063 ms
style_201503.js
1094 ms
top_201503.js
1105 ms
owl.carousel.min.js
1120 ms
easyselectbox.min.js
1234 ms
style.css
1097 ms
common_layout_201503.css
1110 ms
header_201503.css
1120 ms
top_201503.css
1139 ms
footer_201503.css
1270 ms
actionscript.js
1273 ms
jslink_v2.js
1267 ms
globalnavi.css
1278 ms
top_globalnavi.js
1326 ms
outinginfo.css
1425 ms
jquery.easing.1.3.js
1446 ms
outinginfo.js
1448 ms
element.js
76 ms
lets_topbnr.css
1283 ms
lets_topbnr.js
1325 ms
pjs.js
476 ms
lets_clip_common.js
1166 ms
clip_common_201503.css
1270 ms
footer_sns.css
967 ms
conversion.js
19 ms
s_retargeting.js
623 ms
letshuc.js
850 ms
sinjuku_pc.png
502 ms
flbn_english.png
182 ms
header_common02.png
179 ms
lets_branding_1508_pop_t04-a-narrow-animate.gif
487 ms
parts_skip_cookie.png
286 ms
bnr_header-c3-logo.gif
298 ms
lets_branding_1508_pop_t04-a-narrow-animate-logo.gif
326 ms
15040.jpg
524 ms
ico_kvNew.png
355 ms
9642.jpg
443 ms
15044.jpg
629 ms
9645.jpg
486 ms
14949.jpg
708 ms
9646.jpg
613 ms
15002.jpg
655 ms
9643.jpg
655 ms
15052.jpg
872 ms
15047.jpg
928 ms
15025.jpg
786 ms
15023.jpg
811 ms
15021.jpg
970 ms
15019.jpg
883 ms
15017.jpg
943 ms
15014.jpg
971 ms
15030.jpg
1047 ms
14585.jpg
1235 ms
14984.jpg
1240 ms
14988.jpg
1103 ms
14828.jpg
1128 ms
14819.jpg
1129 ms
14611.jpg
1224 ms
sibuya_pc.png
649 ms
ikebukuro_pc.png
484 ms
ginza_pc.png
496 ms
003.jpg
810 ms
005.jpg
875 ms
721.png
1117 ms
722.png
1118 ms
723.png
1132 ms
724.png
1275 ms
726.png
1294 ms
727.png
1407 ms
728.png
1434 ms
translateelement.css
78 ms
main.js
96 ms
14516.jpg
1410 ms
14013.jpg
1286 ms
14014.jpg
1285 ms
element_main.js
37 ms
js
329 ms
14015.jpg
1290 ms
14016.jpg
1288 ms
15037.jpg
1234 ms
15036.jpg
1288 ms
15035.jpg
1290 ms
15034.jpg
1288 ms
15033.jpg
1295 ms
15032.jpg
1278 ms
13092.jpg
1232 ms
14730.jpg
1184 ms
tominfes160209_300x250.gif
603 ms
14871.jpg
1302 ms
10940.jpg
1399 ms
sdk.js
7 ms
14762.jpg
1186 ms
widgets.js
33 ms
61 ms
g.js
508 ms
79 ms
xd_arbiter.php
26 ms
xd_arbiter.php
44 ms
12359.jpg
1332 ms
15013.jpg
1152 ms
37 ms
15015.jpg
1132 ms
15027.jpg
1249 ms
40 ms
15018.jpg
1269 ms
15024.jpg
1161 ms
15020.jpg
1135 ms
15022.jpg
1174 ms
15026.jpg
1178 ms
106114_300.jpg
1195 ms
106188_300.jpg
1164 ms
106125_300.jpg
1140 ms
106185_300.jpg
1338 ms
14266.jpg
1155 ms
index.php
172 ms
s_code.js
484 ms
14756.jpg
1272 ms
14758.jpg
1138 ms
FACE1_5.jpg
1139 ms
106198_300.jpg
1071 ms
FACE1_5.jpg
1282 ms
106196_300.jpg
1190 ms
FACE1_5.jpg
1138 ms
106195_300.jpg
1181 ms
FACE1_5.jpg
1085 ms
106194_300.jpg
1135 ms
15011.jpg
1179 ms
14903.jpg
1177 ms
15012.jpg
1200 ms
14901.jpg
1207 ms
14524.jpg
1117 ms
15010.jpg
1120 ms
15009.jpg
1177 ms
sn.js
361 ms
14765.jpg
1166 ms
14766.jpg
1397 ms
14899.jpg
1105 ms
14522.jpg
1067 ms
14353.jpg
1240 ms
14887.jpg
1621 ms
15008.jpg
1363 ms
14886.jpg
1576 ms
14641.jpg
1261 ms
13657.jpg
1250 ms
14644.jpg
1237 ms
sc_www.enjoytokyo.jp.js
806 ms
13905.jpg
1529 ms
14060.jpg
2039 ms
13906.jpg
1497 ms
13458.jpg
1301 ms
14063.jpg
1459 ms
14807.jpg
1450 ms
9618.png
1433 ms
13559.gif
1391 ms
9689.jpg
1464 ms
13956.jpg
1595 ms
14291.jpg
1424 ms
14288.jpg
1497 ms
10549.jpg
1445 ms
755412IMG1.jpg
1460 ms
1247338IMG1.jpg
1445 ms
1255625IMG1.jpg
1468 ms
1247598IMG2.jpg
1473 ms
1239185IMG1.jpg
1517 ms
lm_194IMG1.jpg
1621 ms
l_00043261IMG2.jpg
1496 ms
kiji_noimage.png
1457 ms
l_00059468IMG1.jpg
1486 ms
l_00052626IMG2.jpg
1538 ms
14997.png
1560 ms
12226.jpg
1511 ms
img_topAppList01.jpg
1527 ms
gtm_n.js
163 ms
img_topAppList02.jpg
1475 ms
img_topAppList03.jpg
1533 ms
ga_usr.php
490 ms
gtm.js
18 ms
analytics.js
5 ms
sns_icon_facebook.png
1364 ms
collect
25 ms
collect
63 ms
ec.js
5 ms
sns_icon_twitter.png
1340 ms
collect
2 ms
collect
41 ms
ga-audiences
19 ms
ga-audiences
24 ms
14281.jpg
1269 ms
14760.jpg
1241 ms
14761.jpg
1274 ms
14759.jpg
1298 ms
header_icon.png
1138 ms
spacer.gif
1187 ms
bi.js
566 ms
17 ms
js
327 ms
18 ms
img_parts_common02.png
1143 ms
ico_top_list.png
1137 ms
bg_datelist.png
1077 ms
icn_common.png
1135 ms
ico_topArticle.png
1136 ms
ico_eye.png
1118 ms
home-group-materials.png
1314 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
23 ms
btn_countpageset.png
918 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
16 ms
like.php
59 ms
vpc6VNjRPXV.js
35 ms
LVx-xkvaJ0b.png
22 ms
346 ms
jot
92 ms
translate_24dp.png
30 ms
l
49 ms
cleardot.gif
22 ms
googlelogo_color_68x28dp.png
4 ms
te_ctrl3.gif
10 ms
loading.gif
18 ms
te_bk.gif
13 ms
enjoytokyo.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
enjoytokyo.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
enjoytokyo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enjoytokyo.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 Enjoytokyo.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.
enjoytokyo.jp
Open Graph description is not detected on the main page of Enjoytokyo. 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: