10.4 sec in total
2.1 sec
7.8 sec
502 ms
Visit ooi-guide.jp now to see the best up-to-date OOI GUIDE content and also check out these interesting facts you probably never knew about ooi-guide.jp
大井町商店街グルメMAP
Visit ooi-guide.jpWe analyzed Ooi-guide.jp page load time and found that the first response time was 2.1 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Ooi-guide.jp rating and web reputation
ooi-guide.jp performance score
2087 ms
347 ms
25 ms
910 ms
31 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 60% of them (59 requests) were addressed to the original Ooi-guide.jp, 21% (21 requests) were made to Maps.google.com and 7% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Ooi-guide.jp.
Page size can be reduced by 508.6 kB (25%)
2.0 MB
1.5 MB
In fact, the total size of Ooi-guide.jp main page is 2.0 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.3 kB or 86% of the original size.
Potential reduce by 80.8 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. OOI GUIDE images are well optimized though.
Potential reduce by 327.2 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 327.2 kB or 65% of the original size.
Potential reduce by 14.4 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. Ooi-guide.jp needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 83% of the original size.
Number of requests can be reduced by 37 (40%)
92
55
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OOI GUIDE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ooi-guide.jp
2087 ms
style.css
347 ms
js
25 ms
infobox.js
910 ms
jquery.min.js
31 ms
default.css
177 ms
common.css
867 ms
top.css
363 ms
ga.js
46 ms
bg.gif
183 ms
langNav_zh_off.gif
174 ms
langNav_ja_off.gif
183 ms
top_banner_en.jpg
898 ms
btg_00_en.gif
197 ms
side_navi_g_japanese_en_off.gif
348 ms
side_navi_g_restaurant_en_off.gif
347 ms
side_navi_g_chinese_en_off.gif
363 ms
side_navi_g_bar_en_off.gif
364 ms
side_navi_g_lightmeal_en_off.gif
391 ms
side_navi_g_other_en_off.gif
516 ms
bts_00_en.gif
514 ms
submit_en.gif
539 ms
btm_00_en.gif
542 ms
side_navi_f_bank_en_off.gif
581 ms
side_navi_f_atm_en_off.gif
684 ms
side_navi_f_postoffice_en_off.gif
685 ms
side_navi_f_lavatory_en_off.gif
720 ms
side_navi_f_school_en_off.gif
721 ms
side_navi_f_hotel_en_off.gif
774 ms
side_navi_f_aed_en_off.gif
854 ms
side_navi_f_police_en_off.gif
856 ms
side_navi_f_firehouse_en_off.gif
900 ms
side_navi_f_hospital_en_off.gif
902 ms
side_navi_f_shrine_en_off.gif
968 ms
side_navi_f_temple_en_off.gif
1025 ms
bn_pickup_en.gif
1028 ms
65_011.jpg
1958 ms
25_01.jpg
1439 ms
39_01.jpg
2350 ms
71_01.jpg
2209 ms
01_01.jpg
2256 ms
bn_access_en.gif
1192 ms
rosen_en.gif
1537 ms
bn_hot_en.gif
1622 ms
02_01.jpg
2227 ms
__utm.gif
19 ms
02_02.jpg
3137 ms
03_01.jpg
2511 ms
03_02.jpg
3214 ms
60_01.jpg
3611 ms
60_02.jpg
2956 ms
72_01.jpg
2746 ms
72_02.jpg
3046 ms
banner_machidukuri.gif
2913 ms
banner_sinakan.gif
3069 ms
bg_red.gif
2959 ms
arrow_top.png
2973 ms
common.js
37 ms
map.js
38 ms
util.js
37 ms
marker.js
27 ms
StaticMapService.GetMapImage
211 ms
onion.js
53 ms
openhand_8_8.cur
29 ms
ViewportInfoService.GetViewportInfo
91 ms
stats.js
25 ms
controls.js
17 ms
transparent.png
36 ms
css
31 ms
map_icon_gourmet_japanese.png
200 ms
google4.png
53 ms
map_icon_gourmet_bar.png
183 ms
map_icon_gourmet_restaurant.png
192 ms
map_icon_gourmet_chinese.png
189 ms
map_icon_gourmet_lightmeal.png
202 ms
map_icon_gourmet_other.png
182 ms
mapcnt6.png
57 ms
sv5.png
56 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
37 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
46 ms
vt
62 ms
vt
103 ms
vt
56 ms
vt
65 ms
vt
73 ms
vt
64 ms
vt
130 ms
vt
129 ms
vt
133 ms
vt
132 ms
vt
140 ms
vt
137 ms
tmapctrl.png
29 ms
tmapctrl4.png
22 ms
vt
189 ms
AuthenticationService.Authenticate
266 ms
ooi-guide.jp SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ooi-guide.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 Ooi-guide.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.
ooi-guide.jp
Open Graph description is not detected on the main page of OOI GUIDE. 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: