Tools & Wizards About Us
tokyostory.net screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tokyostory.net

TOKYO STORY|PERFECT GUIDE for TOKYO(JAPAN) TRAVELERS

Page Load Speed

16.8 sec in total

First Response

2.6 sec

Resources Loaded

13 sec

Page Rendered

1.2 sec

tokyostory.net screenshot

About Website

Visit tokyostory.net now to see the best up-to-date TOKYO STORY content for Japan and also check out these interesting facts you probably never knew about tokyostory.net

Discover TOKYO, create your own STORY.TOKYO STORY takes you to Tokyo outside the guidebook. Visit our website to create and share your own trip plans! Please

Visit tokyostory.net

Key Findings

We analyzed Tokyostory.net page load time and found that the first response time was 2.6 sec and then it took 14.2 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

tokyostory.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

tokyostory.net

2632 ms

cssreset-min.css

14 ms

bxslide.css

328 ms

style.css

495 ms

jquery1.7.2.min.js

834 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 74% of them (78 requests) were addressed to the original Tokyostory.net, 19% (20 requests) were made to Scontent.cdninstagram.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Tokyostory.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.1 kB (16%)

Content Size

3.9 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyostory.net main page is 3.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. 55% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 49.4 kB

  • Original 61.2 kB
  • After minification 58.6 kB
  • After compression 11.8 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 49.4 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 342.8 kB

  • Original 3.6 MB
  • After minification 3.2 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. TOKYO STORY images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 166.2 kB

  • Original 253.2 kB
  • After minification 251.6 kB
  • After compression 87.0 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 166.2 kB or 66% of the original size.

CSS Optimization

-90%

Potential reduce by 58.8 kB

  • Original 65.2 kB
  • After minification 24.2 kB
  • After compression 6.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. Tokyostory.net needs all CSS files to be minified and compressed as it can save up to 58.8 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (16%)

Requests Now

100

After Optimization

84

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyostory.net

tokyostory.net

2632 ms

cssreset-min.css

cssreset-min.css

14 ms

bxslide.css

bxslide.css

328 ms

style.css

style.css

495 ms

jquery1.7.2.min.js

jquery1.7.2.min.js

834 ms

galleria-1.4.2.min.js

galleria-1.4.2.min.js

719 ms

modal.js

modal.js

335 ms

touchslider.js

touchslider.js

660 ms

bxslide.js

bxslide.js

832 ms

header.css

header.css

174 ms

main_visual.css

main_visual.css

379 ms

top_page.css

top_page.css

2312 ms

single.css

single.css

535 ms

contents.css

contents.css

560 ms

account.css

account.css

654 ms

sidebar.css

sidebar.css

704 ms

footer.css

footer.css

732 ms

modal.css

modal.css

876 ms

12751477_1727703697447790_728779685_n.jpg

12751477_1727703697447790_728779685_n.jpg

164 ms

washi.png

washi.png

1014 ms

logo.png

logo.png

517 ms

fb.png

fb.png

354 ms

google.png

google.png

378 ms

logo4.png

logo4.png

379 ms

top111.jpg

top111.jpg

1311 ms

top222.jpg

top222.jpg

1391 ms

top333.jpg

top333.jpg

1462 ms

shopping.png

shopping.png

711 ms

goumet.png

goumet.png

845 ms

spot.png

spot.png

1200 ms

wi-fi.png

wi-fi.png

1321 ms

sento.png

sento.png

1511 ms

event.png

event.png

1730 ms

%E3%81%B0%E3%81%AA%E3%81%AA%EF%BC%92.png

%E3%81%B0%E3%81%AA%E3%81%AA%EF%BC%92.png

2658 ms

man.png

man.png

1845 ms

472.jpg

472.jpg

2218 ms

%E6%B5%B7%E9%AE%AE%E2%91%A31.jpg

%E6%B5%B7%E9%AE%AE%E2%91%A31.jpg

2457 ms

67.jpg

67.jpg

2393 ms

Pix-71.png

Pix-71.png

3642 ms

441.jpg

441.jpg

2838 ms

1353-150x150.jpg

1353-150x150.jpg

2535 ms

1352-150x150.jpg

1352-150x150.jpg

2728 ms

1351-150x150.jpg

1351-150x150.jpg

2813 ms

%E3%82%A2%E3%83%A1%E3%82%B7%E3%83%B3%EF%BC%91-150x150.jpg

%E3%82%A2%E3%83%A1%E3%82%B7%E3%83%B3%EF%BC%91-150x150.jpg

2872 ms

1092-150x150.jpg

1092-150x150.jpg

2995 ms

%E5%86%99%E7%9C%9F%EF%BC%96Fujiten-150x150.jpg

%E5%86%99%E7%9C%9F%EF%BC%96Fujiten-150x150.jpg

3091 ms

4183-150x150.jpg

4183-150x150.jpg

3149 ms

%E5%86%99%E7%9C%9F%EF%BC%915-150x150.jpg

%E5%86%99%E7%9C%9F%EF%BC%915-150x150.jpg

3180 ms

%E5%86%99%E7%9C%9F%EF%BC%914-150x150.jpg

%E5%86%99%E7%9C%9F%EF%BC%914-150x150.jpg

3259 ms

Pic16-150x150.jpg

Pic16-150x150.jpg

3350 ms

Pic15-150x150.jpg

Pic15-150x150.jpg

3456 ms

Pic27-150x150.jpg

Pic27-150x150.jpg

3485 ms

Pic3--150x150.jpg

Pic3--150x150.jpg

3518 ms

Pic13-150x150.jpg

Pic13-150x150.jpg

3587 ms

12826276_922019154560128_1984082517_n.jpg

12826276_922019154560128_1984082517_n.jpg

141 ms

12725007_200472436981738_824755933_n.jpg

12725007_200472436981738_824755933_n.jpg

130 ms

10838805_256004111398270_1219961086_n.jpg

10838805_256004111398270_1219961086_n.jpg

141 ms

1389701_859247274221905_404902034_n.jpg

1389701_859247274221905_404902034_n.jpg

172 ms

12717124_1698827320363829_1441062625_n.jpg

12717124_1698827320363829_1441062625_n.jpg

141 ms

12729459_919265721474825_126268161_n.jpg

12729459_919265721474825_126268161_n.jpg

174 ms

12568744_171468716560818_1145459222_n.jpg

12568744_171468716560818_1145459222_n.jpg

170 ms

12446001_228035604195896_1312126615_n.jpg

12446001_228035604195896_1312126615_n.jpg

170 ms

12534141_777243459048067_701933345_n.jpg

12534141_777243459048067_701933345_n.jpg

183 ms

12407336_519140494930192_397801614_n.jpg

12407336_519140494930192_397801614_n.jpg

168 ms

918226_1542186966092178_650678408_n.jpg

918226_1542186966092178_650678408_n.jpg

166 ms

12393742_731879660248810_1666440768_n.jpg

12393742_731879660248810_1666440768_n.jpg

172 ms

12534137_1546481445668595_929251591_n.jpg

12534137_1546481445668595_929251591_n.jpg

172 ms

1169991_1623566707905291_2054165315_n.jpg

1169991_1623566707905291_2054165315_n.jpg

172 ms

12362265_1757219661173457_704525030_n.jpg

12362265_1757219661173457_704525030_n.jpg

167 ms

12346217_154033678296582_453577416_n.jpg

12346217_154033678296582_453577416_n.jpg

168 ms

12354025_166290457064742_1249228331_n.jpg

12354025_166290457064742_1249228331_n.jpg

169 ms

12357380_1684341191812546_1254414628_n.jpg

12357380_1684341191812546_1254414628_n.jpg

167 ms

12139850_515720581919998_821904155_n.jpg

12139850_515720581919998_821904155_n.jpg

168 ms

sdk.js

sdk.js

169 ms

9102-150x150.jpg

9102-150x150.jpg

3708 ms

analytics.js

analytics.js

47 ms

collect

collect

20 ms

collect

collect

77 ms

66 ms

xd_arbiter.php

xd_arbiter.php

83 ms

xd_arbiter.php

xd_arbiter.php

139 ms

report.jpg

report.jpg

4437 ms

userplans.jpg

userplans.jpg

4553 ms

%E9%B0%BB%E5%BA%97%EF%BC%951-150x150.jpeg

%E9%B0%BB%E5%BA%97%EF%BC%951-150x150.jpeg

3523 ms

66-150x150.jpg

66-150x150.jpg

3447 ms

86-150x150.jpg

86-150x150.jpg

3283 ms

Pix-71-150x150.png

Pix-71-150x150.png

3608 ms

Pix-213-150x150.jpg

Pix-213-150x150.jpg

3206 ms

67-150x150.jpg

67-150x150.jpg

3074 ms

103-150x150.jpg

103-150x150.jpg

3023 ms

56-150x150.jpg

56-150x150.jpg

3267 ms

%EF%BC%91%EF%BC%95%EF%BC%96%E3%80%80%EF%BC%941-150x150.jpg

%EF%BC%91%EF%BC%95%EF%BC%96%E3%80%80%EF%BC%941-150x150.jpg

3221 ms

%E3%81%8D%E3%81%9F%E3%81%B5%E3%81%8F%E3%80%80%EF%BC%971-150x150.jpg

%E3%81%8D%E3%81%9F%E3%81%B5%E3%81%8F%E3%80%80%EF%BC%971-150x150.jpg

3167 ms

ts_l.jpg

ts_l.jpg

3277 ms

ts_r.jpg

ts_r.jpg

3215 ms

sns_google.png

sns_google.png

3233 ms

sns_instagram.png

sns_instagram.png

2882 ms

sns_twitter.png

sns_twitter.png

2893 ms

modal_fb.png

modal_fb.png

2685 ms

modal_gp.png

modal_gp.png

2707 ms

modal_or.png

modal_or.png

2647 ms

modal_key.png

modal_key.png

2693 ms

modal_login.png

modal_login.png

2621 ms

bx_loader.gif

bx_loader.gif

4570 ms

mv_arr_l.png

mv_arr_l.png

4911 ms

mv_arr_r.png

mv_arr_r.png

4680 ms

Accessibility Review

tokyostory.net accessibility score

78

Accessibility Issues

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tokyostory.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tokyostory.net SEO score

90

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyostory.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Tokyostory.net 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

tokyostory.net

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