14.7 sec in total
550 ms
13.6 sec
540 ms
Click here to check amazing COM HAUS content. Otherwise, check out these important facts you probably never knew about com-haus.net
熊本市で注文住宅を建てるならコムハウスへ。施工例やOB様の声が満載のカタログ請求や見学会情報などはHPからご覧いただけます。自由設計と優れたデザイン、インテリアコーディネートで、心地良い家づくりをご提案致します。
Visit com-haus.netWe analyzed Com-haus.net page load time and found that the first response time was 550 ms and then it took 14.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
com-haus.net performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.9 s
14/100
25%
Value16.7 s
0/100
10%
Value110 ms
97/100
30%
Value0
100/100
15%
Value18.9 s
3/100
10%
550 ms
6820 ms
341 ms
26 ms
524 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 98% of them (124 requests) were addressed to the original Com-haus.net, 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 (6.8 sec) belongs to the original domain Com-haus.net.
Page size can be reduced by 203.4 kB (7%)
3.0 MB
2.8 MB
In fact, the total size of Com-haus.net main page is 3.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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 17.8 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 17.8 kB or 75% of the original size.
Potential reduce by 45.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. COM HAUS images are well optimized though.
Potential reduce by 100.7 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 100.7 kB or 73% of the original size.
Potential reduce by 39.0 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. Com-haus.net needs all CSS files to be minified and compressed as it can save up to 39.0 kB or 80% of the original size.
Number of requests can be reduced by 18 (14%)
125
107
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COM HAUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
com-haus.net
550 ms
www.com-haus.net
6820 ms
import.css
341 ms
jquery.min.js
26 ms
jquery.easing.1.3.js
524 ms
jquery.cookie.js
361 ms
jqueryAutoHeight.js
370 ms
jquery.innerfade.js
556 ms
jQueryRotate.js
846 ms
jquery.validate.js
1079 ms
form.js
555 ms
functions.js
697 ms
analytics.js
741 ms
top_add_style.css
742 ms
jquery.gridslide.js
873 ms
top.js
926 ms
common.css
589 ms
base.css
844 ms
font.css
708 ms
layout.css
1326 ms
works.css
773 ms
analytics.js
18 ms
bg_body_left.gif
187 ms
bg_body_right.gif
181 ms
logo01.gif
187 ms
navi01_off.png
175 ms
navi02_off.png
171 ms
navi03_off.png
340 ms
navi04_off.png
348 ms
navi09_off.png
359 ms
navi05_off.png
369 ms
navi06_off.png
371 ms
navi07_off.png
507 ms
navi08_off.png
522 ms
img_nidhaus.jpg
1799 ms
img_photobook_off.jpg
1479 ms
img_work28.jpg
1517 ms
img_mainimage04.jpg
1348 ms
img_mainimage01.jpg
1561 ms
img_mainimage02.jpg
1855 ms
img_mainimage03.jpg
2809 ms
tit_order.gif
1701 ms
bg_order.jpg
2256 ms
bnr_staffblog.jpg
2256 ms
bnr_works.jpg
2335 ms
bnr_online_blanc.jpg
2530 ms
bg_news_.jpg
2776 ms
tit_news.gif
2441 ms
btn_newslist_off.gif
2515 ms
bnr_nidhaus.jpg
3180 ms
img_window01.jpg
2874 ms
img_window01_2.jpg
3033 ms
img_window01_3.jpg
2950 ms
bnr_calender.gif
2980 ms
tit_cafeinterior.jpg
3412 ms
bg_cafe.jpg
3470 ms
bnr_renovation.gif
3154 ms
collect
13 ms
bnr_obblog.jpg
3377 ms
bnr_line01.gif
3337 ms
bnr_interior03.jpg
3379 ms
img_window03.jpg
3560 ms
img_window03_2.jpg
3777 ms
img_window03_3.jpg
3838 ms
bnr_interior01_02.jpg
3690 ms
bnr_dsstyle.jpg
4203 ms
img_window02.jpg
3559 ms
img_window02_2.jpg
3907 ms
img_window02_3.jpg
4162 ms
bnr_event.jpg
4159 ms
bnr_flow.gif
3034 ms
tit_about.gif
2870 ms
bg_about.gif
3293 ms
bnr_interior02.jpg
3483 ms
2-e1458462822610.jpg
3241 ms
ico_cp.png
3263 ms
bg_compedia.gif
2999 ms
img_window04.jpg
2962 ms
img_window04_2.jpg
3085 ms
img_window04_3.jpg
2886 ms
tit_staff.gif
2675 ms
bg_staff.gif
2704 ms
bnr_recruit.jpg
3263 ms
bnr_facebook.gif
2515 ms
bnr_kimagureblog.jpg
2769 ms
bg_library.jpg
3907 ms
to_all.png
2455 ms
bnr_casita.jpg
3178 ms
bg_hausmaking.gif
2661 ms
tit_hausmaking.gif
2437 ms
IMG_6582-640x480.jpg
3652 ms
P11902852-640x359.jpg
3648 ms
IMG_6702-640x480.jpg
3349 ms
DSC_0025-640x425.jpg
2841 ms
DSC_0036-e1458197606190-425x640.jpg
3177 ms
DSC_00221-640x425.jpg
3122 ms
P1190305-e1457259147296.jpg
3807 ms
DSCF1764-640x426.jpg
3639 ms
IMG_6739-480x640.jpg
3960 ms
DSCF1813-640x426.jpg
3697 ms
019-640x480.jpg
4094 ms
DSCF1679-640x426.jpg
3862 ms
DSCF5281-640x426.jpg
3609 ms
noimg.gif
3206 ms
bnr_ichigoichie.jpg
3730 ms
bnr_attention.gif
3619 ms
bnr_soon02.gif
3392 ms
img_copyright.gif
3376 ms
btn_pagetop.gif
3418 ms
navi01_on.png
3372 ms
navi02_on.png
3289 ms
navi03_on.png
3244 ms
navi04_on.png
3254 ms
navi09_on.png
3444 ms
navi05_on.png
3174 ms
navi06_on.png
3197 ms
navi07_on.png
3183 ms
navi08_on.png
3169 ms
img_photobook_on.jpg
4078 ms
btn_newslist_on.gif
3153 ms
bg_navigation.gif
3002 ms
ico_new01.gif
3014 ms
logo02.gif
1404 ms
ico_arrow01.gif
1498 ms
ico_new02.gif
1210 ms
bg_hausmaking02.png
828 ms
ico_new03.gif
871 ms
com-haus.net 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
Links do not have a discernible name
com-haus.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
Browser errors were logged to the console
Page has valid source maps
com-haus.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Com-haus.net 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 Com-haus.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.
com-haus.net
Open Graph description is not detected on the main page of COM HAUS. 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: