7.6 sec in total
1.8 sec
5.3 sec
464 ms
Welcome to tokyo.town.co.jp homepage info - get ready to check Tokyo Town best content for Japan right away, or after learning these important things about tokyo.town.co.jp
【町コミ!】 東京都
Visit tokyo.town.co.jpWe analyzed Tokyo.town.co.jp page load time and found that the first response time was 1.8 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tokyo.town.co.jp performance score
name
value
score
weighting
Value1.7 s
91/100
10%
Value1.7 s
99/100
25%
Value2.2 s
99/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
1816 ms
1972 ms
1818 ms
1830 ms
22 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tokyo.town.co.jp, 34% (24 requests) were made to Town.co.jp and 30% (21 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Hellotalking.com.
Page size can be reduced by 497.7 kB (36%)
1.4 MB
872.2 kB
In fact, the total size of Tokyo.town.co.jp main page is 1.4 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 675.5 kB which makes up the majority of the site volume.
Potential reduce by 79.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. 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 79.1 kB or 84% of the original size.
Potential reduce by 18.9 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. Tokyo Town images are well optimized though.
Potential reduce by 374.1 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 374.1 kB or 66% of the original size.
Potential reduce by 25.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. Tokyo.town.co.jp needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 85% of the original size.
Number of requests can be reduced by 31 (48%)
64
33
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyo Town. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tokyo.town.co.jp
1816 ms
csstown.css
1972 ms
rating.css
1818 ms
common.css
1830 ms
jquery.loadmask.css
22 ms
jquery-1.7.1.min.js
2330 ms
jquery.loadmask.js
31 ms
common.js
1837 ms
get_banner.php
2239 ms
get_banner.php
2246 ms
urchin.js
23 ms
js
80 ms
bar_town3.png
731 ms
1456626181_slide_img01.jpg
1321 ms
1456625634_slide_img01%20(1).jpg
1110 ms
1446008046_%E3%83%94%E3%82%A2%E3%83%8E%E5%AD%90%E4%BE%9B.jpg
964 ms
b_list.gif
728 ms
whitespace_left_on.png
729 ms
whitespace_right_on.png
729 ms
logo_town.png
735 ms
ue.gif
737 ms
theme.png
962 ms
area.png
964 ms
bus_ss.gif
965 ms
b_s_map.png
1028 ms
line_s.gif
1029 ms
8a9c349bc2985eef4bb5fbf8c1f92fe5.jpg
692 ms
b_listb.gif
964 ms
bg_news_title.gif
1105 ms
toko.png
1105 ms
b_s_kuti3.gif
1105 ms
__utm.gif
69 ms
common.js
31 ms
map.js
31 ms
util.js
165 ms
marker.js
29 ms
onion.js
52 ms
openhand_8_8.cur
154 ms
StaticMapService.GetMapImage
307 ms
infowindow.js
132 ms
ViewportInfoService.GetViewportInfo
133 ms
stats.js
126 ms
controls.js
110 ms
transparent.png
107 ms
css
92 ms
google4.png
174 ms
go.png
320 ms
gurmet.png
368 ms
life.png
369 ms
go.png
406 ms
mapcnt6.png
80 ms
sv5.png
80 ms
vt
46 ms
vt
35 ms
tmapctrl.png
32 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
57 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
98 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
100 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
100 ms
vt
38 ms
vt
50 ms
vt
38 ms
vt
51 ms
vt
43 ms
vt
88 ms
vt
87 ms
vt
49 ms
cb_scout5.png
87 ms
tmapctrl4.png
34 ms
imgs8.png
48 ms
tokyo.town.co.jp accessibility score
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
Document doesn't have a <title> element
No form fields have multiple labels
Image elements do not have [alt] attributes
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
tokyo.town.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tokyo.town.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo.town.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tokyo.town.co.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.
tokyo.town.co.jp
Open Graph description is not detected on the main page of Tokyo Town. 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: