14.7 sec in total
5.2 sec
9.1 sec
450 ms
Click here to check amazing Burning Land content. Otherwise, check out these important facts you probably never knew about burningland.co.kr
Visit burningland.co.krWe analyzed Burningland.co.kr page load time and found that the first response time was 5.2 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
burningland.co.kr performance score
5192 ms
240 ms
23 ms
741 ms
225 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Burningland.co.kr, 32% (30 requests) were made to Blogthumb2.naver.net and 31% (29 requests) were made to Blogimgs.naver.net. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Burningland.co.kr.
Page size can be reduced by 940.9 kB (64%)
1.5 MB
518.1 kB
In fact, the total size of Burningland.co.kr main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 980.3 kB which makes up the majority of the site volume.
Potential reduce by 398 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 398 B or 44% of the original size.
Potential reduce by 18.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. Burning Land images are well optimized though.
Potential reduce by 722.6 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 722.6 kB or 74% of the original size.
Potential reduce by 199.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. Burningland.co.kr needs all CSS files to be minified and compressed as it can save up to 199.6 kB or 85% of the original size.
Number of requests can be reduced by 43 (46%)
93
50
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Burning Land. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
burningland.co.kr
5192 ms
rhtjgus93
240 ms
Frameset-981964519.js
23 ms
PrologueList.nhn
741 ms
NBlogHidden.nhn
225 ms
Hidden-597428542.js
12 ms
MusicPlayer-449972894.js
27 ms
LayoutTopCommon-484882993.css
11 ms
player-846d457.css
42 ms
RemoveSubDomain-dea9950.js
57 ms
Jindo152-363950062.js
62 ms
LayoutTopCommon-730083628.js
58 ms
JindoComponent-318925938.js
111 ms
PrologueWebzine-71207160.css
59 ms
gnb_quirks_euckr.nhn
225 ms
allowSwfForChrome-7dd9772.js
55 ms
LayoutBottomCommon-902441421.js
55 ms
spc.gif
158 ms
1005_login.png
148 ms
attachImage_3483731358.jpeg
1469 ms
btn_confirm2.gif
146 ms
profileImage.jpg
1472 ms
attachImage_761081126.jpeg
1472 ms
attachImage_788283739.jpeg
1469 ms
attachImage_2220297435.jpeg
1467 ms
attachImage_168804284.jpeg
1466 ms
attachImage_4030439663.jpeg
1469 ms
dddd.jpg
1470 ms
1016.jpg
1471 ms
attachImage_3009622798.jpeg
1472 ms
attachImage_2256668205.jpeg
1471 ms
NaverBlog_20160224_084731_37.jpg
1472 ms
NaverBlog_20160223_001857_01.jpg
1469 ms
NaverBlog_20160221_162118_01.jpg
1470 ms
NaverBlog_20160220_075658_03.jpg
1488 ms
NaverBlog_20160217_181704_01.jpg
1483 ms
attachImage_3483731358.jpeg
1470 ms
attachImage_761081126.jpeg
1509 ms
attachImage_788283739.jpeg
1636 ms
attachImage_2220297435.jpeg
1933 ms
attachImage_168804284.jpeg
1902 ms
attachImage_4030439663.jpeg
1955 ms
dddd.jpg
1977 ms
1016.jpg
2045 ms
attachImage_3009622798.jpeg
2153 ms
attachImage_2256668205.jpeg
2440 ms
NaverBlog_20160224_084731_37.jpg
2436 ms
NaverBlog_20160223_001857_01.jpg
2458 ms
NaverBlog_20160221_162118_01.jpg
2503 ms
NaverBlog_20160220_075658_03.jpg
2561 ms
NaverBlog_20160217_181704_01.jpg
2660 ms
ico_help.gif
131 ms
btn_thin_close.gif
129 ms
btn_close8.gif
129 ms
ico_file.gif
129 ms
btn_download2.gif
129 ms
btn_cancel3.gif
129 ms
btn_close3.gif
129 ms
btn_close5.gif
129 ms
btn_confirm.gif
128 ms
btn_cancel.gif
129 ms
btn_close_1.gif
142 ms
btn_viewexif.gif
141 ms
btn_originaldn.gif
140 ms
spc.gif
140 ms
tit_viewexif.gif
139 ms
ico_notice2.gif
141 ms
btn_close.gif
140 ms
btn_close3.gif
141 ms
btn_close.gif
140 ms
btn_ok.gif
138 ms
btn_close2.gif
140 ms
btn_confirm_pop2.gif
139 ms
btn_cancel_pop2.gif
139 ms
btn_close.gif
139 ms
promo_npay.png
104 ms
btn_blogsearch.gif
146 ms
shadow.png
144 ms
shadow02.png
162 ms
bg_not_available_word.gif
146 ms
0101_image.gif
163 ms
WidgetListAsync.nhn
1408 ms
m
654 ms
ExternalWidgetRender.nhn
915 ms
ExternalWidgetRender.nhn
919 ms
ExternalWidgetRender.nhn
950 ms
getLoginStatus.nhn
724 ms
profileImage.jpg
457 ms
0162_icon.gif
19 ms
btn_layer_close.gif
17 ms
promo_npay_1603.png
14 ms
clickcrD.js
13 ms
1005_menu.png
11 ms
sp_gnb_v10.png
14 ms
burningland.co.kr SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Burningland.co.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Burningland.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.
burningland.co.kr
Open Graph description is not detected on the main page of Burning Land. 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: