12.1 sec in total
1.3 sec
9.3 sec
1.5 sec
Welcome to duck0.co.kr homepage info - get ready to check Duck 0 best content for South Korea right away, or after learning these important things about duck0.co.kr
50년 전통의 목공구 전문점, 조각공구, 서각, 수공구
Visit duck0.co.krWe analyzed Duck0.co.kr page load time and found that the first response time was 1.3 sec and then it took 10.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.
duck0.co.kr performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value20.1 s
0/100
25%
Value18.8 s
0/100
10%
Value150 ms
94/100
30%
Value0.37
29/100
15%
Value19.9 s
2/100
10%
1311 ms
1001 ms
115 ms
1472 ms
1970 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 92% of them (107 requests) were addressed to the original Duck0.co.kr, 3% (3 requests) were made to Web14.logcounter.com and 2% (2 requests) were made to Serial14.logcounter.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Duck0.co.kr.
Page size can be reduced by 425.2 kB (21%)
2.0 MB
1.6 MB
In fact, the total size of Duck0.co.kr main page is 2.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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 97.6 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 50.6 kB, which is 46% 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 97.6 kB or 89% of the original size.
Potential reduce by 38.0 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. Duck 0 images are well optimized though.
Potential reduce by 260.3 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 260.3 kB or 76% of the original size.
Potential reduce by 29.3 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. Duck0.co.kr needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 82% of the original size.
Number of requests can be reduced by 19 (17%)
115
96
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duck 0. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
duck0.co.kr
1311 ms
common.css
1001 ms
wcslog.js
115 ms
jquery-1.7.2.min.js
1472 ms
flash.js
1970 ms
rightbanner.js
772 ms
bookmark.js
514 ms
main.css
725 ms
shopRbanner.html
773 ms
header.1.css
977 ms
mcommon.js
1007 ms
jquery.easing.1.3.min.js
805 ms
jquery.sliderkit.1.9.2.pack.js
1000 ms
footer.1.css
996 ms
detailpage.js
1060 ms
jquery.language.js
781 ms
jquery.option.js
1404 ms
Log_script_logsid.html
985 ms
cookie.js
1058 ms
icon_cart.gif
688 ms
ban01.jpg
695 ms
logo.gif
694 ms
btn_search.gif
877 ms
top_bbs01.gif
888 ms
top_bbs02.gif
897 ms
top_bbs03.gif
896 ms
top_bbs05.gif
1099 ms
ban02.jpg
1099 ms
btn_allcate.gif
1112 ms
cate01.gif
1117 ms
cate02.gif
1115 ms
cate03.gif
1169 ms
cate04.gif
1306 ms
cate05.gif
1307 ms
cate06.gif
1316 ms
cate07.gif
1322 ms
cate08.gif
1324 ms
cate09.gif
1376 ms
main01.jpg
2456 ms
main02.jpg
2453 ms
main03.jpg
2492 ms
ban03.jpg
1547 ms
ban04.jpg
1546 ms
ban05.jpg
2781 ms
ban06.jpg
1974 ms
ban07.jpg
1553 ms
tit_best.gif
1771 ms
0010010000032.jpg
2004 ms
1
1799 ms
view_shopdetail.gif
1978 ms
0010020000032.jpg
1976 ms
25
2171 ms
0010020000232.jpg
2045 ms
0010030000062.jpg
2057 ms
0010040000222.jpg
2052 ms
2
2054 ms
0050040000242.jpg
2061 ms
0090010000072.jpg
2061 ms
0040040000042.jpg
2066 ms
0010060000012.jpg
2075 ms
0010020000062.jpg
2072 ms
scroll.css
2060 ms
0140040000042.jpg
2148 ms
0050020000112.jpg
2152 ms
0010040000152.jpg
2141 ms
0090030000022.jpg
2139 ms
0040010000372.jpg
2141 ms
0040010000332.jpg
3858 ms
6
2125 ms
0010010000132.jpg
2126 ms
0010010000072.jpg
2136 ms
0050020000142.jpg
2143 ms
0010030000502.jpg
3411 ms
ban_best.jpg
2315 ms
0010010000022.jpg
2145 ms
0010030000262.jpg
3453 ms
tit_new.gif
1951 ms
0040010000432.jpg
1948 ms
3
1948 ms
0050010000312.jpg
1711 ms
0050010000302.jpg
1974 ms
0050010000292.jpg
1770 ms
0010030000672.jpg
1792 ms
0010030000662.jpg
1989 ms
0010030000652.jpg
1982 ms
0010030000642.jpg
2008 ms
0010030000622.jpg
1983 ms
0010030000612.jpg
1981 ms
0040060000042.jpg
1990 ms
0030010000402.jpg
2199 ms
0110010000232.jpg
2199 ms
0090010000412.jpg
2182 ms
0090010000402.jpg
2306 ms
0090040000032.jpg
2264 ms
0030010000392.jpg
2248 ms
0110010000222.jpg
4448 ms
0010030000492.jpg
2779 ms
0010030000532.jpg
3399 ms
bt_ban_cs.gif
2199 ms
bt_ban_bank.gif
2196 ms
bt_ban_quick.gif
2229 ms
tit_news.gif
2439 ms
m
715 ms
bt_logo.gif
2414 ms
[sr].gif
766 ms
mslog.js
995 ms
quick.gif
2296 ms
bg.gif
2506 ms
top_bbs_bg.gif
2486 ms
top_cate_bg.gif
2501 ms
best_bg.gif
2294 ms
Conf_nawebd.js
526 ms
ms.log
495 ms
[sr].gif
703 ms
emd_pt.js
705 ms
HTTP_s.js
997 ms
duck0.co.kr 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-hidden="true"] elements contain focusable descendents
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
duck0.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
duck0.co.kr 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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duck0.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Duck0.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.
duck0.co.kr
Open Graph description is not detected on the main page of Duck 0. 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: