11.2 sec in total
863 ms
7.5 sec
2.8 sec
Visit naebange.com now to see the best up-to-date Naebange content and also check out these interesting facts you probably never knew about naebange.com
내방에 놓으면 딱 좋은!!! 상품들을 까다롭게 엄선하여 제안합니다 !,·´″```°³о♡
Visit naebange.comWe analyzed Naebange.com page load time and found that the first response time was 863 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
naebange.com performance score
863 ms
382 ms
397 ms
400 ms
395 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 95% of them (179 requests) were addressed to the original Naebange.com, 2% (3 requests) were made to Web4.logcounter.com and 1% (2 requests) were made to Serial4.logcounter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Naebange.com.
Page size can be reduced by 1.0 MB (21%)
4.8 MB
3.7 MB
In fact, the total size of Naebange.com main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 261.7 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 261.7 kB or 89% of the original size.
Potential reduce by 661.3 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, Naebange needs image optimization as it can save up to 661.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 95.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 95.6 kB or 74% of the original size.
Number of requests can be reduced by 21 (11%)
188
167
The browser has sent 188 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naebange. 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.
naebange.com
863 ms
product_list.js
382 ms
bookmark.js
397 ms
design_func.js
400 ms
search_topmuti.js
395 ms
flash.js
597 ms
wcslog.js
19 ms
logo_top.gif
607 ms
top_m1.gif
571 ms
top_bar.gif
582 ms
top_m2.gif
583 ms
top_m3.gif
591 ms
top_m4.gif
978 ms
top_m5.gif
979 ms
top_m6.gif
980 ms
top_ban1.gif
981 ms
top_ban2.gif
982 ms
ban_naver.gif
983 ms
ban_open.gif
985 ms
top_menu1.gif
986 ms
topmenu_bar.gif
1080 ms
top_menu2.gif
1083 ms
top_menu3.gif
1084 ms
top_menu4.gif
1084 ms
top_menu5.gif
1161 ms
topbbs_bar.gif
1167 ms
spacer.gif
1178 ms
category_title.gif
1180 ms
ban_leftcus.gif
1195 ms
delivery.gif
1202 ms
news_title.gif
1357 ms
ban_main1.jpg
1557 ms
ban_main2.jpg
1413 ms
hot_title.gif
1216 ms
0200050000293.jpg
1620 ms
515
1232 ms
537
1384 ms
Log_script_logsid.html
1407 ms
cookie.js
1236 ms
rightbanner.js
1374 ms
shopRbanner.html
1383 ms
shopMiniBanner.html
1409 ms
shopMiniBanner.html
1229 ms
0200050000233.jpg
1615 ms
0200050000113.jpg
1569 ms
0200050000093.jpg
1571 ms
0200050000273.jpg
1596 ms
0200050000083.jpg
1395 ms
m
466 ms
get_flash_player.gif
77 ms
517
1020 ms
0200050000333.jpg
1413 ms
0200060000083.jpg
1213 ms
532
1366 ms
0200060000403.jpg
1374 ms
522
1405 ms
0200060000093.jpg
1415 ms
0200060000363.jpg
1319 ms
0200060000343.jpg
1655 ms
0200060000323.jpg
1477 ms
0200020000063.jpg
1700 ms
0200020000053.jpg
1502 ms
0200020000043.jpg
1626 ms
0200020000023.jpg
1428 ms
0200020000013.jpg
1584 ms
0200010000043.jpg
1805 ms
500
1598 ms
510
1728 ms
0200010000073.jpg
1801 ms
recommend_title.gif
1598 ms
0200050000343.jpg
1782 ms
498
1432 ms
0200050000103.jpg
1571 ms
0200050000043.jpg
1599 ms
[sr].gif
659 ms
mslog.js
812 ms
0200020000153.jpg
1596 ms
0200020000163.jpg
1589 ms
0200010000013.jpg
1772 ms
0200010000063.jpg
1590 ms
0200030000103.jpg
1593 ms
0200030000063.jpg
1601 ms
0200030000053.jpg
1600 ms
0200030000083.jpg
1409 ms
0200030000223.jpg
1561 ms
0200040000043.jpg
1455 ms
0200040000023.jpg
1448 ms
0200040000123.jpg
1423 ms
0200040000013.jpg
1426 ms
0200040000053.jpg
1536 ms
Conf_mylife024.js
603 ms
0200040000103.jpg
1414 ms
0200060000553.jpg
1451 ms
0200060000543.jpg
1417 ms
0200060000533.jpg
1420 ms
0200060000523.jpg
1418 ms
0200060000513.jpg
1530 ms
ms.log
402 ms
0200060000423.jpg
1404 ms
0200060000413.jpg
1413 ms
0200060000313.jpg
1411 ms
0200060000153.jpg
1285 ms
recommend_bt.gif
1259 ms
new_title.jpg
1342 ms
0200010000023.jpg
1371 ms
0200010000033.jpg
1403 ms
[sr].gif
594 ms
emd_pt.js
807 ms
0200010000113.jpg
1268 ms
0200010000053.jpg
1236 ms
0200020000033.jpg
1234 ms
0200020000073.jpg
1331 ms
0200020000093.jpg
1221 ms
0200020000123.jpg
1245 ms
0200020000133.jpg
1227 ms
0200130000273.jpg
1245 ms
0200040000183.jpg
1243 ms
0200040000173.jpg
1347 ms
0200050000263.jpg
1203 ms
0200050000323.jpg
1225 ms
0200060000383.jpg
1216 ms
0200060000353.jpg
1231 ms
0200060000433.jpg
1238 ms
HTTP_s.js
1174 ms
0200060000393.jpg
1213 ms
0200060000373.jpg
1199 ms
0200060000503.jpg
1210 ms
0200060000493.jpg
1208 ms
0200060000483.jpg
1225 ms
0200060000103.jpg
1220 ms
0200060000073.jpg
1211 ms
0200060000053.jpg
1195 ms
0200060000063.jpg
1202 ms
0200060000133.jpg
1213 ms
0200060000143.jpg
1229 ms
0200060000173.jpg
1228 ms
0200060000163.jpg
1218 ms
0200060000033.jpg
1187 ms
0200060000043.jpg
1204 ms
0200060000023.jpg
1213 ms
0200060000013.jpg
1220 ms
0200070000383.jpg
1220 ms
0200070000093.jpg
1219 ms
0200070000083.jpg
1193 ms
0200060000213.jpg
1204 ms
0200100000093.jpg
1217 ms
0200100000113.jpg
1223 ms
0200100000453.jpg
1226 ms
519
1223 ms
0200100000483.jpg
1194 ms
0200080000093.jpg
1197 ms
0200080000083.jpg
1211 ms
0200080000073.jpg
1213 ms
0200090000033.jpg
1216 ms
0200090000073.jpg
1216 ms
0200030000033.jpg
1199 ms
0200030000093.jpg
1196 ms
0200030000133.jpg
1213 ms
0200090000063.jpg
1209 ms
0200090000023.jpg
1205 ms
0200090000013.jpg
1209 ms
0200090000053.jpg
1208 ms
0200100000053.jpg
1199 ms
0200100000033.jpg
1208 ms
0200070000223.jpg
1203 ms
0200070000373.jpg
1213 ms
ban_btcus1.gif
1209 ms
ban_btcus2.gif
1212 ms
qna_title.gif
1201 ms
review_title.gif
1201 ms
bottombanner14.gif
1195 ms
bottombanner6.gif
1207 ms
bottombanner2_KOOKMIN.gif
1196 ms
bottombanner13.gif
1211 ms
bottombanner4.gif
1200 ms
bottombanner7.gif
1208 ms
bottombanner16.gif
1196 ms
bt_m1.gif
1208 ms
bt_m2.gif
1197 ms
bt_m3.gif
1210 ms
bt_m4.gif
1200 ms
bt_m5.gif
1201 ms
bt_home.gif
1192 ms
bt_top.gif
1203 ms
logo_bt.gif
1191 ms
business_license1.gif
1210 ms
topmenu_bg.gif
1199 ms
recommend_bg.gif
1200 ms
mobileshop_rbanner.gif
1199 ms
naebange.com SEO score
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naebange.com 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 Naebange.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
naebange.com
Open Graph description is not detected on the main page of Naebange. 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: