7 sec in total
664 ms
5.9 sec
416 ms
Click here to check amazing Au 9999 Blog content for United States. Otherwise, check out these important facts you probably never knew about au9999.blog.me
Visit au9999.blog.meWe analyzed Au9999.blog.me page load time and found that the first response time was 664 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
au9999.blog.me performance score
664 ms
211 ms
9 ms
772 ms
214 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Au9999.blog.me, 23% (34 requests) were made to Blogimgs.naver.net and 22% (33 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.7 MB (61%)
2.8 MB
1.1 MB
In fact, the total size of Au9999.blog.me main page is 2.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.9 MB which makes up the majority of the site volume.
Potential reduce by 382 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 382 B or 44% of the original size.
Potential reduce by 73.8 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, Au 9999 Blog needs image optimization as it can save up to 73.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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. Au9999.blog.me 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 67 (45%)
148
81
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Au 9999 Blog. 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.
au9999.blog.me
664 ms
au9999
211 ms
Frameset-981964519.js
9 ms
PrologueList.nhn
772 ms
NBlogHidden.nhn
214 ms
Hidden-597428542.js
8 ms
MusicPlayer-449972894.js
16 ms
LayoutTopCommon-484882993.css
16 ms
player-846d457.css
13 ms
RemoveSubDomain-dea9950.js
33 ms
Jindo152-363950062.js
32 ms
LayoutTopCommon-730083628.js
44 ms
JindoComponent-318925938.js
42 ms
PrologueWebzine-71207160.css
61 ms
gnb_quirks_euckr.nhn
110 ms
allowSwfForChrome-7dd9772.js
95 ms
LayoutBottomCommon-902441421.js
57 ms
777777.jpg
766 ms
spc.gif
319 ms
5.jpg
460 ms
btn_confirm2.gif
315 ms
S.jpg
317 ms
14.jpg
643 ms
53.jpg
593 ms
anigif.gif
514 ms
44.jpg
480 ms
27.jpg
477 ms
21.jpg
1176 ms
8.jpg
997 ms
15.jpg
1176 ms
1.jpg
950 ms
40.jpg
1196 ms
12.jpg
1081 ms
76.jpg
1365 ms
anigif.gif
1600 ms
78.jpg
1517 ms
16.jpg
1671 ms
7555.jpg
1641 ms
123.jpg
1727 ms
6.jpg
1824 ms
7.jpg
2026 ms
111.jpg
2050 ms
anigif.gif
2124 ms
1.jpg
2114 ms
P1160097.JPG
2392 ms
333.jpg
2354 ms
2.jpg
2454 ms
12744617_1048813365171526_2946396430602582015_n.jpg
2556 ms
123.jpg
2623 ms
1.jpg
2685 ms
22222.jpg
2838 ms
11.jpg
2882 ms
11.jpg
2887 ms
4444.jpg
3274 ms
ico_help.gif
303 ms
0000_login.png
313 ms
ico_n.gif
313 ms
btn_thin_close.gif
314 ms
btn_close8.gif
314 ms
ico_file.gif
314 ms
btn_download2.gif
314 ms
btn_cancel3.gif
315 ms
btn_close3.gif
316 ms
btn_close5.gif
315 ms
btn_confirm.gif
316 ms
btn_cancel.gif
316 ms
btn_close_1.gif
316 ms
btn_viewexif.gif
316 ms
btn_originaldn.gif
315 ms
spc.gif
315 ms
tit_viewexif.gif
316 ms
ico_notice2.gif
315 ms
btn_close.gif
315 ms
btn_close3.gif
316 ms
btn_close.gif
316 ms
btn_ok.gif
316 ms
btn_close2.gif
316 ms
btn_confirm_pop2.gif
315 ms
btn_cancel_pop2.gif
316 ms
btn_close.gif
317 ms
promo_npay.png
284 ms
0155_966.gif
284 ms
blog2.nhn
732 ms
WidgetView.nhn
264 ms
WidgetListAsync.nhn
469 ms
m
473 ms
btn_blogsearch.gif
36 ms
shadow.png
35 ms
shadow02.png
34 ms
bg_not_available_word.gif
35 ms
0137_back8.gif
36 ms
0102_image.gif
69 ms
section_connect_widget2-413879d.css
9 ms
jindo.min-78c07e0.js
11 ms
agent.ie11-6694cec.js
20 ms
BuddyConnectWidget-242001126.js
19 ms
BuddyConnectBriefWidget-898830988.js
34 ms
IMG_1982.jpg
468 ms
ico_arr2.gif
17 ms
b.gif
17 ms
2013-11-18+17%3B23%3B54.jpg
13 ms
iqltm13432.JPG
13 ms
profileImage.jpg
14 ms
%BB%E7%C1%F8%B1%E2.gif
14 ms
1.jpg
34 ms
devil.png
33 ms
%C1%A6%B8%F1-%BE%F8%C0%BD-1%2B%281%29.jpg
43 ms
main.jpg
127 ms
111.jpg
13 ms
ddoddochi.png
117 ms
guc_bs_fw15_066_resize.jpg
68 ms
%C7%EC%B5%E5%C6%F92.png
37 ms
1111.jpg
39 ms
004.jpg
68 ms
%C7%C1%B7%CE%C7%CA-1.jpg
66 ms
line_skin20_v.gif
21 ms
ico_skin21_arr.gif
21 ms
ico_up.gif
39 ms
btn_skin20_pgn.gif
38 ms
btn_skin21_add_2.png
49 ms
btn_skin20_adm_2.png
47 ms
btn_skin20_dnld_2.png
54 ms
thumb_179_185.gif
35 ms
972645.gif
56 ms
0153_head.gif
26 ms
S.jpg
42 ms
0153_body.gif
41 ms
0153_icon.gif
23 ms
0153_footer.gif
51 ms
ExternalWidgetRender.nhn
1517 ms
ExternalWidgetRender.nhn
1535 ms
ExternalWidgetRender.nhn
1546 ms
ExternalWidgetRender.nhn
1560 ms
ExternalWidgetRender.nhn
1590 ms
ExternalWidgetRender.nhn
1646 ms
ExternalWidgetRender.nhn
2096 ms
ExternalWidgetRender.nhn
2227 ms
sp_postwidget_150409.png
286 ms
post_base.js
316 ms
jindo_component.js
304 ms
mug.pubcenter.postWidget.js
278 ms
getLoginStatus.nhn
448 ms
promo_npay_1603.png
3 ms
clickcrD.js
52 ms
0000_menu.png
6 ms
sp_gnb_v10.png
3 ms
100001286163481.2601.280109301.png
1020 ms
88.jpg
65 ms
daddy_widget_green.jpg
46 ms
100001286163481.2601.280109301.png
1035 ms
au9999.blog.me 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 Au9999.blog.me 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 Au9999.blog.me 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.
au9999.blog.me
Open Graph description is not detected on the main page of Au 9999 Blog. 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: