Tools & Wizards About Us
foxtory.blog.me screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

foxtory.blog.me

폭스토리 : 네이버 블로그

Page Load Speed

5.1 sec in total

First Response

608 ms

Resources Loaded

4.2 sec

Page Rendered

245 ms

foxtory.blog.me screenshot

About Website

Visit foxtory.blog.me now to see the best up-to-date Foxtory Blog content for United States and also check out these interesting facts you probably never knew about foxtory.blog.me

Visit foxtory.blog.me

Key Findings

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

Performance Metrics

foxtory.blog.me performance score

0

Network Requests Diagram

foxtory.blog.me

608 ms

foxtory

229 ms

Frameset-981964519.js

9 ms

PrologueList.nhn

609 ms

NBlogHidden.nhn

228 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Foxtory.blog.me, 31% (38 requests) were made to Blogimgs.naver.net and 18% (22 requests) were made to Blogpfthumb.phinf.naver.net. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Blogthumb2.naver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (50%)

Content Size

2.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-44%

Potential reduce by 383 B

  • Original 865 B
  • After minification 861 B
  • After compression 482 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 383 B or 44% of the original size.

Image Optimization

-4%

Potential reduce by 34.3 kB

  • Original 802.3 kB
  • After minification 768.1 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. Foxtory Blog images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 844.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 302.0 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 844.3 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 212.1 kB

  • Original 249.5 kB
  • After minification 232.7 kB
  • After compression 37.3 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. Foxtory.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.

Requests Breakdown

Number of requests can be reduced by 63 (51%)

Requests Now

123

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foxtory.blog.me

foxtory.blog.me

608 ms

foxtory

foxtory

229 ms

Frameset-981964519.js

Frameset-981964519.js

9 ms

PrologueList.nhn

PrologueList.nhn

609 ms

NBlogHidden.nhn

NBlogHidden.nhn

228 ms

Hidden-597428542.js

Hidden-597428542.js

4 ms

MusicPlayer-449972894.js

MusicPlayer-449972894.js

17 ms

LayoutTopCommon-484882993.css

LayoutTopCommon-484882993.css

8 ms

player-846d457.css

player-846d457.css

19 ms

RemoveSubDomain-dea9950.js

RemoveSubDomain-dea9950.js

22 ms

Jindo152-363950062.js

Jindo152-363950062.js

25 ms

LayoutTopCommon-730083628.js

LayoutTopCommon-730083628.js

37 ms

JindoComponent-318925938.js

JindoComponent-318925938.js

23 ms

PrologueWebzine-71207160.css

PrologueWebzine-71207160.css

36 ms

gnb_quirks_euckr.nhn

gnb_quirks_euckr.nhn

107 ms

allowSwfForChrome-7dd9772.js

allowSwfForChrome-7dd9772.js

32 ms

LayoutBottomCommon-902441421.js

LayoutBottomCommon-902441421.js

33 ms

top_skin.gif

top_skin.gif

510 ms

spc.gif

spc.gif

399 ms

PrologueList.nhn

PrologueList.nhn

438 ms

title_0315.png

title_0315.png

768 ms

btn_confirm2.gif

btn_confirm2.gif

395 ms

thumnail.png

thumnail.png

500 ms

0030_login.png

0030_login.png

393 ms

btn_confirm.gif

btn_confirm.gif

393 ms

btn_cancel.gif

btn_cancel.gif

393 ms

btn_close.gif

btn_close.gif

395 ms

ico-ccl1-by-nc-nd.gif

ico-ccl1-by-nc-nd.gif

393 ms

btn_thin_close.gif

btn_thin_close.gif

394 ms

btn_close8.gif

btn_close8.gif

395 ms

ico_file.gif

ico_file.gif

395 ms

btn_download2.gif

btn_download2.gif

395 ms

btn_cancel3.gif

btn_cancel3.gif

396 ms

btn_close3.gif

btn_close3.gif

398 ms

btn_close5.gif

btn_close5.gif

398 ms

btn_confirm.gif

btn_confirm.gif

397 ms

btn_cancel.gif

btn_cancel.gif

397 ms

btn_close_1.gif

btn_close_1.gif

400 ms

btn_viewexif.gif

btn_viewexif.gif

397 ms

btn_originaldn.gif

btn_originaldn.gif

397 ms

spc.gif

spc.gif

398 ms

tit_viewexif.gif

tit_viewexif.gif

399 ms

ico_notice2.gif

ico_notice2.gif

402 ms

btn_close.gif

btn_close.gif

399 ms

btn_close3.gif

btn_close3.gif

401 ms

btn_close.gif

btn_close.gif

402 ms

btn_ok.gif

btn_ok.gif

402 ms

btn_close2.gif

btn_close2.gif

402 ms

btn_confirm_pop2.gif

btn_confirm_pop2.gif

402 ms

btn_cancel_pop2.gif

btn_cancel_pop2.gif

403 ms

ico_help.gif

ico_help.gif

397 ms

title_0308.png

title_0308.png

981 ms

title_0304.png

title_0304.png

762 ms

title_0303.png

title_0303.png

1027 ms

title_0302.png

title_0302.png

970 ms

title_0301.png

title_0301.png

1288 ms

title_0114.png

title_0114.png

1662 ms

title_0113.png

title_0113.png

1669 ms

title_1230.png

title_1230.png

2121 ms

title_0310.png

title_0310.png

1456 ms

title_0121.png

title_0121.png

1607 ms

title_0105.png

title_0105.png

2036 ms

title_1231.png

title_1231.png

2497 ms

title_1216.png

title_1216.png

2144 ms

title_1210.png

title_1210.png

2410 ms

title_1125.png

title_1125.png

2487 ms

title_1123.png

title_1123.png

2630 ms

promo_npay.png

promo_npay.png

351 ms

title.jpg

title.jpg

1013 ms

0154_773.gif

0154_773.gif

339 ms

WidgetView.nhn

WidgetView.nhn

331 ms

WidgetListAsync.nhn

WidgetListAsync.nhn

531 ms

m

m

398 ms

btn_blogsearch.gif

btn_blogsearch.gif

67 ms

shadow.png

shadow.png

56 ms

shadow02.png

shadow02.png

57 ms

bg_not_available_word.gif

bg_not_available_word.gif

57 ms

0158_head.gif

0158_head.gif

58 ms

0106_image_1.gif

0106_image_1.gif

58 ms

section_connect_widget2-413879d.css

section_connect_widget2-413879d.css

18 ms

jindo.min-78c07e0.js

jindo.min-78c07e0.js

21 ms

agent.ie11-6694cec.js

agent.ie11-6694cec.js

19 ms

BuddyConnectWidget-242001126.js

BuddyConnectWidget-242001126.js

29 ms

BuddyConnectBriefWidget-898830988.js

BuddyConnectBriefWidget-898830988.js

50 ms

line_skin20_v.gif

line_skin20_v.gif

27 ms

img_profile_anonymous.gif

img_profile_anonymous.gif

22 ms

%25B8%25C6%25BD%25BA%25C1%25A4%25BA%25B8%25C5%25EB%25BD%25C5-%25B7%25CE%25B0%25ED.jpg

%25B8%25C6%25BD%25BA%25C1%25A4%25BA%25B8%25C5%25EB%25BD%25C5-%25B7%25CE%25B0%25ED.jpg

49 ms

login_basic.gif

login_basic.gif

47 ms

1016162_381745775258719_287143056_n.jpg

1016162_381745775258719_287143056_n.jpg

73 ms

profileImage.jpg

profileImage.jpg

468 ms

IMG_0323.jpg

IMG_0323.jpg

70 ms

naver_com_20160310_135141.png

naver_com_20160310_135141.png

82 ms

124.jpg

124.jpg

92 ms

%BF%A1%B5%E0%C4%AB%C0%CC%B7%CE%BD%BA+%B7%CE%B0%ED.jpg

%BF%A1%B5%E0%C4%AB%C0%CC%B7%CE%BD%BA+%B7%CE%B0%ED.jpg

83 ms

z.jpg

z.jpg

115 ms

profileimage.jpg

profileimage.jpg

560 ms

%25C3%25CA%25C4%25DA%25C3%25CA%25C4%25DA.jpg

%25C3%25CA%25C4%25DA%25C3%25CA%25C4%25DA.jpg

103 ms

h-logo-11-18_1_c.gif

h-logo-11-18_1_c.gif

134 ms

angel.jpg

angel.jpg

572 ms

%B4%CF%C7%CF%BF%C0%C1%F7%B1%B8.jpg

%B4%CF%C7%CF%BF%C0%C1%F7%B1%B8.jpg

513 ms

002.jpg

002.jpg

160 ms

1.PNG

1.PNG

183 ms

1.jpg

1.jpg

654 ms

zzinwang.jpg

zzinwang.jpg

240 ms

Untitled-3.jpg

Untitled-3.jpg

343 ms

ssook.gif

ssook.gif

366 ms

ico_arr2.gif

ico_arr2.gif

15 ms

b.gif

b.gif

16 ms

ico_skin24_arr.gif

ico_skin24_arr.gif

14 ms

ico_up.gif

ico_up.gif

14 ms

btn_skin20_pgn.gif

btn_skin20_pgn.gif

15 ms

btn_skin24_add_2.png

btn_skin24_add_2.png

9 ms

btn_skin20_adm_2.png

btn_skin20_adm_2.png

8 ms

btn_skin20_dnld_2.png

btn_skin20_dnld_2.png

9 ms

3911478.gif

3911478.gif

28 ms

0162_icon.gif

0162_icon.gif

25 ms

sp_widget_map_v4.png

sp_widget_map_v4.png

23 ms

thumnail.png

thumnail.png

630 ms

bg_country_v3.gif

bg_country_v3.gif

9 ms

getLoginStatus.nhn

getLoginStatus.nhn

467 ms

promo_npay_1603.png

promo_npay_1603.png

3 ms

clickcrD.js

clickcrD.js

7 ms

0030_menu.png

0030_menu.png

5 ms

sp_gnb_v10.png

sp_gnb_v10.png

5 ms

SEO Factors

foxtory.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 Foxtory.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 Foxtory.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

foxtory.blog.me

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