14.3 sec in total
2.6 sec
11 sec
695 ms
Visit lo-has.kr now to see the best up-to-date Lo Has content and also check out these interesting facts you probably never knew about lo-has.kr
간편하게 붙이면 완벽하게 방수가되는 방수 부틸테이프 반영구적 수명
Visit lo-has.krWe analyzed Lo-has.kr page load time and found that the first response time was 2.6 sec and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lo-has.kr performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value10.8 s
0/100
25%
Value11.0 s
6/100
10%
Value780 ms
37/100
30%
Value0.492
17/100
15%
Value14.6 s
8/100
10%
2607 ms
391 ms
391 ms
9 ms
670 ms
Our browser made a total of 170 requests to load all elements on the main page. We found that 85% of them (144 requests) were addressed to the original Lo-has.kr, 4% (6 requests) were made to Asp3.http.or.kr and 2% (3 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Lo-has.kr.
Page size can be reduced by 697.5 kB (43%)
1.6 MB
929.8 kB
In fact, the total size of Lo-has.kr main page is 1.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. 65% of websites need less resources to load. Images take 725.1 kB which makes up the majority of the site volume.
Potential reduce by 123.7 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 24.3 kB, which is 17% 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 123.7 kB or 89% of the original size.
Potential reduce by 0 B
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. Lo Has images are well optimized though.
Potential reduce by 371.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 371.2 kB or 72% of the original size.
Potential reduce by 202.6 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. Lo-has.kr needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.
Number of requests can be reduced by 59 (35%)
167
108
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lo Has. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
lo-has.kr
2607 ms
common.js
391 ms
cid.generate.js
391 ms
wcslog.js
9 ms
optimizer.php
670 ms
jquerymin.js
981 ms
rolling.js
594 ms
AuthSSLManager.js
1557 ms
AuthSSLManager.plugin.js
1348 ms
optimizer.php
944 ms
btn_prd_zoom.gif
391 ms
txt_prog_001.gif
398 ms
bg.gif
222 ms
search_but.gif
230 ms
search_ment.gif
232 ms
0289f343c5549b69f179637455a6d7d7.gif
1907 ms
f7b3b06ec64aba8ed91a2f99d5f87adc.gif
655 ms
left_bg.gif
514 ms
left_tt.gif
513 ms
login.gif
699 ms
login_down.gif
700 ms
left_d.gif
701 ms
cate_t.gif
835 ms
skin2_category43_menu.gif
875 ms
13c1b6982e9b280cbe780587981467d4.gif
912 ms
0bfaec682babdd886feb080865af66df.gif
942 ms
8a98d08ba42e88228c57a4d2a177c9ca.gif
1157 ms
4533fac91daf3c695765bfde4e0f6766.gif
1033 ms
skin2_category171_menu.gif
1066 ms
5bd3e035962bebfd632a171d80731661.gif
1120 ms
bc274304e5d90a58bdfa783ac7164b57.gif
1144 ms
skin4_category49_menu.gif
1240 ms
skin2_category172_menu.gif
1902 ms
4c3763a61ccfaae95bbcbdc69219e372.gif
1902 ms
df9a1ac2b9c86365ebb686a7e179c00e.gif
1902 ms
32a97000dc3da654e7646447a43b16ad.gif
1903 ms
skin2_category174_menu.gif
1904 ms
ee262c16711e107212de9b982cdee3a2.gif
1903 ms
left_b1.gif
1906 ms
left_b_1.gif
1907 ms
left_b_2.gif
1909 ms
board_t.gif
1904 ms
1374ce3a35e974ff8a91e94a47e87a89.gif
1903 ms
23480207d2851ce839bed88875bc6509.gif
1904 ms
btn_bag.gif
391 ms
btn_option.gif
392 ms
img_loading_bar.gif
803 ms
988317d5eff477ffa6adab359a1f11b3.gif
1901 ms
board_4.gif
1830 ms
130fbb98fc204c889748227f277ee222.gif
1693 ms
f41686f05c32e9ebaf9e1efb99941a72.gif
1687 ms
9b3ac9b67adb810f7587fb4754431bd7.gif
1702 ms
45e1750d128d2c846874916c11fe8781.gif
1652 ms
bank.gif
1474 ms
bank_link.gif
1504 ms
p3Eve2ZO2LU
91 ms
www-embed-player-vflfNyN_r.css
30 ms
www-embed-player.js
48 ms
base.js
80 ms
esc.gif
1417 ms
main_s_m.gif
1453 ms
main_s_t.gif
1427 ms
sc1.gif
1865 ms
sc2.gif
1929 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
33 ms
ad_status.js
34 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
28 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
28 ms
sc3.gif
2174 ms
scc1.gif
1426 ms
scc2.gif
1418 ms
scc3.gif
1465 ms
main_s_d.gif
1463 ms
b02ad83e9e73d50879b565796c626c38.gif
1681 ms
main_middle_b1.gif
1482 ms
main_middle_b2.gif
1585 ms
9fd9762f3d52afa886b4fe778d9a8000.gif
1809 ms
m
665 ms
sr.gif
782 ms
shinjd21_3006.jpg
1433 ms
weblog.js
628 ms
async
1074 ms
SubCategory
1297 ms
shinjd21_3049.jpg
1488 ms
shinjd21_3048.gif
1313 ms
shinjd21_12.jpg
1344 ms
shinjd21_1153.jpg
1569 ms
shinjd21_2947.jpg
1517 ms
shinjd21_2955.jpg
1560 ms
shinjd21_2213.jpg
1567 ms
shinjd21_13.jpg
1862 ms
shinjd21_3089.jpg
1889 ms
bbar.gif
1767 ms
shinjd21_3006.jpg
1966 ms
shinjd21_12.jpg
2073 ms
shinjd21_2955.jpg
2265 ms
shinjd21_2947.jpg
2456 ms
shinjd21_3048.gif
2756 ms
shinjd21_2213.jpg
2908 ms
shinjd21_3122.jpg
2127 ms
shinjd21_3141.jpg
2199 ms
shinjd21_2963.jpg
2751 ms
shinjd21_2948.jpg
2705 ms
shinjd21_2949.jpg
3009 ms
shinjd21_3051.jpg
2442 ms
shinjd21_3049.jpg
2948 ms
shinjd21_970.jpg
3186 ms
shinjd21_3062.jpg
2686 ms
shinjd21_2995.jpg
3461 ms
ASP_Conf.js
1176 ms
shinjd21_3061.jpg
2646 ms
shinjd21_2212.jpg
2995 ms
shinjd21_2667.jpg
3330 ms
shinjd21_3010.jpg
2949 ms
nnbar.gif
2740 ms
shinjd21_13.jpg
3236 ms
shinjd21_1783.jpg
3098 ms
shinjd21_3067.jpg
2965 ms
shinjd21_2755.jpg
3156 ms
shinjd21_2732.jpg
3243 ms
shinjd21_3124.jpg
3075 ms
shinjd21_3136.jpg
3069 ms
sbar.gif
3065 ms
shinjd21_1153.jpg
3065 ms
shinjd21_2985.jpg
3118 ms
shinjd21_3050.jpg
3141 ms
shinjd21_2974.jpg
2995 ms
shinjd21_3053.jpg
2927 ms
shinjd21_3082.jpg
2911 ms
[sr].gif
395 ms
emd_pt.js
533 ms
shinjd21_3083.jpg
2857 ms
shinjd21_2697.jpg
2821 ms
shinjd21_1429.jpg
3003 ms
shinjd21_2682.jpg
2705 ms
shinjd21_2731.jpg
2675 ms
HTTP_s.js
1610 ms
ebar.gif
2595 ms
shinjd21_3144.jpg
2502 ms
shinjd21_3146.jpg
2217 ms
shinjd21_3147.jpg
2263 ms
shinjd21_3143.jpg
2206 ms
shinjd21_3121.jpg
2189 ms
shinjd21_3131.jpg
2156 ms
shinjd21_3132.jpg
1937 ms
shinjd21_3000.jpg
1892 ms
shinjd21_2998.jpg
1930 ms
shinjd21_2997.jpg
1870 ms
shinjd21_2951.jpg
1607 ms
shinjd21_2964.jpg
1609 ms
st.php
780 ms
shinjd21_2965.jpg
1464 ms
shinjd21_2966.jpg
1469 ms
shinjd21_2952.jpg
1416 ms
down.gif
1595 ms
quick.gif
1306 ms
ct.gif
1292 ms
ctt.gif
1298 ms
cdd.gif
1247 ms
cd.gif
1322 ms
notice_bg.gif
1284 ms
main_middle_bg.gif
1258 ms
sbg.gif
1310 ms
cbg.gif
1297 ms
quick_line.gif
1306 ms
scc1a.gif
1324 ms
scc2a.gif
1265 ms
sst.php
439 ms
log_run.php
534 ms
scc3a.gif
198 ms
lo-has.kr 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
lo-has.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lo-has.kr SEO score
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
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lo-has.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 Lo-has.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.
lo-has.kr
Open Graph description is not detected on the main page of Lo Has. 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: