Tools & Wizards About Us
tokyoeats.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

tokyoeats.jp

Tokyo Eats | Just a Taste

Page Load Speed

6 sec in total

First Response

1.1 sec

Resources Loaded

2.8 sec

Page Rendered

2.1 sec

tokyoeats.jp screenshot

About Website

Visit tokyoeats.jp now to see the best up-to-date Tokyo Eats content for Canada and also check out these interesting facts you probably never knew about tokyoeats.jp

Tokyo Eats - a daily Tokyo food blog about good places to eat in and around Tokyo, Japan. Photos, reviews and ratings of Tokyo restaurants.

Visit tokyoeats.jp

Key Findings

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

Performance Metrics

tokyoeats.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.199

62/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

www.tokyoeats.jp

1132 ms

279 ms

style.css

115 ms

public.css

62 ms

style.min.css

131 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 78% of them (62 requests) were addressed to the original Tokyoeats.jp, 6% (5 requests) were made to Facebook.com and 6% (5 requests) were made to Widgets.pinterest.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tokyoeats.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 352.3 kB (5%)

Content Size

6.8 MB

After Optimization

6.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 122.2 kB

  • Original 147.8 kB
  • After minification 144.8 kB
  • After compression 25.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 122.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 6.1 MB
  • After minification 6.1 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 Eats images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 135.5 kB

  • Original 465.9 kB
  • After minification 465.0 kB
  • After compression 330.4 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 135.5 kB or 29% of the original size.

CSS Optimization

-85%

Potential reduce by 93.4 kB

  • Original 110.2 kB
  • After minification 96.7 kB
  • After compression 16.8 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. Tokyoeats.jp needs all CSS files to be minified and compressed as it can save up to 93.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (41%)

Requests Now

79

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tokyoeats.jp

www.tokyoeats.jp

1132 ms

279 ms

style.css

style.css

115 ms

public.css

public.css

62 ms

style.min.css

style.min.css

131 ms

jquery.js

jquery.js

137 ms

jquery.js

jquery.js

149 ms

easyTooltip.js

easyTooltip.js

146 ms

show_ads.js

show_ads.js

75 ms

pinit.js

pinit.js

5 ms

wp-embed.min.js

wp-embed.min.js

34 ms

243 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

40 ms

pin_it_button.png

pin_it_button.png

19 ms

header.jpg

header.jpg

41 ms

tokyoeats-cup-date.jpg

tokyoeats-cup-date.jpg

41 ms

restaurant_ukaitei01.jpg

restaurant_ukaitei01.jpg

130 ms

restaurant_ukaitei02.jpg

restaurant_ukaitei02.jpg

94 ms

restaurant_ukaitei03.jpg

restaurant_ukaitei03.jpg

143 ms

restaurant_ukaitei03.5.jpg

restaurant_ukaitei03.5.jpg

102 ms

restaurant_ukaitei04.jpg

restaurant_ukaitei04.jpg

167 ms

spacer.gif

spacer.gif

132 ms

rating_4.5.gif

rating_4.5.gif

138 ms

rating_4.gif

rating_4.gif

161 ms

rating_cost_4.gif

rating_cost_4.gif

163 ms

tokyoeats-post-footer-maki.jpg

tokyoeats-post-footer-maki.jpg

171 ms

tokyoeats-post-footer2.jpg

tokyoeats-post-footer2.jpg

173 ms

restaurant_tsurutontan1.jpg

restaurant_tsurutontan1.jpg

195 ms

restaurant_tsurutontan2.jpg

restaurant_tsurutontan2.jpg

204 ms

restaurant_tsurutontan3.jpg

restaurant_tsurutontan3.jpg

204 ms

restaurant_tsurutontan4.jpg

restaurant_tsurutontan4.jpg

294 ms

rating_cost_2.gif

rating_cost_2.gif

208 ms

cafe_quicheyoroizuka1.jpg

cafe_quicheyoroizuka1.jpg

358 ms

cafe_quicheyoroizuka2.jpg

cafe_quicheyoroizuka2.jpg

321 ms

cafe_quicheyoroizuka3.jpg

cafe_quicheyoroizuka3.jpg

296 ms

place_aonodokutsu1.jpg

place_aonodokutsu1.jpg

296 ms

place_aonodokutsu2.jpg

place_aonodokutsu2.jpg

297 ms

place_aonodokutsu3.jpg

place_aonodokutsu3.jpg

302 ms

place_aonodokutsu4.jpg

place_aonodokutsu4.jpg

321 ms

place_aonodokutsu5.jpg

place_aonodokutsu5.jpg

318 ms

cafe_anpanman1.jpg

cafe_anpanman1.jpg

319 ms

cafe_anpanman2.jpg

cafe_anpanman2.jpg

328 ms

cafe_anpanman3.jpg

cafe_anpanman3.jpg

358 ms

cafe_anpanman4.jpg

cafe_anpanman4.jpg

363 ms

cafe_anpanman5.jpg

cafe_anpanman5.jpg

359 ms

cafe_anpanman6.jpg

cafe_anpanman6.jpg

356 ms

rating_3.5.gif

rating_3.5.gif

356 ms

rating_cost_1.gif

rating_cost_1.gif

400 ms

tokyoeats-paging-utensils.jpg

tokyoeats-paging-utensils.jpg

376 ms

like.php

like.php

279 ms

like.php

like.php

461 ms

tokyoeats-sidebar-top.jpg

tokyoeats-sidebar-top.jpg

356 ms

like.php

like.php

139 ms

tokyoeats-sidebar-left-top.jpg

tokyoeats-sidebar-left-top.jpg

372 ms

like.php

like.php

284 ms

adsbygoogle.js

adsbygoogle.js

193 ms

like.php

like.php

240 ms

pinit_main.js

pinit_main.js

11 ms

about-heart-maki.jpg

about-heart-maki.jpg

327 ms

tokyoeats-sidebar-right-top.jpg

tokyoeats-sidebar-right-top.jpg

317 ms

count.json

count.json

33 ms

count.json

count.json

43 ms

count.json

count.json

36 ms

count.json

count.json

35 ms

count.json

count.json

34 ms

tokyoeats-sidebar-left-bottom.jpg

tokyoeats-sidebar-left-bottom.jpg

295 ms

tokyoeats-sidebar-right-bottom.jpg

tokyoeats-sidebar-right-bottom.jpg

300 ms

tokyoeats-sidebar-bottom.jpg

tokyoeats-sidebar-bottom.jpg

310 ms

nav_side_guidebook.jpg

nav_side_guidebook.jpg

306 ms

summaryofallposts.jpg

summaryofallposts.jpg

285 ms

tokyoeats-likeusonfb.jpg

tokyoeats-likeusonfb.jpg

288 ms

tokyoeats-laeats.jpg

tokyoeats-laeats.jpg

290 ms

tokyoeats-sidebar-bottom-lines.jpg

tokyoeats-sidebar-bottom-lines.jpg

293 ms

tokyoeats-sidebar-main-bg.jpg

tokyoeats-sidebar-main-bg.jpg

304 ms

y-w6ncCxpsQ.js

y-w6ncCxpsQ.js

30 ms

FEppCFCt76d.png

FEppCFCt76d.png

28 ms

tokyoeats-sidebar-left-middle.jpg

tokyoeats-sidebar-left-middle.jpg

287 ms

tokyoeats-sidebar-right-middle.jpg

tokyoeats-sidebar-right-middle.jpg

278 ms

search.png

search.png

277 ms

show_ads_impl.js

show_ads_impl.js

256 ms

Accessibility Review

tokyoeats.jp accessibility score

86

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tokyoeats.jp best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tokyoeats.jp SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

tokyoeats.jp

Open Graph description is not detected on the main page of Tokyo Eats. 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: