10.3 sec in total
739 ms
9 sec
574 ms
Click here to check amazing Ytmall content for South Korea. Otherwise, check out these important facts you probably never knew about ytmall.co.kr
기대이상의 만족을 드리는 Ytmall 종합쇼핑몰, 오늘만특가 세일, 의류, 잡화, 가구, 식품, 가전, 화장품, 브랜드, 언더웨어, 잡화, 의류, 리빙용품, 유아, 스포츠, 디지털, 가전, 쇼핑몰, 쇼핑, 종합몰, 온라인종합쇼핑몰
Visit ytmall.co.krWe analyzed Ytmall.co.kr page load time and found that the first response time was 739 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ytmall.co.kr performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value4.3 s
43/100
25%
Value4.6 s
70/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value2.5 s
98/100
10%
739 ms
704 ms
396 ms
15 ms
15 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 71% of them (104 requests) were addressed to the original Ytmall.co.kr, 3% (5 requests) were made to Code.jquery.com and 3% (5 requests) were made to Koreanmall.com. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Ytmall.co.kr.
Page size can be reduced by 515.0 kB (18%)
2.8 MB
2.3 MB
In fact, the total size of Ytmall.co.kr main page is 2.8 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. 70% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 89.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 35.1 kB, which is 32% 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 89.4 kB or 82% of the original size.
Potential reduce by 62.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. Ytmall images are well optimized though.
Potential reduce by 239.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 239.1 kB or 75% of the original size.
Potential reduce by 124.4 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. Ytmall.co.kr needs all CSS files to be minified and compressed as it can save up to 124.4 kB or 81% of the original size.
Number of requests can be reduced by 53 (38%)
139
86
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ytmall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ytmall.co.kr
739 ms
704 ms
style.css
396 ms
jquery-1.11.0.min.js
15 ms
jquery-migrate-1.2.1.min.js
15 ms
jquery-ui.js
16 ms
jquery.timers.js
450 ms
jslib.js
451 ms
searchedKwd.js
455 ms
common.js
467 ms
mini_cart.js
511 ms
ui.js
588 ms
common.js
756 ms
zoom.js
610 ms
jquery.gallery.js
667 ms
jquery.imageScroller.js
677 ms
menu.js
693 ms
jquery.cookie.js
666 ms
jquery-ui.css
10 ms
css
23 ms
css
37 ms
css
42 ms
css
45 ms
jqModal.css
760 ms
layout.css
975 ms
default.css
807 ms
third_log_script_header.js
887 ms
shopping_slide.js
897 ms
jquery.eventbanner.js
918 ms
js_rolling.js
1021 ms
nsm_log.js
813 ms
wcslog.js
245 ms
jquery.browser.min.js
918 ms
jquery.url.packed.js
918 ms
jquery.jqmodal.js
985 ms
roosevelt.js
20 ms
wp_astg_4.0.js
602 ms
sr.gif
799 ms
lang_us.jpg
276 ms
209014_a_55.jpg
274 ms
jumpRendingRibon.png
737 ms
close_btn.png
457 ms
209096_a_55.jpg
407 ms
209286_a_55.jpg
458 ms
209315_a_55.jpg
459 ms
209343_a_55.jpg
459 ms
209351_a_55.jpg
526 ms
209358_a_55.jpg
504 ms
btn_to_up.gif
606 ms
btn_to_down.gif
685 ms
160223_@bill_icon_01.jpg
684 ms
ytmall_160212_@bill_icon_02.jpg
685 ms
160217_@bill_icon_03.jpg
732 ms
160211_@bill_icon_005.jpg
779 ms
160215_@bill_icon_05.jpg
807 ms
ytmall_160219_@bill_icon_06.jpg
909 ms
160217_@bill_icon_07.jpg
912 ms
160222_@bill_icon_08.jpg
909 ms
ytmall_160226_@bill_icon_09.jpg
959 ms
ytmall_151211_@bill_icon_03.jpg
1040 ms
160127_@bill_icon_11.jpg
1006 ms
160223_@bill_icon_12.jpg
1134 ms
208658_a_320.jpg
1362 ms
207375_a_320.jpg
1597 ms
195625_a_320.jpg
1446 ms
173170_a_320.jpg
1414 ms
207378_a_320.jpg
1791 ms
208422_a_320.jpg
1813 ms
207420_a_320.jpg
1815 ms
203695_a_320.jpg
1812 ms
207490_a_320.jpg
1872 ms
200477_a_320.jpg
1822 ms
207377_a_320.jpg
2296 ms
@tr_ban.jpg
206 ms
goto_sk.png
254 ms
160223_@bill_01.jpg
1289 ms
ytmall_160212_@bill_02.jpg
793 ms
160217_@bill_03.jpg
1249 ms
160211_@bill_04.jpg
1327 ms
160215_@bill_05.jpg
988 ms
ytmall_160219_@bill_06.jpg
1027 ms
160217_@bill_07.jpg
1467 ms
160222_@bill_08.jpg
1578 ms
ytmall_160226_@bill_09.jpg
1435 ms
ytmall_151211_@bill_03.jpg
1923 ms
160127_@bill_11.jpg
2310 ms
160223_@bill_12.jpg
2016 ms
151217_@mid_ban_01.jpg
1624 ms
160119_@mid_ban_02.jpg
1692 ms
ytmall_mid_ban_03.jpg
1776 ms
arrowLeft.png
1827 ms
arrowRight.png
1917 ms
199315_a_180.jpg
1975 ms
136809_a_180.jpg
2028 ms
203877_a_180.jpg
2142 ms
168462_a_180.jpg
2146 ms
203874_a_180.jpg
2167 ms
212672_a_180.jpg
2244 ms
212671_a_180.jpg
2228 ms
212670_a_180.jpg
2366 ms
212661_a_180.jpg
2371 ms
212660_a_180.jpg
2363 ms
main_info.gif
2430 ms
analytics.js
23 ms
globalBg.jpg
933 ms
newfooterRightLink.gif
2469 ms
newFooterBottom_02.gif
2553 ms
ytlogo1224.jpg
2543 ms
collect
15 ms
collect
104 ms
NanumGothic-Regular.woff
6536 ms
cmm_set.gif
2434 ms
w5P-SI7QJQSDqB3GziL8XT8E0i7KZn-EPnyo3HZu7kw.woff
22 ms
ngc5.nsm-corp.com
1222 ms
bstrk.1.js
822 ms
ga-audiences
80 ms
bg_li.gif
2450 ms
icon_bth_mp.gif
2511 ms
bg_nav.gif
2511 ms
ASP_Conf.js
919 ms
bg_li2.gif
2034 ms
bg_more.gif
1843 ms
logger.v4.1.js
396 ms
m
642 ms
analysis.js
977 ms
ScriptServlet
45 ms
m
697 ms
social_mainBG2.gif
1815 ms
lang_kr.jpg
229 ms
ui-bg_flat_75_ffffff_40x100.png
13 ms
m
618 ms
aac
724 ms
aac
731 ms
wpc.php
473 ms
info.php
1967 ms
mSns_n.jpg
1673 ms
mSns_f.jpg
1755 ms
tracker.1.tsp
838 ms
mSns_t.jpg
1620 ms
newFooterTopBg.gif
1578 ms
ytlogobottom1224.jpg
1581 ms
widerplanet.php
583 ms
pixel
16 ms
wpc.php
1798 ms
pixel
15 ms
wpg.php
1774 ms
wpp.php
455 ms
ytmall.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ytmall.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ytmall.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
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ytmall.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 Ytmall.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.
ytmall.co.kr
Open Graph description is not detected on the main page of Ytmall. 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: