20.6 sec in total
173 ms
19.1 sec
1.4 sec
Welcome to dongyoungsang.com homepage info - get ready to check Dongyoungsang best content for South Korea right away, or after learning these important things about dongyoungsang.com
짤,짤방,움짤,웃짤,유머,웃긴,다시보기
Visit dongyoungsang.comWe analyzed Dongyoungsang.com page load time and found that the first response time was 173 ms and then it took 20.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
dongyoungsang.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value6.1 s
12/100
25%
Value4.2 s
78/100
10%
Value740 ms
40/100
30%
Value0
100/100
15%
Value8.8 s
35/100
10%
173 ms
153 ms
75 ms
168 ms
156 ms
Our browser made a total of 213 requests to load all elements on the main page. We found that 25% of them (53 requests) were addressed to the original Dongyoungsang.com, 13% (28 requests) were made to Img.iacstatic.co.kr and 8% (18 requests) were made to Ad.about.co.kr. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Hcimg.realclick.co.kr.
Page size can be reduced by 430.3 kB (38%)
1.1 MB
691.0 kB
In fact, the total size of Dongyoungsang.com main page is 1.1 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. 55% of websites need less resources to load. Javascripts take 513.1 kB which makes up the majority of the site volume.
Potential reduce by 25.1 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 25.1 kB or 80% of the original size.
Potential reduce by 29.4 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. Dongyoungsang images are well optimized though.
Potential reduce by 305.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 305.2 kB or 59% of the original size.
Potential reduce by 70.6 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. Dongyoungsang.com needs all CSS files to be minified and compressed as it can save up to 70.6 kB or 71% of the original size.
Number of requests can be reduced by 79 (38%)
209
130
The browser has sent 209 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dongyoungsang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
dongyoungsang.com
173 ms
drama
153 ms
xe.min.css
75 ms
board.css
168 ms
white.css
156 ms
star_rating.css
163 ms
jquery.rating.css
163 ms
layout.css
163 ms
style.css
169 ms
default.login.css
195 ms
jquery.min.js
250 ms
x.min.js
226 ms
xe.min.js
205 ms
jquery.tooltip.js
227 ms
global.js
224 ms
list.js
337 ms
jquery.rating.min.js
333 ms
common.js
327 ms
default.login.js
327 ms
font-awesome.min.css
398 ms
d4a3838947d53996be9cf9a4b4feaa42.ko.compiled.js
313 ms
0fb628d6cf472a314c27f240d2538077.ko.compiled.js
716 ms
f673688ff0d5e63712dd21741b8f4226.ko.compiled.js
330 ms
autolink.js
330 ms
f8825b6528ca5f3c9053060af4f5b4d5.ko.compiled.js
329 ms
ce80712d5adccc260036f8db92f81488.ko.js
329 ms
dongyoungsang.2014.9.png
61 ms
wing.01.htm
344 ms
wing.02.htm
343 ms
wing.03.htm
365 ms
main.01.htm
368 ms
main.02.htm
305 ms
main.03.htm
312 ms
main.11.htm
290 ms
main.12.htm
364 ms
main.13.htm
353 ms
main.31.htm
329 ms
main.32.htm
280 ms
main.33.htm
315 ms
wing.11.htm
437 ms
wing.12.htm
462 ms
wing.13.htm
457 ms
dongyoungsang_tag.w.png
428 ms
lineVr11.gif
441 ms
buttonBlack.gif
449 ms
new.gif
440 ms
star-matrix.gif
439 ms
arrowPagination.gif
440 ms
Rbanner_manual.dongyoungsang.png
450 ms
bgGnbVr.gif
448 ms
CCL.png
447 ms
msg.loading.gif
461 ms
_desktop.300x250.htm
336 ms
ajs.php
306 ms
ajs.php
282 ms
_desktop.160x600.htm
308 ms
rsense_ad.js
907 ms
56a0756140036486750172
677 ms
wp_ad_300.php
1607 ms
56a0763bafa46093833739
675 ms
rsense_ad.js
840 ms
ajs.php
238 ms
analytics.js
217 ms
wp_ad_160.php
1474 ms
ajs.php
119 ms
ajs.php
1160 ms
top_middle
782 ms
lg.php
133 ms
wfr.php
3427 ms
lg.php
135 ms
3640.js
280 ms
3640.js
269 ms
wfr.php
3394 ms
lg.php
160 ms
fontawesome-webfont.woff
159 ms
collect
57 ms
top_middle
696 ms
lg.php
122 ms
3640
284 ms
3640
277 ms
ajs.php
172 ms
ajs.php
149 ms
passback
195 ms
lg.php
58 ms
passback
196 ms
lg.php
54 ms
wait.gif
1322 ms
view_ad_adcrm.html
518 ms
view_ad_adcrm.html
517 ms
view_ad_adcrm.html
519 ms
jquery-1.8.2.min.js
486 ms
jquery.base64.js
436 ms
adbay.controller.v1.10.js
444 ms
base.css
450 ms
slide.css
480 ms
slide.common.js
482 ms
slide.300x250.controller.js
662 ms
slide.160x600.controller.js
683 ms
top_left
727 ms
top_left
810 ms
ad_asyn_ct_passback.html
744 ms
lg.php
27 ms
adBanner
2428 ms
adBanner
2445 ms
adBanner
2439 ms
wfr.php
2080 ms
wfr.php
2037 ms
top_middle
773 ms
top_left
687 ms
top_middle
706 ms
top_left
1525 ms
ad.js
379 ms
top_left
215 ms
top_middle
218 ms
top_middle
206 ms
ad_live.html
213 ms
passback
213 ms
ajs.php
25 ms
ajs.php
47 ms
wfr.php
990 ms
lg.php
15 ms
ad.css
256 ms
lg.php
36 ms
ad_live.html
455 ms
top_left
237 ms
wfr.php
784 ms
top_left
424 ms
wfr.php
995 ms
top_left
226 ms
jquery-1.9.1.min.js
120 ms
btn_prev.png
332 ms
btn_next.png
330 ms
d36b706114d75fdae0acd4639c470b39.jpg
327 ms
e2a5ea1dacdaf33312eb41dd09fc34b8.jpg
319 ms
d4bebf77ab49a6eddf42070cd83ce34a.jpg
321 ms
4ef91fa40e56b7f3f977869b68c3b464.jpg
321 ms
1c3f2ff5895e43d6fe830c1dc718dc5c.png
321 ms
passback
239 ms
adtruth.php
646 ms
adtruth.php
642 ms
adtruth.php
639 ms
adtruth.php
656 ms
adtruth.php
694 ms
adtruth.php
734 ms
top_left
282 ms
view_ad.html
528 ms
view_ad.html
540 ms
view_ad.html
516 ms
top_left
613 ms
adtruth.php
642 ms
prefs.js
427 ms
pkg54427_9.gif
7495 ms
jquery-1.6.2.min.js
7421 ms
ad.js
7403 ms
7deaf44fed260b6fe3e7debfa5e08833.jpg
44 ms
485ceb258e0053424d7f0bdea68bf647.jpg
30 ms
4ed10767baa9e649a051d2ed6dbadcf9.jpg
7000 ms
b5183de64c840014affc34ac47184d12.jpg
7000 ms
2d0106d326a792b0789cd28d7ddb14be.jpg
7000 ms
9405591a8b811b76fe0822f7ac85f3d9.jpg
6998 ms
233e20853aa1d406d73fb0545a805515.jpg
6998 ms
d7300d9d7e7603e6d537bfab79e74f46.jpg
6999 ms
c1bf7d1de4ebb9fb527197e8ab631ec1.png
7003 ms
di.php
6570 ms
di.php
3136 ms
di.php
2615 ms
di.php
5886 ms
di.php
1677 ms
di.php
1157 ms
di.php
679 ms
di.php
524 ms
20680af15172a0762a42c8e9b34a925c.gif
212 ms
9e4e8b073f0704de8e253c712d6aea78.jpg
212 ms
2bc2a324208beac0aeed3dedd3e82d7f.jpg
212 ms
f475d7d7c058b3dcf3adaaf18cf619ae.jpg
212 ms
5867c41c9dc40f2469ab712494400821.jpg
204 ms
c6f2e227562e07ca8cfb2ef797d3be30.jpg
212 ms
b0adf6819b97363c0d57e7296059812e.jpg
212 ms
5d563ae966c8a7467fa53a7503f8704a.jpg
213 ms
ad_live.html
280 ms
wfr.php
290 ms
wfr.php
571 ms
wfr.php
525 ms
wfr.php
574 ms
wfr.php
513 ms
wfr.php
5345 ms
wfr.php
705 ms
tgad_globe.png
552 ms
lg.php
2500 ms
35797123b6a4e5bb4066dcf14c64c8ff.jpg
399 ms
wfr.php
729 ms
300.php
837 ms
13dfe890a68f1bf69c4e421f35510576.jpg
160 ms
lg.php
2256 ms
lg.php
2222 ms
lg.php
2290 ms
3ebfed1c3c3abea9397003bbb2b47382.png
484 ms
lg.php
2049 ms
lg.php
1867 ms
rta.js
124 ms
pop_ad.php
806 ms
210.png
530 ms
CM_B_1023642.jpg
878 ms
wfr.php
485 ms
300.php
675 ms
rta.js
37 ms
pop_ad.php
490 ms
c6425aafcd27972cdae003bacc811193.jpg
27 ms
84ab6370ec97997b0037e31950318ec9.jpg
32 ms
5825a77089fba032df774c0bf800edf7.jpg
33 ms
d32bfc61d8ca86c79e2000f4641827a2.jpg
34 ms
CM_B_1023656.jpg
818 ms
lg.php
440 ms
dongyoungsang.com 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
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.
dongyoungsang.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
dongyoungsang.com SEO score
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
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dongyoungsang.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 Dongyoungsang.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.
dongyoungsang.com
Open Graph description is not detected on the main page of Dongyoungsang. 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: