4.2 sec in total
830 ms
3.1 sec
274 ms
Welcome to navitokyo.com homepage info - get ready to check Navitokyo best content for Japan right away, or after learning these important things about navitokyo.com
東京都の地域情報サイト『なび東京』は利用者の皆さんがより良い事業者を見つける為に東京都の事業者情報を無料で掲載。地元のビジネスを支援します。
Visit navitokyo.comWe analyzed Navitokyo.com page load time and found that the first response time was 830 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
navitokyo.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.2 s
74/100
25%
Value9.8 s
10/100
10%
Value6,310 ms
0/100
30%
Value0.094
91/100
15%
Value26.8 s
0/100
10%
830 ms
566 ms
385 ms
408 ms
421 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 30% of them (42 requests) were addressed to the original Navitokyo.com, 9% (12 requests) were made to Apis.google.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Navitokyo.com.
Page size can be reduced by 588.0 kB (53%)
1.1 MB
531.7 kB
In fact, the total size of Navitokyo.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 555.4 kB which makes up the majority of the site volume.
Potential reduce by 177.0 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 177.0 kB or 72% of the original size.
Potential reduce by 6.7 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. Navitokyo images are well optimized though.
Potential reduce by 357.3 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 357.3 kB or 64% of the original size.
Potential reduce by 47.0 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. Navitokyo.com needs all CSS files to be minified and compressed as it can save up to 47.0 kB or 85% of the original size.
Number of requests can be reduced by 78 (59%)
133
55
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Navitokyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
navitokyo.com
830 ms
jquery.min.js
566 ms
fascio.js
385 ms
normalize.min.css
408 ms
main.css
421 ms
13.js
489 ms
feed2js.php
407 ms
feed2js.php
419 ms
jquery.min.js
33 ms
main.js
270 ms
gpt.js
14 ms
navitokuselect.gif
432 ms
navitokyo150x50.gif
197 ms
yajirusi.gif
197 ms
new01-002.gif
199 ms
ico_crown2_2.gif
203 ms
ico_crown2_3.gif
218 ms
ico_crown2_4.gif
414 ms
ico_rank2b_4.gif
414 ms
ico_rank2b_5.gif
414 ms
ico_rank2b_6.gif
414 ms
ico_rank2b_7.gif
429 ms
ico_rank2b_8.gif
439 ms
ico_rank2b_9.gif
623 ms
ico_rank2b_10.gif
622 ms
qrcode_s_tokyo.gif
623 ms
qrcode_tokyo_m.gif
623 ms
netfloydlogo.png
638 ms
sdk.js
269 ms
famfamfam_icon-information.png
659 ms
vline.png
812 ms
glyphish_icon-magnify.png
812 ms
plugin-13.gif
674 ms
pubads_impl_81.js
22 ms
famfamfam_icon-vcard.png
793 ms
famfamfam_icon-page_white_edit.png
797 ms
ads
352 ms
container.html
27 ms
ajs.php
233 ms
64 ms
xd_arbiter.php
261 ms
xd_arbiter.php
463 ms
lg.php
36 ms
famfamfam_icon-heart.png
527 ms
yusuke_kamiyamane_icon-store.png
612 ms
icon-kurashi.png
701 ms
icon-kaimono.png
700 ms
icon-asobu.png
677 ms
icon-sumai.png
700 ms
icon-business.png
703 ms
icon-biyou.png
858 ms
icon-taberu.png
899 ms
icon-manabu.png
901 ms
icon-iryou.png
900 ms
icon-koukyo.png
901 ms
famfamfam_icon-chart_bar.png
879 ms
famfamfam_icon-bell.png
1011 ms
yusuke_kamiyamane_icon-mobile-phone.png
1021 ms
plusone.js
91 ms
widgets.js
93 ms
apricot.php
609 ms
ga.js
24 ms
__utm.gif
13 ms
ajs.php
211 ms
expansion_embed.js
18 ms
osd.js
13 ms
9025776355727197001
104 ms
abg.js
105 ms
m_js_controller.js
123 ms
googlelogo_color_112x36dp.png
53 ms
15833140869504982609
109 ms
like.php
84 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
76 ms
fastbutton
146 ms
followers
285 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
199 ms
like_box.php
118 ms
vpc6VNjRPXV.js
569 ms
LVx-xkvaJ0b.png
476 ms
postmessageRelay
96 ms
s
93 ms
x_button_blue2.png
38 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
33 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
75 ms
siylcCr24Vv.css
392 ms
0q9EiyOzKa_.css
388 ms
_rx8naC75Dy.js
508 ms
x5F9OMjKyLw.js
524 ms
ICDbTSzjQEg.js
445 ms
TTCre3391I0.js
444 ms
rs=AGLTcCM33YTayW1hOOQWOUmV6IE54WuGEg
51 ms
api.js
66 ms
core:rpc:shindig.random:shindig.sha1.js
95 ms
2536007149-postmessagerelay.js
63 ms
lg.php
36 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
53 ms
gprofile_button-16.png
3 ms
cpw-7de38e2bb0.png
14 ms
photo.jpg
198 ms
photo.jpg
201 ms
photo.jpg
199 ms
photo.jpg
183 ms
photo.jpg
213 ms
photo.jpg
217 ms
photo.jpg
230 ms
photo.jpg
237 ms
photo.jpg
212 ms
photo.jpg
230 ms
photo.jpg
232 ms
photo.jpg
234 ms
photo.jpg
198 ms
photo.jpg
213 ms
photo.jpg
211 ms
photo.jpg
231 ms
photo.jpg
222 ms
photo.jpg
237 ms
photo.jpg
225 ms
photo.jpg
233 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
55 ms
rs=AGLTcCOMzGzsL-BXgbmI9gBw8DLTAQj4rg
85 ms
data
99 ms
jot
116 ms
10891676_424426657716252_5378772275377851168_n.jpg
305 ms
150466_153340871491500_1910536562_n.png
352 ms
12687842_950238541713793_8562727399654423263_n.jpg
423 ms
11214344_831122820305548_8040596966724072670_n.jpg
489 ms
12744060_1695431850696672_9178366722091352781_n.jpg
492 ms
544040_102933143217476_902470881_n.jpg
488 ms
72359_946151122143640_4373926611428826842_n.jpg
492 ms
12243329_561557163995553_3908653874456625191_n.jpg
490 ms
249622_106318196127377_828061_n.jpg
556 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
75 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
135 ms
activeview
15 ms
ui
35 ms
navitokyo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
navitokyo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
navitokyo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Navitokyo.com 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 Navitokyo.com 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.
navitokyo.com
Open Graph description is not detected on the main page of Navitokyo. 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: