15.5 sec in total
3.4 sec
10.3 sec
1.8 sec
Click here to check amazing Wecanall content. Otherwise, check out these important facts you probably never knew about wecanall.co.kr
kusamayayoi
Visit wecanall.co.krWe analyzed Wecanall.co.kr page load time and found that the first response time was 3.4 sec and then it took 12.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.
wecanall.co.kr performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.032
100/100
15%
Value0
0/100
10%
3422 ms
470 ms
878 ms
2616 ms
894 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 97% of them (100 requests) were addressed to the original Wecanall.co.kr, 1% (1 request) were made to Googleadservices.com and 1% (1 request) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Wecanall.co.kr.
Page size can be reduced by 339.9 kB (26%)
1.3 MB
973.2 kB
In fact, the total size of Wecanall.co.kr main page is 1.3 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. 25% of websites need less resources to load. Images take 950.7 kB which makes up the majority of the site volume.
Potential reduce by 95.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 20.2 kB, which is 19% 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 95.4 kB or 89% of the original size.
Potential reduce by 66.2 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. Wecanall images are well optimized though.
Potential reduce by 82.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 82.2 kB or 57% of the original size.
Potential reduce by 96.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. Wecanall.co.kr needs all CSS files to be minified and compressed as it can save up to 96.0 kB or 86% of the original size.
Number of requests can be reduced by 27 (27%)
101
74
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wecanall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
wecanall.co.kr
3422 ms
import.css
470 ms
uniform.default.css
878 ms
jquery-1.8.3.min.js
2616 ms
jquery.uniform.min.js
894 ms
comm.js
674 ms
menu_model.js
888 ms
jcarousellite-1.8.7.min.js
802 ms
default.css
714 ms
layout.css
861 ms
common.css
890 ms
contents.css
1994 ms
main.css
1188 ms
nanumgothic.css
435 ms
conversion.js
25 ms
20141104204342_01.jpg
2146 ms
bg_header.gif
309 ms
logo.gif
544 ms
ico_tip.gif
308 ms
ico_1.gif
305 ms
btn_search1.gif
304 ms
bg_link1.gif
540 ms
gnb01.gif
562 ms
gnb02.gif
556 ms
gnb03.gif
549 ms
gnb04.gif
570 ms
gnb05.gif
570 ms
gnb06.gif
546 ms
gnb07.gif
753 ms
gnb08.gif
755 ms
gnb09.gif
751 ms
ico_new.png
762 ms
ico_hit.gif
782 ms
bg_box01.gif
790 ms
20160228182304_01.jpg
2370 ms
20160210224718_01.jpg
4939 ms
20141104005755_01.PNG
6121 ms
20141024142620_01.png
2263 ms
20141230135930_01.jpg
3394 ms
20141027123221_01.jpg
2057 ms
f_btn.gif
2373 ms
20141031003838_01.jpg
2164 ms
20150502204114_01.jpg
2036 ms
20150108133645_01.jpg
2013 ms
20150525051328_01.jpg
2233 ms
20141231085936_01.jpg
2188 ms
20141229105131_01.jpg
2680 ms
20141120053954_01.jpg
2615 ms
20141106170930_01.jpg
2627 ms
20150309100427_01.jpg
2732 ms
20150210145807_01.jpg
2726 ms
20150223172634_01.jpg
2782 ms
20150315163243_01.jpg
3139 ms
20150116113305_01.jpg
2958 ms
20140725132540_01.jpg
3189 ms
20150130185026_01.jpg
3047 ms
20150408132927_01.jpg
3319 ms
20150318153918_01.jpg
3366 ms
20160228182938_01.jpg
3832 ms
20140613165512_01.jpg
3718 ms
20150126164020_01.jpg
4753 ms
20150210114033_01.jpg
3872 ms
20140729174848_01.jpg
4169 ms
20140705153711_01.jpg
4004 ms
20160328105315_01.jpg
3982 ms
20160328105345_01.jpg
4044 ms
20160328105243_01.jpg
4136 ms
20160316004836_01.jpg
4646 ms
20160315172702_01.jpg
4267 ms
20160314174835_01.jpg
4675 ms
20160311190000_01.jpg
4368 ms
20160311185256_01.jpg
4389 ms
20160308192615_01.jpg
4500 ms
20160303142936_01.jpg
4803 ms
20160303142816_01.jpg
5057 ms
20160303142626_01.jpg
5160 ms
bg_container_line.gif
2342 ms
bg_m_todays.gif
2455 ms
bg_box1.gif
2461 ms
ico_recomme.gif
2575 ms
bl_01.gif
2653 ms
btn_more.gif
2659 ms
bg_link2.gif
2829 ms
ico_star.gif
2873 ms
ico_m_tab.gif
2902 ms
ico_2.gif
3064 ms
bg_footer.gif
3073 ms
ico_top.gif
2967 ms
238 ms
46 ms
20160219025302_01.jpg
2923 ms
20160221005631_01.jpg
3140 ms
20140812012620_01.jpg
3585 ms
20150130191809_01.jpg
3125 ms
20150206185210_01.jpg
3020 ms
20141201170703_01.jpg
3730 ms
20150606232425_01.jpg
3086 ms
20140725145628_01.jpg
3269 ms
20140802093538_01.jpg
3063 ms
20150121173208_01.jpg
3072 ms
20140627184912_01.jpg
3468 ms
bg_box01.gif
3119 ms
20160201155700.gif
3058 ms
wecanall.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
wecanall.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Missing source maps for large first-party JavaScript
wecanall.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
EN
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecanall.co.kr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Wecanall.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.
wecanall.co.kr
Open Graph description is not detected on the main page of Wecanall. 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: