7.6 sec in total
1.6 sec
5.7 sec
397 ms
Visit yongbaksa.com now to see the best up-to-date Yongbaksa content and also check out these interesting facts you probably never knew about yongbaksa.com
글쓰고 촬영하고 편집하는 사람
Visit yongbaksa.comWe analyzed Yongbaksa.com page load time and found that the first response time was 1.6 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
yongbaksa.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value15.9 s
0/100
25%
Value14.2 s
1/100
10%
Value250 ms
85/100
30%
Value0.914
3/100
15%
Value14.6 s
8/100
10%
1558 ms
207 ms
7 ms
808 ms
201 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yongbaksa.com, 24% (35 requests) were made to Blogimgs.naver.net and 21% (30 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.1 MB (60%)
1.8 MB
716.6 kB
In fact, the total size of Yongbaksa.com main page is 1.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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 380 B
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 380 B or 44% of the original size.
Potential reduce by 39.5 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. Yongbaksa images are well optimized though.
Potential reduce by 844.3 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 844.3 kB or 74% of the original size.
Potential reduce by 212.1 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. Yongbaksa.com needs all CSS files to be minified and compressed as it can save up to 212.1 kB or 85% of the original size.
Number of requests can be reduced by 74 (51%)
144
70
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yongbaksa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yongbaksa.com
1558 ms
mycamera
207 ms
Frameset-981964519.js
7 ms
PrologueList.nhn
808 ms
NBlogHidden.nhn
201 ms
Hidden-597428542.js
4 ms
MusicPlayer-449972894.js
16 ms
LayoutTopCommon-484882993.css
9 ms
player-846d457.css
22 ms
RemoveSubDomain-dea9950.js
24 ms
Jindo152-363950062.js
26 ms
LayoutTopCommon-730083628.js
39 ms
JindoComponent-318925938.js
39 ms
PrologueWebzine-71207160.css
37 ms
gnb_quirks_euckr.nhn
111 ms
allowSwfForChrome-7dd9772.js
99 ms
LayoutBottomCommon-902441421.js
98 ms
spc.gif
1631 ms
PrologueList.nhn
1677 ms
20160125_083045.jpg
1698 ms
btn_confirm2.gif
1628 ms
CAM00968-1.jpg
1649 ms
20151222_110503_edit_edit_edit.jpg
1694 ms
20151017_203658.jpg
1688 ms
20151011_144403_HDR.jpg
1695 ms
20151003_153509_HDR.jpg
1695 ms
20150509_195252.jpg
1688 ms
20150509_194647_HDR.jpg
1696 ms
20150509_195009_HDR.jpg
1696 ms
YBS_5407_resize.JPG
1698 ms
20150408_125337.jpg
1696 ms
PicsArt_1415519608642.jpg
1697 ms
1414217929660_20141025_151630.jpg
1716 ms
1411656816776_20140921_185650.jpg
1698 ms
1408765746212_20140822_220427_HDR.jpg
1697 ms
20140801_084828.jpg
1698 ms
anigif2.gif
1699 ms
1420686860_1420682199_1.jpg
1700 ms
YBS_4490.JPG
1890 ms
1412722563390_20141007_144702.jpg
1967 ms
20140610_163128.gif
2082 ms
CX88000_front.jpg
2092 ms
%B4%CF%C4%DC_TIPA_%BE%EE%BF%F6%B5%E5_%BC%F6%BB%F3_%C1%A6%C7%B0_%C0%CC%B9%CC%C1%F6.jpg
2173 ms
i480.jpg
2496 ms
01-1200.jpg
2337 ms
20151226_151659.jpg
2486 ms
QMemo%2B_2015-12-24-23-21-51.jpg
2527 ms
20151017_175255.jpg
2612 ms
20151013_165937_edit_edit.jpg
2636 ms
20151013_165937_edit_edit.jpg
2745 ms
20151009_194505_HDR.jpg
2988 ms
ico_help.gif
1615 ms
0032_login.png
1619 ms
greenreviewWidget.png
1621 ms
btn_thin_close.gif
1616 ms
btn_close8.gif
1618 ms
ico_file.gif
1618 ms
btn_download2.gif
1618 ms
btn_cancel3.gif
1619 ms
btn_close3.gif
1620 ms
btn_close5.gif
1620 ms
btn_confirm.gif
1618 ms
btn_cancel.gif
1617 ms
btn_close_1.gif
1618 ms
btn_viewexif.gif
1619 ms
btn_originaldn.gif
1619 ms
spc.gif
1618 ms
tit_viewexif.gif
1620 ms
ico_notice2.gif
1619 ms
btn_close.gif
1619 ms
btn_close3.gif
1622 ms
btn_close.gif
1620 ms
btn_ok.gif
1620 ms
btn_close2.gif
1623 ms
btn_confirm_pop2.gif
1620 ms
btn_cancel_pop2.gif
1621 ms
btn_close.gif
1622 ms
promo_npay.png
1623 ms
0117_h982.gif
1621 ms
naverblog_banner.jpg
1615 ms
113.jpg
1642 ms
WidgetView.nhn
1600 ms
WidgetListAsync.nhn
1814 ms
m
432 ms
btn_blogsearch.gif
90 ms
shadow.png
92 ms
shadow02.png
91 ms
bg_not_available_word.gif
91 ms
0117_b982.gif
103 ms
0105_back1_2.gif
91 ms
0105_back2.gif
94 ms
0105_back3_2.gif
93 ms
0105_back4.gif
93 ms
0105_back6.gif
93 ms
0105_back7_2.gif
93 ms
0105_back8.gif
94 ms
0105_back9_2.gif
95 ms
0138_head.gif
95 ms
0138_body.gif
93 ms
0138_footer.gif
97 ms
0104_image_1.gif
95 ms
0101_back.gif
96 ms
0117_f982.gif
99 ms
getLoginStatus.nhn
522 ms
section_connect_widget2-413879d.css
45 ms
jindo.min-78c07e0.js
46 ms
agent.ie11-6694cec.js
55 ms
BuddyConnectWidget-242001126.js
53 ms
BuddyConnectBriefWidget-898830988.js
71 ms
line_skin20_v.gif
25 ms
M_2.jpg
44 ms
ico_arr2.gif
21 ms
IMG_9891_m_01.jpg
30 ms
logo.png
31 ms
login_basic.gif
20 ms
111123123.jpg
54 ms
11060949_1025342860824071_6200318686963372837_n.jpg
55 ms
icon2.jpg
38 ms
%BF%A3%C1%F8+%C0%FD%B0%B3%B5%B5.jpg
56 ms
%C1%A6%B8%F1-%BE%F8%C0%BD-2.png
66 ms
IMG_7134.jpg
68 ms
%B7%B9%C0%CE%BA%B8%BF%EC%C7%C7%BD%C3.JPG
63 ms
04.jpg
125 ms
bb00dd.jpg
98 ms
%C0%DB%C0%BA%BB%E7%C0%CC%C1%EED3S_3427.jpg
84 ms
IMGP4467.jpg
90 ms
%BA%ED%B7%CE%B1%D7.JPG
132 ms
b.gif
17 ms
ico_skin23_arr.gif
18 ms
ico_up.gif
17 ms
btn_skin20_pgn.gif
17 ms
btn_skin23_add_2.png
14 ms
btn_skin20_adm_2.png
9 ms
btn_skin20_dnld_2.png
9 ms
CAM00968-1.jpg
307 ms
0141_head.gif
39 ms
sp_widget_map_v4.png
36 ms
bg_country_v3.gif
9 ms
0141_body.gif
9 ms
0141_icon.gif
10 ms
0141_footer.gif
9 ms
promo_npay_1603.png
10 ms
clickcrD.js
4 ms
0032_menu.png
5 ms
sp_gnb_v10.png
5 ms
yongbaksa.com 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.
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
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.
yongbaksa.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
Page has valid source maps
yongbaksa.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Yongbaksa.com 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 Yongbaksa.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.
yongbaksa.com
Open Graph description is not detected on the main page of Yongbaksa. 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: