10.4 sec in total
1.1 sec
8.9 sec
417 ms
Welcome to nemo.ne.kr homepage info - get ready to check Nemo Ne best content right away, or after learning these important things about nemo.ne.kr
Visit nemo.ne.krWe analyzed Nemo.ne.kr page load time and found that the first response time was 1.1 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
nemo.ne.kr performance score
1145 ms
211 ms
11 ms
563 ms
203 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nemo.ne.kr, 27% (36 requests) were made to Blogimgs.naver.net and 21% (28 requests) were made to Blogimgs.naver.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Post.phinf.naver.net.
Page size can be reduced by 1.8 MB (50%)
3.5 MB
1.8 MB
In fact, the total size of Nemo.ne.kr main page is 3.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. 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. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 395 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 395 B or 44% of the original size.
Potential reduce by 132.6 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. Nemo Ne images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 75% 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. Nemo.ne.kr 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 79 (59%)
134
55
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nemo Ne. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
nemo.ne.kr
1145 ms
hoon8007
211 ms
Frameset-981964519.js
11 ms
PrologueList.nhn
563 ms
NBlogHidden.nhn
203 ms
Hidden-597428542.js
7 ms
MusicPlayer-449972894.js
20 ms
LayoutTopCommon-484882993.css
17 ms
player-846d457.css
30 ms
RemoveSubDomain-dea9950.js
24 ms
Jindo152-363950062.js
29 ms
LayoutTopCommon-730083628.js
23 ms
JindoComponent-318925938.js
44 ms
PrologueWebzine-71207160.css
22 ms
gnb_quirks_euckr.nhn
238 ms
allowSwfForChrome-7dd9772.js
69 ms
0273_head.jpg
42 ms
spc.gif
531 ms
attachImage_1542232525.jpeg
557 ms
btn_confirm2.gif
20 ms
0010.jpg
21 ms
0011_login.png
743 ms
ico-ccl4-by-nc-nd.gif
550 ms
btn_thin_close.gif
529 ms
btn_close8.gif
530 ms
ico_file.gif
529 ms
btn_download2.gif
529 ms
btn_cancel3.gif
531 ms
btn_close3.gif
531 ms
btn_close5.gif
532 ms
btn_confirm.gif
533 ms
btn_cancel.gif
533 ms
btn_close_1.gif
533 ms
btn_viewexif.gif
534 ms
btn_originaldn.gif
537 ms
spc.gif
535 ms
tit_viewexif.gif
534 ms
ico_notice2.gif
536 ms
btn_close.gif
538 ms
btn_close3.gif
536 ms
btn_close.gif
538 ms
btn_ok.gif
538 ms
btn_close2.gif
539 ms
btn_confirm_pop2.gif
540 ms
btn_cancel_pop2.gif
540 ms
btn_close.gif
540 ms
ico_help.gif
13 ms
mosadjE9kS.jpeg
567 ms
IMG_1458.JPG
547 ms
IMG_0876.JPG
545 ms
IMG_0951.JPG
546 ms
attachImage_1542232525.jpeg
565 ms
IMG_0743.JPG
1247 ms
IMG_0522.jpg
1250 ms
IMG_0497.png
1251 ms
Untitled-1.jpg
1249 ms
IMG_4169.jpg
1248 ms
attachImage_2670698081.jpeg
1251 ms
eav9flxjmhoajhzj7nwt.jpg
1484 ms
LayoutBottomCommon-902441421.js
6 ms
promo_npay.png
46 ms
0155_966.gif
38 ms
WidgetView.nhn
431 ms
blog2.nhn
672 ms
btn_blogsearch.gif
324 ms
shadow.png
325 ms
shadow02.png
326 ms
bg_not_available_word.gif
326 ms
0105_back1_2.gif
12 ms
0105_back2.gif
13 ms
0105_back3_2.gif
62 ms
0105_back4.gif
300 ms
0105_back6.gif
63 ms
0105_back7_2.gif
62 ms
0105_back8.gif
62 ms
0105_back9_2.gif
62 ms
0101_back.gif
298 ms
0142_head.gif
300 ms
0142_body.gif
61 ms
0142_footer.gif
61 ms
ccl-4.gif
62 ms
0128_image.gif
293 ms
weather_6_bg.png
61 ms
WidgetListAsync.nhn
640 ms
m
741 ms
section_connect_widget2-413879d.css
4 ms
jindo.min-78c07e0.js
5 ms
agent.ie11-6694cec.js
16 ms
BuddyConnectWidget-242001126.js
15 ms
BuddyConnectBriefWidget-898830988.js
33 ms
line_skin20_v.gif
22 ms
%25BB%25F3%25BF%25EB2.jpg
610 ms
IMG_0803.JPG
604 ms
0400011209_40476_012.gif
608 ms
%BC%D5.jpg
604 ms
%BA%ED%B7%CE%B1%D7%C7%C1%B7%CE%C7%CA%BB%E7%C1%F8.jpg
17 ms
%BC%AE%BE%E7-591-seushj.jpg
608 ms
logo.jpg
21 ms
1425742409303.jpeg
22 ms
login_basic.gif
24 ms
profileimage.jpg
749 ms
dilma.png
1004 ms
profileImage.jpg
1051 ms
BATMAN1.jpg
602 ms
-IMG_6363.JPG
604 ms
IMG_1310.png
605 ms
ico_arr2.gif
14 ms
b.gif
17 ms
ico_skin21_arr.gif
16 ms
ico_up.gif
14 ms
btn_skin20_pgn.gif
15 ms
btn_skin21_add_2.png
10 ms
btn_skin20_adm_2.png
10 ms
btn_skin20_dnld_2.png
10 ms
ExternalWidgetRender.nhn
1498 ms
sp_postwidget_150409.png
14 ms
mug_obj_143254157751715027.jpg
6032 ms
post_base.js
23 ms
jindo_component.js
18 ms
mug.pubcenter.postWidget.js
12 ms
2703121.gif
297 ms
0145_head.gif
297 ms
weather_6_3.png
30 ms
0010.jpg
1220 ms
sp_widget_map_v4.png
16 ms
bg_country_v3.gif
15 ms
0145_body.gif
16 ms
0145_icon.gif
28 ms
0145_footer.gif
105 ms
getLoginStatus.nhn
697 ms
2016021813030001_Dis_20160218130303.jpg
2211 ms
promo_npay_1603.png
11 ms
clickcrD.js
12 ms
0011_menu.png
10 ms
sp_gnb_v10.png
7 ms
nemo.ne.kr SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nemo.ne.kr 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 Nemo.ne.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.
nemo.ne.kr
Open Graph description is not detected on the main page of Nemo Ne. 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: