9.6 sec in total
1.5 sec
7.5 sec
531 ms
Visit shose.co.kr now to see the best up-to-date Shose content and also check out these interesting facts you probably never knew about shose.co.kr
테프론후렉시블,테프론닛블,PVC호스류,닥트용호스,PVC호스,산업용호스류,고무호스,복합고무호스,유압용호스,유압용부속,후렉시블/배관류,후렉시블,신주배관자재,비석면킹,호스릴류,워터릴,전기릴,스프링밸런서,고압세척기부품,원터치피팅류(상아/닛다),카플러,상아피팅/튜브,닛다무아피팅,닛다무아튜브
Visit shose.co.krWe analyzed Shose.co.kr page load time and found that the first response time was 1.5 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
shose.co.kr performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value10.6 s
0/100
25%
Value9.1 s
14/100
10%
Value70 ms
99/100
30%
Value0.545
13/100
15%
Value5.7 s
69/100
10%
1548 ms
394 ms
1586 ms
452 ms
20 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 96% of them (126 requests) were addressed to the original Shose.co.kr, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Shose.co.kr.
Page size can be reduced by 515.1 kB (20%)
2.6 MB
2.1 MB
In fact, the total size of Shose.co.kr main page is 2.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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 31.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 6.1 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 31.4 kB or 86% of the original size.
Potential reduce by 157.1 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. Shose images are well optimized though.
Potential reduce by 315.1 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 315.1 kB or 66% of the original size.
Potential reduce by 11.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. Shose.co.kr needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 75% of the original size.
Number of requests can be reduced by 38 (29%)
129
91
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shose. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
shose.co.kr
1548 ms
board.js
394 ms
ckeditor.js
1586 ms
jquery-1.7.2.min.js
452 ms
wcslog.js
20 ms
board.css
418 ms
sanglim.css
490 ms
m
465 ms
analytics.js
37 ms
nanumgothic.css
36 ms
base.css
233 ms
common.css
231 ms
main.css
198 ms
sub.css
203 ms
h1.gif
453 ms
topmenu01.gif
243 ms
topmenu02.gif
394 ms
topmenu03.gif
395 ms
search.gif
436 ms
btn_go.gif
438 ms
gnb01.png
462 ms
gnb02.png
588 ms
gnb03.png
590 ms
gnb04.png
661 ms
gnb05.png
664 ms
visual.jpg
2029 ms
dt.gif
693 ms
dd01.gif
780 ms
dd02.gif
788 ms
dd03.gif
886 ms
dd04.gif
891 ms
dd05.gif
921 ms
dd06.gif
975 ms
dd07.gif
985 ms
call.gif
1111 ms
account.gif
1119 ms
request.gif
1380 ms
list_tit01.gif
1169 ms
list_img.gif
1183 ms
list_tit02.gif
1337 ms
list_img02.gif
1346 ms
list_tit03.gif
1363 ms
list_img03.gif
1382 ms
list_tit04.gif
1561 ms
list_img04.gif
1573 ms
list_tit05.gif
1557 ms
collect
18 ms
list_img05.gif
1455 ms
list_tit06.gif
1410 ms
list_img06.gif
1547 ms
list_tit07.gif
1559 ms
list_img07.gif
1571 ms
list_tit08.gif
1398 ms
list_img08.gif
1470 ms
gall_tit01.gif
1526 ms
[3]%ED%85%8C%ED%94%84%EB%A1%A01.jpg
1553 ms
[1]%ED%85%8C%ED%94%84%EB%A1%A02.jpg
1574 ms
[3]%ED%85%8C%ED%94%84%EB%A1%A03.jpg
1578 ms
097095_1.jpg
1966 ms
[1]%ED%85%8C%ED%94%84%EB%A1%A05.jpg
1567 ms
[1]%ED%85%8C%ED%94%84%ED%8F%B06.jpg
1528 ms
btn_more.gif
1585 ms
gall_tit02.gif
1563 ms
pvc%ED%98%B8%EC%8A%A41.jpg
1486 ms
pvc2.jpg
1757 ms
pvc3.jpg
1500 ms
pvc4.jpg
2034 ms
pvc5.jpg
1560 ms
pvc6.jpg
1749 ms
gall_tit03.gif
1599 ms
%EA%B3%A0%EB%AC%B4%ED%98%B8%EC%8A%A41.jpg
1596 ms
%EA%B3%A0%EB%AC%B4%ED%98%B8%EC%8A%A42.jpg
2010 ms
%EA%B3%A0%EB%AC%B4%ED%98%B8%EC%8A%A43.jpg
1612 ms
%EA%B3%A0%EB%AC%B4%ED%98%B8%EC%8A%A44.jpg
1598 ms
%EA%B3%A0%EB%AC%B4%ED%98%B8%EC%8A%A45.jpg
1597 ms
%EA%B3%A0%EB%AC%B4%ED%98%B8%EC%8A%A46.jpg
1602 ms
gall_tit04.gif
1649 ms
%ED%9B%8401.jpg
1603 ms
%ED%9B%8402.jpg
1766 ms
%ED%9B%8403.jpg
1603 ms
%ED%9B%8404.jpg
1616 ms
%ED%9B%8405.jpg
1606 ms
main_147_s.jpg
1661 ms
gall_tit05.gif
1698 ms
[4]011.jpg
1622 ms
%EB%A6%B401.jpg
1607 ms
%EB%A6%B402.jpg
1618 ms
%EB%A6%B403.jpg
1577 ms
%EB%A6%B404.jpg
1639 ms
%EB%A6%B405.jpg
1565 ms
gall_tit06.gif
1622 ms
%EC%9C%A001.jpg
1565 ms
%EC%9C%A002.jpg
1592 ms
%EC%9C%A003.jpg
1604 ms
%EC%9C%A004.jpg
1574 ms
%EC%9C%A005.jpg
1532 ms
[1]%EC%9C%A006.jpg
1538 ms
gall_tit07.gif
1579 ms
%EC%B9%B401.jpg
1580 ms
%EC%B9%B402.jpg
1485 ms
%EC%B9%B4%ED%94%8C%EB%9F%AC03.jpg
1433 ms
%EC%B9%B404.jpg
1416 ms
%EC%B9%B405.jpg
1434 ms
%EC%B9%B406.jpg
1475 ms
gall_tit08.gif
1365 ms
%ED%94%8401.jpg
1375 ms
%ED%94%8402.jpg
1326 ms
%ED%94%8403.jpg
1407 ms
%ED%94%8404.jpg
1259 ms
%ED%94%8405.jpg
1350 ms
%ED%94%8406.jpg
1348 ms
gall_tit09.gif
1343 ms
%EB%B0%9801.jpg
1289 ms
%EB%B0%9802.jpg
1253 ms
%EB%B0%9803.jpg
1270 ms
%EB%B0%9804.jpg
1349 ms
%EB%B0%9805.jpg
1346 ms
%EB%B0%9806.jpg
1315 ms
gall_tit10.gif
1310 ms
%EC%A0%9C01.jpg
1255 ms
%EC%A0%9C02.jpg
1274 ms
%EC%A0%9C0001.jpg
1311 ms
%EC%A0%9C04.jpg
1349 ms
%EC%A0%9C05.jpg
1354 ms
%EC%A0%9C06.jpg
1288 ms
foot_h1.gif
1259 ms
bg_topmenu.gif
1301 ms
bg_list_area_img.gif
1285 ms
bg_list_area.gif
1359 ms
bg_gallery_img.gif
1351 ms
bg_bm.gif
1262 ms
shose.co.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
Form elements do not have associated labels
shose.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
shose.co.kr SEO score
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shose.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 Shose.co.kr 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.
shose.co.kr
Open Graph description is not detected on the main page of Shose. 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: