Tools & Wizards About Us
hunterfrank.blog.163.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

32 sec in total

First Response

4.4 sec

Resources Loaded

27.3 sec

Page Rendered

351 ms

hunterfrank.blog.163.com screenshot

About Website

Welcome to hunterfrank.blog.163.com homepage info - get ready to check Hunter Frank Blog 163 best content for China right away, or after learning these important things about hunterfrank.blog.163.com

Visit hunterfrank.blog.163.com

Key Findings

We analyzed Hunterfrank.blog.163.com page load time and found that the first response time was 4.4 sec and then it took 27.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

hunterfrank.blog.163.com performance score

0

Network Requests Diagram

hunterfrank.blog.163.com

4365 ms

c.css

103 ms

nb.css

63 ms

bg_browser.jpg

53 ms

bg_top.jpg

179 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hunterfrank.blog.163.com, 28% (17 requests) were made to B.bst.126.net and 26% (16 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 570.8 kB (61%)

Content Size

939.1 kB

After Optimization

368.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hunterfrank.blog.163.com main page is 939.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 448.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 99.6 kB

  • Original 123.1 kB
  • After minification 123.0 kB
  • After compression 23.5 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 99.6 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 12.6 kB

  • Original 186.4 kB
  • After minification 173.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. Hunter Frank Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.3 kB

  • Original 448.7 kB
  • After minification 448.7 kB
  • After compression 138.4 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 310.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 148.4 kB

  • Original 181.0 kB
  • After minification 177.1 kB
  • After compression 32.6 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. Hunterfrank.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (36%)

Requests Now

55

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hunter Frank Blog 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

hunterfrank.blog.163.com

hunterfrank.blog.163.com

4365 ms

c.css

c.css

103 ms

nb.css

nb.css

63 ms

bg_browser.jpg

bg_browser.jpg

53 ms

bg_top.jpg

bg_top.jpg

179 ms

bg_item.png

bg_item.png

137 ms

bg_mid.jpg

bg_mid.jpg

139 ms

640

640

554 ms

20151021164647994799.jpg

20151021164647994799.jpg

5986 ms

bg_bottom.jpg

bg_bottom.jpg

96 ms

icon.png

icon.png

96 ms

6630133180817252049.jpg

6630133180817252049.jpg

1877 ms

1.0.0.js

1.0.0.js

453 ms

lnkbar.png

lnkbar.png

184 ms

image.png

image.png

199 ms

arrow24.png

arrow24.png

197 ms

newtopbaricon8.png

newtopbaricon8.png

195 ms

xcode.png

xcode.png

88 ms

pc.js

pc.js

158 ms

ph.js

ph.js

233 ms

crossdomain.html

crossdomain.html

1885 ms

crossdomain.html

crossdomain.html

2139 ms

request.s

request.s

1917 ms

analyse.png

analyse.png

19940 ms

ava.s

ava.s

1105 ms

Photo4BlogBean.getPhotoDailyStatistic.dwr

Photo4BlogBean.getPhotoDailyStatistic.dwr

1998 ms

crossdomain.html

crossdomain.html

684 ms

analyse.png

analyse.png

19678 ms

analytics.js

analytics.js

170 ms

collect

collect

74 ms

blogPhotoAd

blogPhotoAd

20466 ms

close_01.png

close_01.png

22 ms

top_bg.png

top_bg.png

21 ms

bottom_bg.png

bottom_bg.png

22 ms

left_bg.png

left_bg.png

22 ms

right_bg.png

right_bg.png

42 ms

left_top.png

left_top.png

39 ms

right_top.png

right_top.png

38 ms

left_bottom.png

left_bottom.png

45 ms

right_bottom.png

right_bottom.png

40 ms

shadow.png

shadow.png

22 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2133 ms

HomeBeanNew.getMonthStatistics.dwr

HomeBeanNew.getMonthStatistics.dwr

1533 ms

HomeBeanNew.getWeatherCityCode.dwr

HomeBeanNew.getWeatherCityCode.dwr

3014 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

4015 ms

.gif

.gif

96 ms

ava.s

ava.s

780 ms

ava.s

ava.s

2914 ms

ava.s

ava.s

3806 ms

ava.s

ava.s

927 ms

ava.s

ava.s

3505 ms

ava.s

ava.s

2673 ms

ava.s

ava.s

1411 ms

ava.s

ava.s

3386 ms

ava.s

ava.s

3769 ms

ava.s

ava.s

3415 ms

ava.s

ava.s

5316 ms

ava.s

ava.s

5626 ms

ava.s

ava.s

3769 ms

ava.s

ava.s

6510 ms

ava.s

ava.s

16071 ms

SEO Factors

hunterfrank.blog.163.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hunterfrank.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Hunterfrank.blog.163.com main page’s claimed encoding is gbk. 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.

Social Sharing Optimization

hunterfrank.blog.163.com

Open Graph description is not detected on the main page of Hunter Frank Blog 163. 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: