9.4 sec in total
1.7 sec
7.4 sec
292 ms
Visit richhouse.co.kr now to see the best up-to-date Richhouse content and also check out these interesting facts you probably never knew about richhouse.co.kr
출입통제, 비디오폰, 디지털도어락, CCTV, 근태관리, 지문인식, 번호키, 로비폰, 인터폰, 열쇠, 카메라, DVR
Visit richhouse.co.krWe analyzed Richhouse.co.kr page load time and found that the first response time was 1.7 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
richhouse.co.kr performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value2.7 s
86/100
25%
Value4.6 s
70/100
10%
Value70 ms
99/100
30%
Value0.002
100/100
15%
Value2.3 s
99/100
10%
1666 ms
380 ms
397 ms
590 ms
399 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 95% of them (137 requests) were addressed to the original Richhouse.co.kr, 1% (2 requests) were made to Login2.cafe24ssl.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Richhouse.co.kr.
Page size can be reduced by 305.6 kB (36%)
855.1 kB
549.5 kB
In fact, the total size of Richhouse.co.kr main page is 855.1 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. 50% of websites need less resources to load. Images take 680.7 kB which makes up the majority of the site volume.
Potential reduce by 42.4 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 8.4 kB, which is 16% 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 42.4 kB or 83% of the original size.
Potential reduce by 163.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, Richhouse needs image optimization as it can save up to 163.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 84.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 84.9 kB or 81% of the original size.
Potential reduce by 14.5 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. Richhouse.co.kr needs all CSS files to be minified and compressed as it can save up to 14.5 kB or 78% of the original size.
Number of requests can be reduced by 15 (10%)
143
128
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Richhouse. 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 4 to 1 for CSS and as a result speed up the page load time.
richhouse.co.kr
1666 ms
common.js
380 ms
reset.css
397 ms
main.css
590 ms
main_tablet-desktop.css
399 ms
jquery-1.7.2.min.js
6 ms
jquery.easing.1.3.js
402 ms
default.js
786 ms
cid.generate.js
567 ms
wcslog.js
7 ms
optimizer.php
601 ms
pagecheck.js
594 ms
layout_main.js
419 ms
gnb.js
574 ms
AuthSSLManager.js
1507 ms
AuthSSLManager.plugin.js
1303 ms
optimizer.php
1604 ms
ico_access.gif
629 ms
logo.gif
194 ms
search_btn.gif
198 ms
menu01.png
387 ms
menu02.png
383 ms
menu03.png
202 ms
menu04.png
385 ms
menu05.png
401 ms
menu06.png
399 ms
menu07.png
589 ms
menu08.png
591 ms
menu09.png
591 ms
menu_marker.png
592 ms
submenu_left_bg.png
609 ms
submenu_right_bg.png
779 ms
sub1_m1.gif
789 ms
sub1_m2.gif
789 ms
sub1_m3.gif
790 ms
sub2_m1.gif
812 ms
sub2_m2.gif
968 ms
sub2_m3.gif
1646 ms
sub2_m4.gif
1647 ms
sub2_m5.gif
1646 ms
sub2_m6.gif
1647 ms
sub3_m1.gif
1648 ms
sub3_m2.gif
1647 ms
sub3_m3.gif
1648 ms
sub3_m4.gif
1649 ms
sub3_m5.gif
1649 ms
sub3_m6.gif
1649 ms
sub3_m7.gif
1651 ms
sub4_m1.gif
1652 ms
sub4_m2.gif
1651 ms
sub4_m3.gif
1652 ms
sub4_m4.gif
1653 ms
sub4_m5.gif
1640 ms
sub4_m6.gif
1471 ms
sub4_m7.gif
1469 ms
sub4_m8.gif
1463 ms
sub5_m1.gif
1283 ms
sub5_m2.gif
1281 ms
sub5_m3.gif
1281 ms
sub5_m4.gif
1339 ms
sub5_m5.gif
1381 ms
sub5_m6.gif
1193 ms
sub5_m7.gif
1192 ms
sub6_m1.gif
1194 ms
sub6_m2.gif
1205 ms
sub6_m3.gif
1319 ms
sub6_m4.gif
1193 ms
sub6_m5.gif
1184 ms
sub6_m6.gif
1183 ms
sub7_m1.gif
1197 ms
sub7_m2.gif
1183 ms
m
758 ms
sub7_m3.gif
1149 ms
weblog.js
641 ms
async
565 ms
sub7_m4.gif
532 ms
sub7_m5.gif
542 ms
sub7_m6.gif
659 ms
sub7_m7.gif
741 ms
sub7_m8.gif
760 ms
sub7_m9.gif
758 ms
sub8_m1.gif
763 ms
sub8_m2.gif
784 ms
sub8_m3.gif
845 ms
sub8_m4.gif
929 ms
sub8_m5.gif
947 ms
menu_marker2.png
951 ms
login_btn.gif
956 ms
erp.jpg
987 ms
tel.gif
1040 ms
more_btn_prod.gif
1129 ms
f10_offline.jpg
1754 ms
zoom_ico.gif
1204 ms
k1_offline.jpg
1586 ms
v10_offline.jpg
1214 ms
k1.jpg
1357 ms
v10.jpg
1413 ms
gateman_v120.jpg
1876 ms
s170.jpg
1294 ms
mx541.jpg
1524 ms
mi-6300.jpg
1532 ms
shs-5021.jpg
1501 ms
biolitesolo.jpg
1688 ms
bioentryplus.jpg
1560 ms
biostation_t2.jpg
1586 ms
ace-95.jpg
1640 ms
ace-plus-95prox.jpg
2034 ms
kvm-310.jpg
1622 ms
kcv-352_white.jpg
1574 ms
cav-35u.jpg
2030 ms
CAV-43Q.jpg
1637 ms
SHT-3517XM.jpg
1838 ms
S10.jpg
1721 ms
duke2.jpg
1668 ms
jungkk0406_3082.jpg
1682 ms
SHS-5421.jpg
1766 ms
SHS-G510_SINGLE.jpg
1973 ms
quick_top.gif
1823 ms
promotion_top.gif
1819 ms
quick_cart_top.gif
1768 ms
quick_prev_btn.gif
1788 ms
quick_next_btn.gif
1812 ms
quick_top_btn.gif
1824 ms
q_cart_icon.gif
1834 ms
escrow_banner_inicis.gif
1819 ms
f_logo.gif
1874 ms
qrcode.gif
1787 ms
c_menu_division.gif
1750 ms
navi_bg.gif
1750 ms
navi_division.gif
1565 ms
gnb2_bg.gif
1571 ms
sub_division.gif
1576 ms
main-visual-bg_pc.gif
1528 ms
login_box.gif
1503 ms
login_input_bg.gif
1495 ms
login_bult.gif
1417 ms
common_box.gif
1441 ms
customer_box.gif
1428 ms
call_center_bg.gif
1412 ms
mainprod_bg_pc.gif
1377 ms
quick_bottom.gif
1359 ms
quick_dotline.gif
1367 ms
quick_thum_dotline.gif
1335 ms
footer_line_bg.gif
1400 ms
richhouse.co.kr accessibility score
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
Form elements do not have associated labels
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.
richhouse.co.kr 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
richhouse.co.kr SEO score
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
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richhouse.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Richhouse.co.kr main page’s claimed encoding is euc-kr. 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.
richhouse.co.kr
Open Graph description is not detected on the main page of Richhouse. 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: