10.2 sec in total
1.6 sec
8.3 sec
238 ms
Welcome to teien.tokyo-park.or.jp homepage info - get ready to check Teien Tokyo Park best content for Japan right away, or after learning these important things about teien.tokyo-park.or.jp
庭園へ行こう。は東京都公園協会が管轄する庭園情報のポータルサイトです。
Visit teien.tokyo-park.or.jpWe analyzed Teien.tokyo-park.or.jp page load time and found that the first response time was 1.6 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
teien.tokyo-park.or.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value6.1 s
12/100
25%
Value7.2 s
29/100
10%
Value60 ms
100/100
30%
Value0.194
63/100
15%
Value5.0 s
76/100
10%
1625 ms
327 ms
524 ms
34 ms
924 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 83% of them (96 requests) were addressed to the original Teien.tokyo-park.or.jp, 14% (16 requests) were made to Tokyo-park.or.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Tokyo-park.or.jp.
Page size can be reduced by 106.3 kB (9%)
1.2 MB
1.1 MB
In fact, the total size of Teien.tokyo-park.or.jp main page is 1.2 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 20.7 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 20.7 kB or 78% of the original size.
Potential reduce by 41.1 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. Teien Tokyo Park images are well optimized though.
Potential reduce by 16.9 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 16.9 kB or 41% of the original size.
Potential reduce by 27.6 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. Teien.tokyo-park.or.jp needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 84% of the original size.
Number of requests can be reduced by 37 (32%)
114
77
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teien Tokyo Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
teien.tokyo-park.or.jp
1625 ms
common.css
327 ms
common.js
524 ms
jquery.min.js
34 ms
jquery.flexslider-min.js
924 ms
base.css
362 ms
font.css
489 ms
contents.css
884 ms
popup.css
370 ms
%E7%A6%8F%E5%AF%BF%E8%8D%89%E3%81%A8%E9%9B%AA%E5%9B%B2%E3%81%84-thumb-360xauto-47438.bmp
2488 ms
bg001.gif
349 ms
waku001.gif
326 ms
index_bg004.gif
176 ms
lang_bt001_on.gif
187 ms
lang_bt002.gif
165 ms
lang_bt006.gif
179 ms
lang_bt003.gif
328 ms
lang_bt004.gif
350 ms
lang_bt005.gif
356 ms
waku002.gif
597 ms
index_ph001.jpg
1659 ms
kage001.gif
490 ms
kage004.gif
520 ms
line_001.gif
522 ms
index_bg003.gif
744 ms
index_bt001.gif
850 ms
index_bt002.gif
905 ms
index_bt003.gif
910 ms
index_bt004.gif
1003 ms
index_bt005.gif
1136 ms
index_bt006.gif
1213 ms
index_bt007.gif
1288 ms
index_bt008.gif
1296 ms
index_bt009.gif
1410 ms
index_bt010.gif
1488 ms
index_ex001.gif
1377 ms
index_bg001.gif
1461 ms
index_ti001.gif
1470 ms
index_ex002.gif
1539 ms
index_ti002.gif
1596 ms
index_arrow.gif
1634 ms
spacer.gif
1644 ms
index_tx001.gif
1664 ms
index_tx017.gif
1903 ms
index_tx016.gif
1963 ms
%E5%B0%8F%E7%9F%B3%E5%B7%9D%E5%BE%8C%E6%A5%BD%E5%9C%92160224%E3%82%AB%E3%83%B3%E3%83%92%E3%82%B6%E3%82%AF%E3%83%A9%EF%BC%88%E5%86%85%E5%BA%AD%EF%BC%89%20%282%29-thumb-360xauto-49053.jpg
1385 ms
%E6%97%A7%E8%8A%9D%E9%9B%A2%E5%AE%AE%E6%81%A9%E8%B3%9C%E5%BA%AD%E5%9C%92160217%E3%82%A6%E3%83%A1-thumb-360xauto-49012.jpg
1565 ms
005-thumb-360xauto-48917.jpg
1413 ms
%E5%B0%8F%E7%9F%B3%E5%B7%9D%E5%BE%8C%E6%A5%BD%E5%9C%92160217%20%2822%29-thumb-360xauto-48530.jpg
1271 ms
P2150029-thumb-360xauto-48429.jpg
1682 ms
%E6%AE%BF%E3%83%B6%E8%B0%B7%E6%88%B8%E5%BA%AD%E5%9C%92160214%E3%82%BB%E3%83%84%E3%83%96%E3%83%B3%E3%82%BD%E3%82%A6%20%285%29-thumb-360xauto-48388.jpg
1862 ms
P2130638-thumb-360xauto-48386.jpg
1900 ms
%E3%81%91%E3%82%93%E3%81%8D%E3%82%87%E3%81%86%20%282%29-thumb-360xauto-48321.jpg
1942 ms
%E6%B5%9C%E9%9B%A2%E5%AE%AE%E6%81%A9%E8%B3%9C%E5%BA%AD%E5%9C%92160210%E8%8F%9C%E3%81%AE%E8%8A%B12-thumb-360xauto-48274.jpg
2255 ms
160209%E7%99%BD%E6%A2%85-thumb-360xauto-48223.jpg
2273 ms
%E6%AE%BF%E3%83%B6%E8%B0%B7%E6%88%B8%E5%BA%AD%E5%9C%92160207%20%2811%29-thumb-360xauto-48149.jpg
2413 ms
%E3%83%84%E3%82%A3%E3%83%BC%E3%83%88160204-thumb-360xauto-48049.jpg
2589 ms
160118%E9%9B%AA%E6%99%AF%E8%89%B2-thumb-360xauto-47397.jpg
2648 ms
%E6%97%A7%E8%8A%9D%E9%9B%A2%E5%AE%AE%E6%81%A9%E8%B3%9C%E5%BA%AD%E5%9C%92160113%E3%83%AD%E3%82%A6%E3%83%90%E3%82%A4%20%282%29-thumb-360xauto-47223.jpg
2812 ms
151205%20%2811%29-thumb-360xauto-45913.jpg
3012 ms
ga.js
29 ms
index_tx014.gif
1962 ms
__utm.gif
11 ms
bg_h2.gif
1871 ms
teien_now_title.png
1809 ms
h3_ic.gif
1668 ms
snavi_bn_01.gif
2013 ms
snavi_bn_03.jpg
1909 ms
snavi_bn_04.gif
2011 ms
snavi_bn_05.gif
1962 ms
snavi_bn_06.gif
1982 ms
snavi_bn_07.gif
2028 ms
kage002.gif
1888 ms
kage005.gif
1877 ms
foot_bg001.gif
1948 ms
foot_bt001.gif
2081 ms
foot_bt002.gif
1999 ms
foot_bg002.gif
1703 ms
foot_bt003.gif
1863 ms
foot_ex001.gif
1649 ms
foot_bt004.gif
1829 ms
copyright.gif
1807 ms
print.css
175 ms
rnavi_bt001on.gif
348 ms
rnavi_bt002on.gif
324 ms
rnavi_bt003on.gif
349 ms
rnavi_bt004on.gif
370 ms
rnavi_bt005on.gif
326 ms
rnavi_bt007on.gif
354 ms
rnavi_bt008on.gif
685 ms
rnavi_bt009on.gif
688 ms
menu_bt001on.gif
723 ms
menu_bt002on.gif
736 ms
menu_bt003on.gif
746 ms
menu_bt004on.gif
777 ms
menu_bt005on.gif
1047 ms
menu_bt006on.gif
1055 ms
menu_bt007on.gif
1105 ms
menu_bt008on.gif
1122 ms
menu_bt009on.gif
1140 ms
index_bt001on.gif
1187 ms
index_bt002on.gif
1409 ms
index_bt003on.gif
1421 ms
index_bt004on.gif
1487 ms
index_bt005on.gif
1512 ms
index_bt006on.gif
1530 ms
index_bt007on.gif
1593 ms
index_bt008on.gif
1771 ms
index_bt009on.gif
1782 ms
lang_bt002_on.gif
1660 ms
lang_bt003_on.gif
1685 ms
lang_bt004_on.gif
1705 ms
lang_bt005_on.gif
1777 ms
arrow_left.png
1833 ms
arrow_right.png
1857 ms
teien.tokyo-park.or.jp accessibility score
teien.tokyo-park.or.jp 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
General
Impact
Issue
Detected JavaScript libraries
teien.tokyo-park.or.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Teien.tokyo-park.or.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 Teien.tokyo-park.or.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.
teien.tokyo-park.or.jp
Open Graph description is not detected on the main page of Teien Tokyo Park. 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: