2.8 sec in total
638 ms
1.9 sec
264 ms
Click here to check amazing YES Sarang content for United States. Otherwise, check out these important facts you probably never knew about yes.sarang.com
Visit yes.sarang.comWe analyzed Yes.sarang.com page load time and found that the first response time was 638 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
yes.sarang.com performance score
638 ms
218 ms
147 ms
149 ms
150 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 89% of them (81 requests) were addressed to the original Yes.sarang.com, 4% (4 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (638 ms) belongs to the original domain Yes.sarang.com.
Page size can be reduced by 454.8 kB (28%)
1.6 MB
1.2 MB
In fact, the total size of Yes.sarang.com main page is 1.6 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 22.5 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 22.5 kB or 78% of the original size.
Potential reduce by 177.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. Obviously, YES Sarang needs image optimization as it can save up to 177.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 194.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 194.2 kB or 67% of the original size.
Potential reduce by 60.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. Yes.sarang.com needs all CSS files to be minified and compressed as it can save up to 60.4 kB or 84% of the original size.
Number of requests can be reduced by 44 (49%)
90
46
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of YES Sarang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
yes.sarang.com
638 ms
style.css
218 ms
ddsmoothmenu.css
147 ms
contentslider.css
149 ms
jquery.fancybox-1.3.1.css
150 ms
slider.css
152 ms
aboutus.css
216 ms
twitter.css
222 ms
mission.css
223 ms
earlypray.css
223 ms
jquery.min.js
390 ms
jquery.easing.1.2.js
285 ms
jquery.anythingslider.js
286 ms
anythingslider.js
289 ms
animatedcollapse.js
290 ms
colapse.js
293 ms
ddsmoothmenu.js
354 ms
menu.js
354 ms
contentslider.js
358 ms
ddaccordion.js
360 ms
acrodin.js
363 ms
jquery.fancybox-1.3.1.js
492 ms
lightbox.js
424 ms
menu-collapsed.js
427 ms
colorbox.css
429 ms
bbpress.css
521 ms
jquery.js
531 ms
jquery.colorbox-min.js
496 ms
player.js
497 ms
cont_slide.js
409 ms
ga.js
7 ms
__utm.gif
12 ms
widgets.js
82 ms
yes_bg.jpg
215 ms
sitemap.gif
70 ms
contactus.gif
88 ms
wrapper_bg.png
89 ms
head_bg_yes.gif
88 ms
search.gif
88 ms
go.gif
139 ms
NEWYEAR_WEB.jpg
286 ms
2014chosen_web.jpg
545 ms
webbanner.jpg
370 ms
TGIF_2013-681x334.jpg
376 ms
middlebar_bg.png
280 ms
JAEJA-41-1-150x150.jpg
283 ms
JAEJA-41-2-150x150.jpg
350 ms
NEW-32-1-150x150.jpg
354 ms
NEW-32-2-150x150.jpg
355 ms
NEW-32-3-150x150.jpg
420 ms
NEW-32-4-150x150.jpg
423 ms
NEW-32-5-150x150.jpg
424 ms
NEW-32-6-150x150.jpg
439 ms
NEW-32-7-150x150.jpg
445 ms
PAN-15-150x150.jpg
495 ms
SJ-40-150x150.jpg
496 ms
20141011_153310-150x150.jpg
496 ms
IMG_7071-150x150.jpg
543 ms
IMG_8393-150x150.jpg
543 ms
IMG_8401-150x150.jpg
576 ms
IMG_8403-150x150.jpg
576 ms
IMG_1723-150x150.jpg
577 ms
IMG_1658-150x150.jpg
576 ms
IMG_8206-150x150.jpg
604 ms
IMG_8025-150x150.jpg
605 ms
IMG_6968-150x150.jpg
632 ms
DSC_9131-150x150.jpg
633 ms
facebook_icon.png
633 ms
twitter_icon.png
636 ms
triple_img1.jpg
618 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
140 ms
triple_podcast.png
597 ms
triple_img3.jpg
621 ms
heading.gif
622 ms
lfooter.jpg
623 ms
rfooter.jpg
582 ms
little_arrows.png
541 ms
syndication
79 ms
347416404561113089
207 ms
sitemap_pressed.png
476 ms
contactus_pressed.png
493 ms
dropdown.gif
498 ms
overlay.png
430 ms
controls.png
443 ms
border.png
468 ms
loading_background.png
457 ms
loading.gif
471 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
28 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
81 ms
podcast_logo_normal.png
220 ms
jot
25 ms
yes.sarang.com SEO score
KO
UT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yes.sarang.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed language. Our system also found out that Yes.sarang.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.
yes.sarang.com
Open Graph description is not detected on the main page of YES Sarang. 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: