10.5 sec in total
908 ms
6.9 sec
2.6 sec
Click here to check amazing Depound content for South Korea. Otherwise, check out these important facts you probably never knew about depound.com
일상 생활의 자연스러운 아름다움을 담은 감성 라이프를 제안하는 depound 입니다.
Visit depound.comWe analyzed Depound.com page load time and found that the first response time was 908 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.
depound.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value22.5 s
0/100
25%
Value17.0 s
0/100
10%
Value7,670 ms
0/100
30%
Value0.002
100/100
15%
Value33.9 s
0/100
10%
908 ms
435 ms
441 ms
439 ms
39 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 32% of them (26 requests) were addressed to the original Depound.com, 9% (7 requests) were made to App-storage-edge-006.cafe24.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source App-storage-edge-006.cafe24.com.
Page size can be reduced by 1.2 MB (14%)
8.8 MB
7.6 MB
In fact, the total size of Depound.com main page is 8.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 7.3 MB which makes up the majority of the site volume.
Potential reduce by 83.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 83.3 kB or 76% of the original size.
Potential reduce by 84.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. Depound images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 75% of the original size.
Number of requests can be reduced by 41 (55%)
74
33
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Depound. 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 5 to 1 for CSS and as a result speed up the page load time.
depound.com
908 ms
tracekit-0.4.6.js
435 ms
jet.js
441 ms
common.js
439 ms
css
39 ms
css
82 ms
nanumgothic.css
53 ms
jquery-1.11.0.min.js
46 ms
cid.generate.js
425 ms
wcslog.js
245 ms
moment.php
601 ms
optimizer.php
550 ms
optimizer.php
707 ms
slick.min.js
743 ms
lightwidget.js
85 ms
ld.js
80 ms
kp.js
986 ms
enliple_min2.js
1973 ms
i18n.php
1486 ms
optimizer.php
1261 ms
optimizer.php
984 ms
optimizer.php
701 ms
optimizer.php
703 ms
optimizer.php
704 ms
c229da541521bc637785a1533571601a.jpg
3084 ms
4f7be7df69af3871409c40947945d646.jpg
3085 ms
cefc2717d3ef8f5ca4a1c6189bbc8f3c.jpg
3169 ms
16be4b46a00ec5e0bf6b0fcca8cc1663.jpg
3083 ms
6e63afd9f0b143f5f311db52273c5db1.jpg
3037 ms
ebefdab9024f1c516308183c26a2525d.jpg
3080 ms
5827958985c69b9f0631e382a0928f69.jpg
3353 ms
baloonicon.png
469 ms
sns_instagram.png
494 ms
logo.png
469 ms
txt_progress.gif
436 ms
img_loading.gif
433 ms
btn_go.gif
436 ms
btn_close.gif
436 ms
logo_inicis.png
518 ms
logo_ftc.png
717 ms
logo_ssl.png
717 ms
btn_sitetop.png
716 ms
main_on.png
391 ms
main_off.png
968 ms
mainbn.jpg
2566 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
115 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
272 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
298 ms
PN_3Rfi-oW3hYwmKDpxS7F_D-djb.ttf
54 ms
PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsj.ttf
54 ms
PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsj.ttf
54 ms
a15ecfac0c235bb4a2047c40c62b216c.html
242 ms
124814728_275791837197002_1425420558240542178_n.jpg
1753 ms
124936038_737898390157485_7179952449080473020_n.jpg
2272 ms
124190218_365435521357296_4936297985212843072_n.jpg
2555 ms
124031653_193810288870305_672278963643315253_n.jpg
2853 ms
123886067_2683414655245317_137783706013423388_n.jpg
2764 ms
123997638_361990925035184_8800010447092355170_n.jpg
3267 ms
m
1570 ms
fbevents.js
553 ms
analytics.js
670 ms
js
753 ms
bc
1625 ms
trs_esc.js
1250 ms
2178518489144660
257 ms
conversion_async.js
340 ms
135 ms
event
1292 ms
86 ms
104 ms
117 ms
61 ms
50 ms
38 ms
19 ms
ec.js
363 ms
async
483 ms
bg_worldship.gif
103 ms
collect
182 ms
collect
61 ms
collect
58 ms
scriptTags
1045 ms
depound.com 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
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.
depound.com 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
depound.com 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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Depound.com 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 Depound.com 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.
depound.com
Open Graph description is not detected on the main page of Depound. 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: