7.1 sec in total
1.3 sec
5.6 sec
211 ms
Click here to check amazing Hatosan content for Japan. Otherwise, check out these important facts you probably never knew about hatosan.jp
物件検索ならハトさん(ハトマーク東京不動産)。東京都宅建協同組合が運営する不動産情報検索サイトです。賃貸物件をはじめとした不動産を地域・沿線別に探すことができます。
Visit hatosan.jpWe analyzed Hatosan.jp page load time and found that the first response time was 1.3 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hatosan.jp performance score
name
value
score
weighting
Value15.0 s
0/100
10%
Value26.6 s
0/100
25%
Value27.7 s
0/100
10%
Value880 ms
32/100
30%
Value0
100/100
15%
Value30.6 s
0/100
10%
1253 ms
353 ms
878 ms
376 ms
583 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 73% of them (117 requests) were addressed to the original Hatosan.jp, 11% (18 requests) were made to Static.xx.fbcdn.net and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Hatosan.jp.
Page size can be reduced by 244.2 kB (51%)
476.3 kB
232.1 kB
In fact, the total size of Hatosan.jp main page is 476.3 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. 45% of websites need less resources to load. Images take 167.7 kB which makes up the majority of the site volume.
Potential reduce by 48.9 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 48.9 kB or 79% of the original size.
Potential reduce by 21.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. Obviously, Hatosan needs image optimization as it can save up to 21.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 92.6 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 92.6 kB or 61% of the original size.
Potential reduce by 81.1 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. Hatosan.jp needs all CSS files to be minified and compressed as it can save up to 81.1 kB or 85% of the original size.
Number of requests can be reduced by 45 (29%)
156
111
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hatosan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
hatosan.jp
1253 ms
screen.css
353 ms
top.css
878 ms
suggest.css
376 ms
jquery.fancybox-1.3.4.css
583 ms
jquery.min.js
32 ms
jquery.easing.min.js
6 ms
hover_tip.js
392 ms
image_utils.js
526 ms
fhconvert.js
788 ms
suggest.js
979 ms
detailSearchArea.js
699 ms
validate.js
775 ms
jquery.fancybox-1.3.4_patch.js
1214 ms
ga.js
748 ms
conversion.js
16 ms
nexRt.js
17 ms
reset.css
627 ms
base.css
875 ms
elements.css
765 ms
form.css
1006 ms
navigation.css
811 ms
s_retargeting.js
585 ms
conversion.js
481 ms
analytics.js
38 ms
logo_010.gif
188 ms
lead.gif
394 ms
header_favourite_search_btn.gif
189 ms
header_favourite_item_btn.gif
196 ms
header_favourite_com_btn.gif
178 ms
header_history_btn.gif
176 ms
header_about_btn.gif
349 ms
title_quicksearch_010.gif
352 ms
img_quicksearch_010.png
744 ms
title_quicksearch_030.png
373 ms
title_quicksearch_040.png
386 ms
title_quicksearch_050.png
523 ms
btn_quicksearch_010.png
525 ms
img_error_010.png
936 ms
navibox_rent_bg.gif
581 ms
search_railway_btn.gif
584 ms
search_region_btn.gif
695 ms
search_shop_rent_btn.gif
700 ms
search_office_rent_btn.gif
774 ms
search_land_rent_btn.gif
780 ms
search_parking_rent_btn.gif
867 ms
search_building_rent_btn.gif
873 ms
railway_btn.gif
926 ms
region_btn.gif
967 ms
navibox_buy_bg.gif
974 ms
search_condo_buy_btn.gif
1042 ms
search_detached_buy_btn.gif
1179 ms
search_tenure_buy_btn.gif
1184 ms
search_land_buy_btn.gif
1185 ms
search_shop_buy_btn.gif
1190 ms
search_building_buy_btn.gif
1189 ms
navibox_com_bg.gif
1212 ms
info_title.gif
1223 ms
info_like.gif
1300 ms
info_person.gif
1301 ms
all.js
268 ms
movie.jpg
1777 ms
66 ms
49 ms
rt
328 ms
collect
17 ms
54 ms
conversion.js
578 ms
41 ms
35 ms
32 ms
34 ms
bnr_motoduke.gif
1219 ms
bnr_oshiete.gif
1391 ms
bnr_facebook.gif
1223 ms
bnr_twitter.gif
1311 ms
bnr_010.gif
1303 ms
44 ms
xd_arbiter.php
236 ms
xd_arbiter.php
442 ms
bnr_020.gif
1239 ms
back_to_top.gif
1231 ms
logo_020.gif
1310 ms
rftc.gif
1300 ms
header_bg_top.gif
1352 ms
header_favourite_search_btn_on.gif
1236 ms
header_favourite_item_btn_on.gif
1255 ms
header_favourite_com_btn_on.gif
1288 ms
header_history_btn_on.gif
1287 ms
fql.query
59 ms
840 ms
like_box.php
156 ms
getStationNameLists
1640 ms
header_about_btn_on.gif
1234 ms
header_bg_top_020.gif
1233 ms
bg_navibox_010.gif
1205 ms
navibox_rent_txt.gif
1276 ms
fH5ORRrNfAg.css
76 ms
T-QU3r9cNUv.css
94 ms
Wx-mYPGeNCZ.css
113 ms
sth1bJRLzGb.css
142 ms
_rx8naC75Dy.js
161 ms
x5F9OMjKyLw.js
180 ms
ICDbTSzjQEg.js
132 ms
TTCre3391I0.js
130 ms
njO1TPvGzoR.js
132 ms
b_6HNn_J2BZ.js
148 ms
7cm7D75Y0Sf.js
197 ms
rFmE1g6Dkoz.js
210 ms
navibox_rent_bg_on.gif
1190 ms
search_railway_btn_on.gif
1236 ms
search_region_btn_on.gif
1238 ms
search_shop_rent_btn_on.gif
1242 ms
search_office_rent_btn_on.gif
1276 ms
search_land_rent_btn_on.gif
1269 ms
search_parking_rent_btn_on.gif
1242 ms
398894_271350966279641_1766153309_n.jpg
155 ms
420617_233643076717097_1117009555_n.jpg
58 ms
wL6VQj7Ab77.png
29 ms
s7jcwEQH7Sx.png
33 ms
QDwYpIaRyfG.png
31 ms
a-ZN6WoEOje.png
30 ms
search_building_rent_btn_on.gif
1176 ms
navibox_buy_txt.gif
1185 ms
navibox_buy_bg_on.gif
1244 ms
search_condo_buy_btn_on.gif
1241 ms
search_detached_buy_btn_on.gif
1271 ms
search_tenure_buy_btn_on.gif
1294 ms
search_land_buy_btn_on.gif
1330 ms
I6-MnjEovm5.js
18 ms
vlXaquuXMrr.js
21 ms
search_shop_buy_btn_on.gif
1266 ms
search_building_buy_btn_on.gif
1315 ms
navibox_com_txt.gif
1232 ms
navibox_com_bg_on.gif
1237 ms
info_bg_mid.gif
1191 ms
info_bg_btm.gif
1257 ms
info_bg_top.gif
1204 ms
info_number_bg_mid.gif
1229 ms
info_number_bg_right.gif
1226 ms
info_number_bg_left.gif
1134 ms
movie_on.jpg
1175 ms
bnr_motoduke_on.gif
1209 ms
bnr_oshiete_on.gif
1403 ms
bnr_facebook_on.gif
1219 ms
bnr_twitter_on.gif
1216 ms
bnrbox_bg_top.gif
1123 ms
bnrbox_bg_btm.gif
1162 ms
bnr_010_on.gif
1207 ms
arrow_small_right_020.gif
1196 ms
bnr_020_on.gif
1205 ms
back_to_top_on.gif
1129 ms
img_error_020.png
1320 ms
bg_btn.png
1228 ms
info_number_0.gif
1192 ms
info_number_2.gif
1171 ms
info_number_3.gif
1124 ms
info_number_6.gif
1125 ms
info_number_8.gif
1247 ms
info_number_9.gif
1161 ms
print.css
190 ms
hatosan.jp accessibility score
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
hatosan.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hatosan.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hatosan.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 Hatosan.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.
hatosan.jp
Open Graph description is not detected on the main page of Hatosan. 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: