Tools & Wizards About Us
funnywagon.blog.me screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

funnywagon.blog.me

완전안전 : 네이버 블로그

Page Load Speed

5.8 sec in total

First Response

713 ms

Resources Loaded

4 sec

Page Rendered

1.1 sec

funnywagon.blog.me screenshot

About Website

Welcome to funnywagon.blog.me homepage info - get ready to check Funnywagon Blog best content for United States right away, or after learning these important things about funnywagon.blog.me

Visit funnywagon.blog.me

Key Findings

We analyzed Funnywagon.blog.me page load time and found that the first response time was 713 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

funnywagon.blog.me performance score

0

Network Requests Diagram

funnywagon.blog.me

713 ms

funnywagon

206 ms

Frameset-981964519.js

23 ms

PostList.nhn

356 ms

NBlogHidden.nhn

217 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Funnywagon.blog.me, 37% (38 requests) were made to Blogimgs.naver.net and 16% (16 requests) were made to T.static.blog.naver.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Postfiles16.naver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (51%)

Content Size

2.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funnywagon.blog.me main page is 2.3 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.2 MB which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 398 B

  • Original 877 B
  • After minification 873 B
  • After compression 479 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 45% of the original size.

Image Optimization

-3%

Potential reduce by 20.5 kB

  • Original 794.9 kB
  • After minification 774.4 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. Funnywagon Blog images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 918.0 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 327.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 918.0 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 248.3 kB

  • Original 292.8 kB
  • After minification 272.5 kB
  • After compression 44.5 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. Funnywagon.blog.me needs all CSS files to be minified and compressed as it can save up to 248.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (64%)

Requests Now

101

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funnywagon 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 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

funnywagon.blog.me

funnywagon.blog.me

713 ms

funnywagon

funnywagon

206 ms

Frameset-981964519.js

Frameset-981964519.js

23 ms

PostList.nhn

PostList.nhn

356 ms

NBlogHidden.nhn

NBlogHidden.nhn

217 ms

Hidden-597428542.js

Hidden-597428542.js

9 ms

MusicPlayer-449972894.js

MusicPlayer-449972894.js

25 ms

LayoutTopCommon-484882993.css

LayoutTopCommon-484882993.css

18 ms

player-846d457.css

player-846d457.css

13 ms

RemoveSubDomain-dea9950.js

RemoveSubDomain-dea9950.js

27 ms

Jindo152-363950062.js

Jindo152-363950062.js

28 ms

LayoutTopCommon-730083628.js

LayoutTopCommon-730083628.js

37 ms

JindoComponent-318925938.js

JindoComponent-318925938.js

47 ms

PostList-1027637939.css

PostList-1027637939.css

43 ms

gnb_quirks_euckr.nhn

gnb_quirks_euckr.nhn

41 ms

likeit_blog.css

likeit_blog.css

622 ms

likeit.css

likeit.css

624 ms

SeViewerBlog-165931490.css

SeViewerBlog-165931490.css

34 ms

PostTopCommon-327917359.js

PostTopCommon-327917359.js

43 ms

splugin.js

splugin.js

40 ms

PostBottomCommon-1023812380.js

PostBottomCommon-1023812380.js

42 ms

PostBottomCommon_utf8-169531666.js

PostBottomCommon_utf8-169531666.js

113 ms

likeIt.list.js

likeIt.list.js

617 ms

allowSwfForChrome-7dd9772.js

allowSwfForChrome-7dd9772.js

110 ms

LayoutBottomCommon-902441421.js

LayoutBottomCommon-902441421.js

111 ms

spc.gif

spc.gif

71 ms

PostList.nhn

PostList.nhn

284 ms

promo_npay.png

promo_npay.png

59 ms

%C5%A9%B1%E2%BA%AF%C8%AF_%BB%E7%BA%BB+-skateboarding-wallpaper-mobile-9.jpg

%C5%A9%B1%E2%BA%AF%C8%AF_%BB%E7%BA%BB+-skateboarding-wallpaper-mobile-9.jpg

1687 ms

0133_966.gif

0133_966.gif

214 ms

DSC00804.JPG

DSC00804.JPG

1790 ms

DSC00803.JPG

DSC00803.JPG

894 ms

DSC00805.JPG

DSC00805.JPG

1527 ms

DSC00806.JPG

DSC00806.JPG

1370 ms

IMG_9120.JPG

IMG_9120.JPG

1357 ms

htvo_guardians_galaxy_rocket_racoon_backpack.jpg

htvo_guardians_galaxy_rocket_racoon_backpack.jpg

1438 ms

htvo_guardians_galaxy_rocket_racoon_backpack_back.jpg

htvo_guardians_galaxy_rocket_racoon_backpack_back.jpg

889 ms

htvo_guardians_galaxy_rocket_racoon_backpack_inuse.jpg

htvo_guardians_galaxy_rocket_racoon_backpack_inuse.jpg

886 ms

IMG_9120.JPG

IMG_9120.JPG

990 ms

51EwnKQ0NXL.jpg

51EwnKQ0NXL.jpg

1456 ms

DSC00711.JPG

DSC00711.JPG

953 ms

btn_confirm2.gif

btn_confirm2.gif

39 ms

%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_IMG_9217.JPG

%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_IMG_9217.JPG

56 ms

0000_login.png

0000_login.png

39 ms

btn_qk_set.gif

btn_qk_set.gif

40 ms

btn_what2.gif

btn_what2.gif

41 ms

btn_clse_ly2.gif

btn_clse_ly2.gif

40 ms

spc.gif

spc.gif

41 ms

btn_urlcopy.gif

btn_urlcopy.gif

40 ms

btn_thin_close.gif

btn_thin_close.gif

40 ms

btn_close8.gif

btn_close8.gif

42 ms

ico_file.gif

ico_file.gif

41 ms

btn_download2.gif

btn_download2.gif

41 ms

btn_cancel3.gif

btn_cancel3.gif

40 ms

btn_close3.gif

btn_close3.gif

41 ms

btn_close5.gif

btn_close5.gif

40 ms

btn_confirm.gif

btn_confirm.gif

41 ms

btn_cancel.gif

btn_cancel.gif

41 ms

btn_close_1.gif

btn_close_1.gif

41 ms

btn_viewexif.gif

btn_viewexif.gif

42 ms

btn_originaldn.gif

btn_originaldn.gif

41 ms

tit_viewexif.gif

tit_viewexif.gif

40 ms

ico_notice2.gif

ico_notice2.gif

42 ms

btn_close.gif

btn_close.gif

42 ms

btn_close3.gif

btn_close3.gif

41 ms

btn_close.gif

btn_close.gif

42 ms

btn_ok.gif

btn_ok.gif

42 ms

btn_close2.gif

btn_close2.gif

40 ms

btn_confirm_pop2.gif

btn_confirm_pop2.gif

42 ms

btn_cancel_pop2.gif

btn_cancel_pop2.gif

42 ms

btn_close.gif

btn_close.gif

42 ms

DSC00709.JPG

DSC00709.JPG

823 ms

DSC00710.JPG

DSC00710.JPG

1128 ms

DSC00712.JPG

DSC00712.JPG

1676 ms

IMG_9120.JPG

IMG_9120.JPG

1292 ms

ico_help.gif

ico_help.gif

29 ms

bg_qk_ly2.gif

bg_qk_ly2.gif

24 ms

0008_ico1_down.gif

0008_ico1_down.gif

23 ms

MultimediaFLVPlayer.nhn

MultimediaFLVPlayer.nhn

226 ms

ico_tag.gif

ico_tag.gif

19 ms

sp_post_btn.png

sp_post_btn.png

74 ms

lg_photoviewer.gif

lg_photoviewer.gif

31 ms

btn_blogsearch.gif

btn_blogsearch.gif

16 ms

shadow.png

shadow.png

15 ms

shadow02.png

shadow02.png

18 ms

bg_not_available_word.gif

bg_not_available_word.gif

17 ms

btn_left.gif

btn_left.gif

15 ms

btn_right.gif

btn_right.gif

19 ms

btn_original2.png

btn_original2.png

17 ms

btn_close.gif

btn_close.gif

17 ms

0103_image_1.gif

0103_image_1.gif

18 ms

0113_back.gif

0113_back.gif

19 ms

WidgetListAsync.nhn

WidgetListAsync.nhn

267 ms

flvplayer-1.1.0.js

flvplayer-1.1.0.js

598 ms

%C5%A9%B1%E2%BA%AF%C8%AF_IMG_9217.JPG

%C5%A9%B1%E2%BA%AF%C8%AF_IMG_9217.JPG

32 ms

0101_icon.gif

0101_icon.gif

16 ms

btn_rst_clse.gif

btn_rst_clse.gif

14 ms

ico_f_blank.gif

ico_f_blank.gif

13 ms

ico_f_closed_l.gif

ico_f_closed_l.gif

14 ms

0008_arw.gif

0008_arw.gif

9 ms

0008_icon_down.gif

0008_icon_down.gif

8 ms

getLoginStatus.nhn

getLoginStatus.nhn

1123 ms

SEO Factors

funnywagon.blog.me SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funnywagon.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 Funnywagon.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.

Social Sharing Optimization

funnywagon.blog.me

Open Graph description is not detected on the main page of Funnywagon 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: