26.4 sec in total
6.3 sec
19.8 sec
369 ms
Welcome to hyogo-park.or.jp homepage info - get ready to check Hyogo Park best content for Japan right away, or after learning these important things about hyogo-park.or.jp
兵庫県内の公園のイベントや花と緑の情報を写真でご紹介します。
Visit hyogo-park.or.jpWe analyzed Hyogo-park.or.jp page load time and found that the first response time was 6.3 sec and then it took 20.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
hyogo-park.or.jp performance score
6279 ms
367 ms
4807 ms
425 ms
4831 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 96% of them (78 requests) were addressed to the original Hyogo-park.or.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (8.9 sec) belongs to the original domain Hyogo-park.or.jp.
Page size can be reduced by 66.2 kB (52%)
126.8 kB
60.6 kB
In fact, the total size of Hyogo-park.or.jp main page is 126.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 49.9 kB which makes up the majority of the site volume.
Potential reduce by 41.3 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 41.3 kB or 85% of the original size.
Potential reduce by 0 B
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. Hyogo Park images are well optimized though.
Potential reduce by 7.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 7.9 kB or 16% of the original size.
Potential reduce by 16.9 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. Hyogo-park.or.jp needs all CSS files to be minified and compressed as it can save up to 16.9 kB or 82% of the original size.
Number of requests can be reduced by 41 (52%)
79
38
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hyogo 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hyogo-park.or.jp
6279 ms
import.css
367 ms
flexslider.css
4807 ms
roll.js
425 ms
pagescroll.js
4831 ms
flashmove_01.js
423 ms
flashmove_02.js
3896 ms
jquery.min.js
122 ms
jquery.flexslider-min.js
5331 ms
jquery.flexslider-customize.js
621 ms
common.css
3909 ms
contents.css
963 ms
urchin.js
13 ms
title.gif
4168 ms
header_logo.gif
435 ms
search_submit.gif
419 ms
nav.gif
1240 ms
resize_img.php
2150 ms
resize_img.php
2795 ms
top_title02.gif
621 ms
img_map.jpg
7338 ms
top_title01.gif
1017 ms
topimg_akashi.jpg
1846 ms
topimg_flower-center.jpg
2256 ms
topimg_akasikaikyou.jpg
2630 ms
topimg_harima.jpg
2888 ms
topimg_akokaihin.jpg
8854 ms
topimg_akoauto.jpg
3198 ms
topimg_maiko.jpg
3313 ms
topimg_arimafuji.jpg
8549 ms
topimg_hitokura.jpg
3785 ms
topimg_nishiina.jpg
3737 ms
topimg_amagasaki_ryokuti.jpg
5377 ms
topimg_tanba.jpg
4361 ms
topimg_mikisougou.jpg
4906 ms
topimg_midori.jpg
4742 ms
topimg_awajishima.jpg
4941 ms
topimg_awajisano.jpg
5462 ms
topimg_hanasajiki.jpg
5328 ms
topimg_ishinoneya.jpg
5728 ms
topimg_kitaharima.jpg
5604 ms
topimg_kobenishi_tennis.jpg
6003 ms
bg_tab.gif
5802 ms
nav_tab.gif
5933 ms
bt_tolist.gif
6000 ms
icon_bloom.gif
6116 ms
k_23_hanasajiki.gif
6219 ms
icon_new.gif
6183 ms
k_24_awajishima.gif
6251 ms
__utm.gif
6 ms
icon_info.gif
5972 ms
k_15_akoauto.gif
6032 ms
icon_event.gif
5901 ms
k_06_maiko.gif
5554 ms
k_27_tanba.gif
5423 ms
k_28_ishinoneya.gif
4888 ms
k_22_awajisano.gif
4606 ms
k_14_akokaihin.gif
4601 ms
k_12_arimafuji.gif
4295 ms
k_11_hitokura.gif
4149 ms
k_09_nishiina.gif
4166 ms
k_04_harima.gif
3912 ms
k_03_mikisougou.gif
3810 ms
k_01_akashi.gif
3519 ms
k_00_info.gif
3515 ms
sakura_btn.gif
3153 ms
menu_reserve.gif
3095 ms
menu_search.gif
2746 ms
menu_arrow01.gif
2593 ms
search_map.gif
2592 ms
menu_icon_search.gif
2381 ms
menu_event.gif
2327 ms
calender_arrow_l.gif
2236 ms
calender_arrow_r.gif
2127 ms
menu_rule.gif
2186 ms
menu_mobile.gif
2118 ms
menu_download.gif
2008 ms
healthy_park.gif
1962 ms
arrow_pagetop.gif
2133 ms
footer_arrow.gif
2022 ms
flexslider-icon.woff
183 ms
hyogo-park.or.jp SEO score
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hyogo-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 Hyogo-park.or.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
hyogo-park.or.jp
Open Graph description is not detected on the main page of Hyogo 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: