10.5 sec in total
754 ms
8 sec
1.8 sec
Visit wonlog.co.kr now to see the best up-to-date Wonlog content and also check out these interesting facts you probably never knew about wonlog.co.kr
일상 속에 스며드는 우리만의 특별한 데일리룩, 원로그 자체제작 WONT 월/수/금 13시 업데이트!
Visit wonlog.co.krWe analyzed Wonlog.co.kr page load time and found that the first response time was 754 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wonlog.co.kr performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value47.4 s
0/100
25%
Value24.2 s
0/100
10%
Value4,050 ms
1/100
30%
Value0.543
13/100
15%
Value47.8 s
0/100
10%
754 ms
2119 ms
234 ms
555 ms
29 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 36% of them (52 requests) were addressed to the original Wonlog.co.kr, 42% (60 requests) were made to Cafe24img.poxo.com and 5% (7 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Cafe24img.poxo.com.
Page size can be reduced by 549.7 kB (4%)
13.0 MB
12.4 MB
In fact, the total size of Wonlog.co.kr main page is 13.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. Only a small number of websites need less resources to load. Images take 11.7 MB which makes up the majority of the site volume.
Potential reduce by 506.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 506.3 kB or 87% of the original size.
Potential reduce by 6.7 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. Wonlog images are well optimized though.
Potential reduce by 36.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 119 B
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. Wonlog.co.kr has all CSS files already compressed.
Number of requests can be reduced by 48 (34%)
141
93
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wonlog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
wonlog.co.kr
754 ms
wonlog.co.kr
2119 ms
jet.js
234 ms
NPUTcAbZ26S46zVSF3zpuZXC.js
555 ms
jquery.min.js
29 ms
slick.min.js
579 ms
slick.css
585 ms
all.css
35 ms
xeicon.min.css
579 ms
font.css
585 ms
cid.generate.js
597 ms
wcslog.js
31 ms
optimizer.php
573 ms
optimizer_user.php
593 ms
idio.js
577 ms
setup.js
578 ms
topbn.js
582 ms
mainBnr.js
580 ms
prdTab.js
804 ms
spm_f_common.js
2202 ms
snap_combine_script.js
1135 ms
initializer.js
1540 ms
bbsArea1.js
627 ms
ld.js
22 ms
kp.js
100 ms
js
78 ms
kakao.min.js
162 ms
i18n.php
1791 ms
optimizer.php
1712 ms
optimizer_user.php
639 ms
e0cb8dc362a2cafbb65cdfccc2c9a6bb.gif
167 ms
ico_product_point.gif
132 ms
logo.png
420 ms
ic_sch.png
820 ms
0823freeshippingpc.jpg
823 ms
icon_201802012257110700.png
821 ms
icon_201802012257161200.png
821 ms
icon_201802012257060500.png
914 ms
custom_14817183451435026.png
915 ms
benefit_shop1_80372966a3062a85d673.71256017.png
915 ms
benefit_shop1_971963667cd1ee4c5fd9.53768454.png
1174 ms
custom_14617183451423646.png
1176 ms
benefit_shop1_92503666b9760490e209.69720934.png
1175 ms
benefit_shop1_3177106674e4468b79f1.04410827.png
1176 ms
benefit_shop1_26467566b978ef864245.03158479.png
1306 ms
benefit_shop1_93164466a06b56c44811.16936854.png
1300 ms
benefit_shop1_2598676682110cd3a981.06951459.png
1307 ms
benefit_shop1_55640966b975b41820e9.26983760.png
1305 ms
benefit_shop1_30279166b978476676a5.41908652.png
1489 ms
benefit_shop1_22653966909d7b50d022.60297772.png
1491 ms
downicon1.png
1491 ms
downicon2.png
1493 ms
downicon3.png
1675 ms
logo2.png
1679 ms
btn_details.gif
144 ms
ico_tip_title.gif
148 ms
btn_close_tip.gif
153 ms
txt_progress.gif
152 ms
img_loading.gif
150 ms
btn_close.gif
151 ms
7c6a31f40c3af2c66bd67c81d69f6a2d.gif
158 ms
bb0b62c3b9ccaf2f709e3d13b750b5e5.gif
88 ms
acf4cac663c7ea11ee4aa74a69f2cc52.gif
2470 ms
c13e4908d359b28a0e9ca1d5f36925f4.gif
171 ms
d0304f8262fa7999af00e380f584b8ac.gif
148 ms
c7547161286c4bb54c571033b509811e.gif
258 ms
f9509c2abc0944c36adf4e07af43bdf3.gif
2817 ms
4079a30cecbc2c99a430690c6b2a3ab1.gif
265 ms
bb00ba5ac8ccd071a71d8167dd96d727.gif
262 ms
5449d5ab1afe83eff195181951725bb4.gif
269 ms
0ee7c05bb1d9b72e0cfd7893d362205b.gif
325 ms
c9b81a59f5eeb772c5e9d16546ea2181.gif
334 ms
6c4fe18cb5fcdc057d0ba2f66b27c482.gif
341 ms
61cd0c9849ad4422885ea22ad02f89eb.gif
423 ms
8bc1274bd55b311310230fdcb522b746.gif
413 ms
2b5c993b6f8a722d2e55d4a63da47082.gif
400 ms
f5eae14f827c5844699317e81df94b0b.gif
406 ms
445fd2d884b64629beeccef6317c34ba.gif
432 ms
0161712b3cf2eccc544cc4ef3a69315f.gif
426 ms
feb12651ccd698017c6ce3e23cef4025.gif
701 ms
1d58c8ebc6f55d69df2bcf35ee27e40a.gif
3102 ms
ea4457b7b15b5712df884c75866acf95.gif
437 ms
e5f02b08a4d17b49f7fb2280e0afa3ba.gif
2815 ms
c367e4627f823cf2b501813d368a1b2d.gif
2791 ms
d87f8569de62f35d318ba3e143f8c8f9.gif
2811 ms
6c487ff7dfc140d7a50e560ebb13dcd5.gif
2500 ms
064abc5661b0eef6136e8b9afb369687.gif
2587 ms
6744721ca0ce7047c3a111005f42abdf.gif
2720 ms
824cefb227c057aedbefa087f087c7ce.gif
2754 ms
ic_my.png
1435 ms
ic_cart.png
1438 ms
ic_center.png
1441 ms
image_custom_1117235954311905.jpg
1432 ms
5f2292011f708d47ef32e14c85fceb4f.jpg
2449 ms
305bfbe9b300e41b520b4885e0f78f7c.jpg
2457 ms
220dbbc1ba372b6b4c83a7c77297cedf.jpg
4379 ms
1f6ca50c50a87f05f680ffe449300792.jpg
2489 ms
ed350a869f763d219d15743d71498d96.jpg
2493 ms
1a65fb56cce92396aeacfcf69e2221b3.jpg
2509 ms
cb2eac4a84169c825493ee8fc7a9fb7a.jpg
2497 ms
d5a99a19ff72167873f0ff37676bd7d3.jpg
2496 ms
9e961267df5e30d2b70895165e7c89c6.jpg
3522 ms
91ee83a7641f6f2f60439bf1dec485b5.jpg
2518 ms
9973f01fabc75c06c950644418528728.jpg
2500 ms
a50a8e2ae42c3202235f7f2519c25927.jpg
2505 ms
a125289632d0cda7bdef3fdb6640778b.jpg
4566 ms
6172bb3706947fa0a5de0344d5360190.jpg
2527 ms
a0246c4d16fd69f81e45b03e98bc9baa.jpg
2533 ms
f47d2df6574fd370a4f42082f32911d6.gif
2534 ms
0c7d40eedce5601a3434f85e75189530.jpg
2525 ms
200e7ac936bd18842eb3e6919d96844a.jpg
2486 ms
f9f14ce6093d6634181f70fd2739681b.jpg
2535 ms
a10eb2aa32535fe06300f348da90cac3.jpg
2493 ms
ff5676115a74ce5f75f9e2f47a833fbe.jpg
2510 ms
0c7094c348a01a9e0ed28838d60c26eb.jpg
2586 ms
0812rolling.jpg
2096 ms
300eef6150e9dc3c06d0878a88b5f895.jpg
2240 ms
a6ef2b0a1532f9d2de80449560e54da7.jpg
2245 ms
f66fc86d6a49bb543bd7eb16d828b22b.jpg
2250 ms
095ae3d3d78307de41b1d744c13a0cee.jpg
2142 ms
xeicon.ttf
1378 ms
09e5472dabdb8d7c2e80945efabf8fc6.js
658 ms
init.js
898 ms
dff02be025022e9485a33827cb432ebb.jpg
237 ms
bcc59fd1b0b29a39714dc95d71f3909b.jpg
402 ms
a25a42539b11ea0b7bd3f2c715aab3f3.png
402 ms
ct2.html
6 ms
syncframe
40 ms
analytics.js
49 ms
js
47 ms
enp_tracker_cafe24_smart.min.js
2069 ms
event
689 ms
ec.js
20 ms
SubCategory
223 ms
collect
33 ms
collect
24 ms
collect
8 ms
collect
12 ms
7732e3b0cd3663ee838b4e7afd92ab3b.jpg
492 ms
js
36 ms
js
62 ms
6a1c59db45dcd88a148800bb612f5eed.jpg
467 ms
d0039c92754228e19897829a7a48fdc1.jpg
385 ms
5640bd106ab0edf5270f3553dc417ddd.jpg
258 ms
wonlog.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
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
wonlog.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
Missing source maps for large first-party JavaScript
wonlog.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 doesn't use legible font sizes
Tap targets are not sized appropriately
![]()
KO
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wonlog.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 Wonlog.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.
wonlog.co.kr
Open Graph description is not detected on the main page of Wonlog. 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: