8.2 sec in total
622 ms
6.8 sec
755 ms
Welcome to housecommunication.net homepage info - get ready to check Housecommunication best content right away, or after learning these important things about housecommunication.net
関西(大阪・北摂・神戸)・関東(東京)でマンション・一戸建て等、不動産の購入・売却のことから、一級建築士による新築注文住宅、リフォーム、リノベーションに至るまで、不動産に関するお困りごと、お悩みごとなどございましたら、総合不動産会社でもあるハウスコミュニケーションにお任せ下さい。地域に密着した営業スタイルと多数の成約実績から、お客様の「理想の住まい」創りのサポートをさせて頂きます。
Visit housecommunication.netWe analyzed Housecommunication.net page load time and found that the first response time was 622 ms and then it took 7.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.
housecommunication.net performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value27.0 s
0/100
25%
Value21.0 s
0/100
10%
Value6,980 ms
0/100
30%
Value0.309
38/100
15%
Value27.0 s
0/100
10%
622 ms
337 ms
344 ms
347 ms
355 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 62% of them (94 requests) were addressed to the original Housecommunication.net, 9% (14 requests) were made to Njc-web.jp and 8% (12 requests) were made to Img.njc-web.jp. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Housecommunication.net.
Page size can be reduced by 937.4 kB (26%)
3.6 MB
2.6 MB
In fact, the total size of Housecommunication.net main page is 3.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 66.0 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. This page needs HTML code to be minified as it can gain 14.2 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.0 kB or 83% of the original size.
Potential reduce by 357.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. Obviously, Housecommunication needs image optimization as it can save up to 357.8 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 169.4 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 169.4 kB or 51% of the original size.
Potential reduce by 344.2 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. Housecommunication.net needs all CSS files to be minified and compressed as it can save up to 344.2 kB or 86% of the original size.
Number of requests can be reduced by 59 (39%)
151
92
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Housecommunication. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
housecommunication.net
622 ms
boilerplate.css
337 ms
html5reset-1.6.1.css
344 ms
ie8_html5.css
347 ms
flexslider.css
355 ms
meanmenu.css
367 ms
tab.css
365 ms
leanmodal.css
505 ms
style.css
898 ms
jquery.min.js
28 ms
element.js
47 ms
line-button.js
343 ms
bookmark_button.js
320 ms
jquery.easing.min.js
9 ms
respond.min.js
353 ms
jquery.flexslider.js
543 ms
scrolltopcontrol.js
380 ms
jquery.meanmenu.js
382 ms
jquery.todate.js
508 ms
jquery.tab.js
525 ms
DD_roundies_0.0.2a.js
563 ms
jquery.leanModal.min.js
564 ms
jquery.rwdImageMaps.min.js
676 ms
button-only@2x.png
211 ms
house_title_logo.png
210 ms
chinese.png
214 ms
header_menu_icon1.png
211 ms
header_menu_icon2.png
212 ms
slide_16.jpg
699 ms
slide_15.jpg
584 ms
slide_14.jpg
684 ms
slide_13.jpg
688 ms
slide_12.jpg
917 ms
slide_10.jpg
1421 ms
slide_11.jpg
1279 ms
slide_9.jpg
1023 ms
side_ba1.png
858 ms
side_ba2.png
871 ms
side_ba28.png
1029 ms
banner-arrow.png
1043 ms
side_ba25.png
1096 ms
side_ba26.png
1190 ms
side_ba27.png
1199 ms
side_ba19.png
1214 ms
side_ba20.png
1278 ms
side_ba3.png
1359 ms
side_ba4.png
1369 ms
side_ba18.png
1387 ms
side_ba5.png
1457 ms
side_ba7.png
1642 ms
banner-line.png
1528 ms
side_ba21.png
1541 ms
side_ba22.png
1561 ms
side_ba23.png
1593 ms
side_ba24.png
1640 ms
side_ba16.png
1696 ms
mainmenu01.png
1710 ms
mainmenu02.png
1904 ms
mainmenu03.png
1769 ms
sdk.js
17 ms
mainmenu04.png
1820 ms
translateelement.css
95 ms
main.js
179 ms
131 ms
xd_arbiter.php
44 ms
xd_arbiter.php
120 ms
widgets.js
73 ms
news
3091 ms
mainmenu05.png
1664 ms
mainmenu06.png
1679 ms
element_main.js
41 ms
mainmenu07.png
1719 ms
analytics.js
61 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
129 ms
translate_24dp.png
108 ms
l
116 ms
cleardot.gif
145 ms
collect
87 ms
like.php
117 ms
267 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
45 ms
wy1X4hBW7e7.js
66 ms
te_ctrl3.gif
47 ms
LVx-xkvaJ0b.png
53 ms
9903
3149 ms
mainmenu08.png
1360 ms
mainmenu09.png
1546 ms
jot
104 ms
mainmenu10.png
1388 ms
reset.css
17 ms
entry-button.css
17 ms
bbtn-l_v3.png
4 ms
mainmenu11.png
1273 ms
mainmenu12.png
1340 ms
mainmenu13.png
1345 ms
mainmenu14.png
1287 ms
mainmenu15.png
1351 ms
mainmenu16.png
1357 ms
mainmenu17.png
1679 ms
mainmenu18.png
1293 ms
mainmenu20.png
1350 ms
chinastaff_ba1.png
1358 ms
mainmenu19.png
1386 ms
side_ba1_mobile.png
1440 ms
side_ba2_mobile.png
1385 ms
side_ba28_mobile.png
1467 ms
side_ba25_mobile.png
1500 ms
side_ba26_mobile.png
1498 ms
side_ba27_mobile.png
1490 ms
side_ba19_mobile.png
1484 ms
side_ba20_mobile.png
1516 ms
side_ba3_mobile.png
1524 ms
side_ba4_mobile.png
1527 ms
side_ba18_mobile.png
1550 ms
side_ba5_mobile.png
1585 ms
side_ba6_mobile.png
1560 ms
side_ba7_mobile.png
1581 ms
side_ba21_mobile.png
1602 ms
side_ba22_mobile.png
1605 ms
side_ba23_mobile.png
1598 ms
side_ba24_mobile.png
1669 ms
header_menu_icon3.png
1688 ms
footer_title_logo.png
1655 ms
house_scroll_top.png
1593 ms
default_base.css
596 ms
member.css
450 ms
original.css
308 ms
base.css
308 ms
elements.css
451 ms
print.css
311 ms
check.js
608 ms
jquery.js
864 ms
topListClear.js
348 ms
getHeight.js
480 ms
global_menu.css
436 ms
lopsided_ye.css
578 ms
universal_detail.css
443 ms
universal_list.css
439 ms
collect
50 ms
collect
31 ms
0BK6BK00018223.JPG
569 ms
0BK6BK0001825F.JPG
557 ms
0BK6BK0001827D.JPG
398 ms
0BK6BK000181E7.JPG
438 ms
0BK6BK000181CA.JPG
402 ms
0BK6BK000181AB.JPG
399 ms
0BK6BK000180BB.JPG
674 ms
0BK6BK000180F7.JPG
664 ms
0BK6BK0001816F.JPG
695 ms
no_photo.gif
606 ms
0BK6BK0001818E.JPG
775 ms
0BK6BK000180D9.JPG
847 ms
housecommunication.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
housecommunication.net 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
housecommunication.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Housecommunication.net 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 Housecommunication.net 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.
housecommunication.net
Open Graph description is not detected on the main page of Housecommunication. 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: