Tools & Wizards About Us
enjoytokyo.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

enjoytokyo.jp

東京のイベントとおでかけ情報｜レッツエンジョイ東京

Page Load Speed

11.5 sec in total

First Response

341 ms

Resources Loaded

9.9 sec

Page Rendered

1.3 sec

enjoytokyo.jp screenshot

About Website

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

Key Findings

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

Performance Metrics

enjoytokyo.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value26.8 s

0/100

10%

TBT (Total Blocking Time)

Value6,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value42.9 s

0/100

10%

Network Requests Diagram

enjoytokyo.jp

341 ms

enjoytokyo.jp

789 ms

www.enjoytokyo.jp

1049 ms

gtm.js

92 ms

common.css

65 ms

Our browser made a total of 148 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Enjoytokyo.jp, 46% (68 requests) were made to Rstatic.enjoytokyo.jp and 17% (25 requests) were made to Static.enjoytokyo.jp. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Rstatic.enjoytokyo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 700.6 kB (23%)

Content Size

3.0 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 196.1 kB

  • Original 235.4 kB
  • After minification 201.1 kB
  • After compression 39.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. This page needs HTML code to be minified as it can gain 34.3 kB, which is 15% 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 196.1 kB or 83% of the original size.

Image Optimization

-9%

Potential reduce by 148.1 kB

  • Original 1.7 MB
  • After minification 1.6 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. Enjoytokyo images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 356.2 kB

  • Original 990.7 kB
  • After minification 990.4 kB
  • After compression 634.5 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 356.2 kB or 36% of the original size.

CSS Optimization

-0%

Potential reduce by 197 B

  • Original 61.7 kB
  • After minification 61.7 kB
  • After compression 61.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. Enjoytokyo.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (27%)

Requests Now

140

After Optimization

102

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 140 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 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

enjoytokyo.jp

enjoytokyo.jp

341 ms

enjoytokyo.jp

enjoytokyo.jp

789 ms

www.enjoytokyo.jp

www.enjoytokyo.jp

1049 ms

gtm.js

gtm.js

92 ms

common.css

common.css

65 ms

font-icon.css

font-icon.css

57 ms

css2

css2

85 ms

ats.js

ats.js

463 ms

popper.min.js

popper.min.js

43 ms

script.js

script.js

49 ms

parts.js

parts.js

42 ms

odekake.js

odekake.js

43 ms

lets_top.js

lets_top.js

79 ms

js

js

38 ms

js

js

160 ms

uwt.js

uwt.js

256 ms

braze.no-amd.min.js

braze.no-amd.min.js

263 ms

7f85a56ba4.css

7f85a56ba4.css

41 ms

adsct

adsct

339 ms

adsct

adsct

382 ms

font-awesome-css.min.css

font-awesome-css.min.css

15 ms

logo.svg

logo.svg

160 ms

34.jpg

34.jpg

293 ms

ca01fd3e-e4f0-4fd6-a875-e72374896cc7.jpeg

ca01fd3e-e4f0-4fd6-a875-e72374896cc7.jpeg

327 ms

fcc6ef9c-84ab-49cb-8745-8da2e8fa788a.jpeg

fcc6ef9c-84ab-49cb-8745-8da2e8fa788a.jpeg

293 ms

53421810-9883-457f-8e6c-a534610f3aff.jpg

53421810-9883-457f-8e6c-a534610f3aff.jpg

957 ms

9c0ba39a-9ce2-4043-94fb-361fa55a511a.jpg

9c0ba39a-9ce2-4043-94fb-361fa55a511a.jpg

299 ms

a5ba98d0-f744-4259-abaa-4647a02e0830.jpg

a5ba98d0-f744-4259-abaa-4647a02e0830.jpg

292 ms

53421810-9883-457f-8e6c-a534610f3aff.jpg

53421810-9883-457f-8e6c-a534610f3aff.jpg

970 ms

8e0abd03-6d79-45af-920d-809ecf63e025.jpeg

8e0abd03-6d79-45af-920d-809ecf63e025.jpeg

361 ms

4d492880-fee4-449a-8ff5-c42eb2c68449.jpeg

4d492880-fee4-449a-8ff5-c42eb2c68449.jpeg

307 ms

cd4a264c-f1d2-4fe6-8f9a-4f7f02bb2978.jpeg

cd4a264c-f1d2-4fe6-8f9a-4f7f02bb2978.jpeg

997 ms

3b36ddc8-1f8e-4c04-a83d-1f6fa90c6729.jpg

3b36ddc8-1f8e-4c04-a83d-1f6fa90c6729.jpg

360 ms

5dfd3db1-2c56-407e-ab5c-33d581d387e3.jpeg

5dfd3db1-2c56-407e-ab5c-33d581d387e3.jpeg

367 ms

member_register_pc.png

member_register_pc.png

238 ms

member_register_sp.png

member_register_sp.png

239 ms

icon_bookmark.png

icon_bookmark.png

237 ms

icon_clock.png

icon_clock.png

237 ms

icon_pin.png

icon_pin.png

237 ms

icon_train.png

icon_train.png

238 ms

icon_walk.png

icon_walk.png

278 ms

ticket.png

ticket.png

939 ms

icon_yen.png

icon_yen.png

934 ms

icon_bento.png

icon_bento.png

988 ms

app_image_sp.png

app_image_sp.png

1317 ms

app_image.png

app_image.png

1460 ms

badge_apple.png

badge_apple.png

363 ms

qr_apple.png

qr_apple.png

444 ms

badge_google.png

badge_google.png

1247 ms

qr_google.png

qr_google.png

938 ms

35.jpg

35.jpg

279 ms

20.jpg

20.jpg

277 ms

26.jpg

26.jpg

283 ms

16.jpg

16.jpg

2510 ms

29.jpg

29.jpg

275 ms

thumbnail.jpg

thumbnail.jpg

287 ms

thumbnail.jpg

thumbnail.jpg

3819 ms

thumbnail.jpg

thumbnail.jpg

299 ms

thumbnail.jpg

thumbnail.jpg

297 ms

main.jpg

main.jpg

2507 ms

main.jpg

main.jpg

4118 ms

main.jpg

main.jpg

356 ms

main.jpg

main.jpg

4027 ms

main.jpg

main.jpg

359 ms

main.jpg

main.jpg

363 ms

main.jpg

main.jpg

441 ms

main.jpg

main.jpg

442 ms

main.jpg

main.jpg

3856 ms

thumbnail.jpg

thumbnail.jpg

2510 ms

thumbnail.jpg

thumbnail.jpg

2510 ms

thumbnail.jpg

thumbnail.jpg

2516 ms

thumbnail.jpg

thumbnail.jpg

2517 ms

thumbnail.jpg

thumbnail.jpg

2518 ms

thumbnail.png

thumbnail.png

2520 ms

thumbnail.png

thumbnail.png

2521 ms

thumbnail.jpg

thumbnail.jpg

2523 ms

thumbnail.jpg

thumbnail.jpg

2535 ms

img_1.jpg

img_1.jpg

2555 ms

img_2.jpg

img_2.jpg

2537 ms

img_1.jpg

img_1.jpg

4750 ms

img_1.jpg

img_1.jpg

4974 ms

img_5.jpg

img_5.jpg

3817 ms

img_1.jpg

img_1.jpg

3822 ms

img_1.jpg

img_1.jpg

3827 ms

img_3.jpg

img_3.jpg

6214 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ.ttf

254 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

339 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

341 ms

5afe9367169e7128_5058.js

5afe9367169e7128_5058.js

929 ms

fbevents.js

fbevents.js

198 ms

lt.js

lt.js

250 ms

vcdal.js

vcdal.js

197 ms

bi.js

bi.js

990 ms

adsbygoogle.js

adsbygoogle.js

336 ms

beacon.js

beacon.js

195 ms

appealapp_bg_pc.jpg

appealapp_bg_pc.jpg

2227 ms

401 ms

analytics.js

analytics.js

153 ms

img_1.jpg

img_1.jpg

3617 ms

img_1.jpg

img_1.jpg

3588 ms

img_2.jpg

img_2.jpg

3589 ms

img_1.jpg

img_1.jpg

3588 ms

img_1.jpg

img_1.jpg

3586 ms

img_1.jpg

img_1.jpg

3583 ms

img_3.jpg

img_3.jpg

3574 ms

img_1.jpg

img_1.jpg

3577 ms

bf.png

bf.png

875 ms

img_3.jpg

img_3.jpg

3522 ms

img_1.jpg

img_1.jpg

5925 ms

collect

collect

139 ms

err.gif

err.gif

669 ms

img_2.jpg

img_2.jpg

3590 ms

img_1.jpg

img_1.jpg

3588 ms

img_2.jpg

img_2.jpg

3587 ms

show_ads_impl.js

show_ads_impl.js

242 ms

collect

collect

18 ms

js

js

48 ms

ga-audiences

ga-audiences

184 ms

zrt_lookup.html

zrt_lookup.html

27 ms

tracking.min.js

tracking.min.js

16 ms

app3

app3

860 ms

sync

sync

195 ms

b3

b3

899 ms

img_1.jpg

img_1.jpg

1526 ms

img_1.jpg

img_1.jpg

3786 ms

img_2.jpg

img_2.jpg

1613 ms

img_1.jpg

img_1.jpg

1617 ms

img_1.jpg

img_1.jpg

1614 ms

img_2.jpg

img_2.jpg

1614 ms

img_1.jpg

img_1.jpg

1615 ms

img_2.jpg

img_2.jpg

1621 ms

img_1.jpg

img_1.jpg

1622 ms

img_1.jpg

img_1.jpg

1622 ms

img_2.jpg

img_2.jpg

1615 ms

img_1.jpg

img_1.jpg

1615 ms

img_3.jpg

img_3.jpg

1599 ms

img_1.jpg

img_1.jpg

2421 ms

img_1.jpg

img_1.jpg

936 ms

img_2.jpg

img_2.jpg

933 ms

thumb_alacarte_02.jpg

thumb_alacarte_02.jpg

933 ms

2405top.jpg

2405top.jpg

913 ms

thumbnail.jpg

thumbnail.jpg

3091 ms

sodar

sodar

72 ms

rep

rep

172 ms

sodar2.js

sodar2.js

21 ms

runner.html

runner.html

5 ms

aframe

aframe

20 ms

feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js

feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js

4 ms

Accessibility Review

enjoytokyo.jp accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

enjoytokyo.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

enjoytokyo.jp SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

enjoytokyo.jp

Open Graph data is detected on the main page of Enjoytokyo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: