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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

19.2 sec in total

First Response

5.5 sec

Resources Loaded

12.5 sec

Page Rendered

1.2 sec

qdh68.blog.163.com screenshot

About Website

Visit qdh68.blog.163.com now to see the best up-to-date Qdh 68 Blog 163 content for China and also check out these interesting facts you probably never knew about qdh68.blog.163.com

Visit qdh68.blog.163.com

Key Findings

We analyzed Qdh68.blog.163.com page load time and found that the first response time was 5.5 sec and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

qdh68.blog.163.com performance score

0

Network Requests Diagram

qdh68.blog.163.com

5537 ms

c.css

178 ms

nb.css

145 ms

banner.jpg

3278 ms

tab.jpg

19 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Qdh68.blog.163.com, 56% (35 requests) were made to B.bst.126.net and 13% (8 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Api.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.4 kB (59%)

Content Size

1.0 MB

After Optimization

429.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qdh68.blog.163.com main page is 1.0 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. 40% of websites need less resources to load. Javascripts take 522.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 99.6 kB

  • Original 125.0 kB
  • After minification 124.9 kB
  • After compression 25.4 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 80% of the original size.

Image Optimization

-4%

Potential reduce by 9.3 kB

  • Original 216.8 kB
  • After minification 207.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. Qdh 68 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.7 kB

  • Original 522.0 kB
  • After minification 522.0 kB
  • After compression 163.3 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 358.7 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.8 kB

  • Original 182.7 kB
  • After minification 178.8 kB
  • After compression 32.9 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. Qdh68.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qdh68.blog.163.com

qdh68.blog.163.com

5537 ms

c.css

c.css

178 ms

nb.css

nb.css

145 ms

banner.jpg

banner.jpg

3278 ms

tab.jpg

tab.jpg

19 ms

icon.png

icon.png

132 ms

6630133180817252049.jpg

6630133180817252049.jpg

1984 ms

1.0.0.js

1.0.0.js

113 ms

pc.js

pc.js

107 ms

ph.js

ph.js

102 ms

web-c.jpg

web-c.jpg

86 ms

web-a.jpg

web-a.jpg

88 ms

bg-c.gif

bg-c.gif

93 ms

bg-a.gif

bg-a.gif

92 ms

bg-b.gif

bg-b.gif

96 ms

bg-d.gif

bg-d.gif

94 ms

bg-e.gif

bg-e.gif

98 ms

bg-f.gif

bg-f.gif

101 ms

bg-g.gif

bg-g.gif

97 ms

bg-h.gif

bg-h.gif

99 ms

web-b.jpg

web-b.jpg

98 ms

xcode.png

xcode.png

101 ms

lnkbar.png

lnkbar.png

81 ms

image.png

image.png

84 ms

arrow24.png

arrow24.png

89 ms

newtopbaricon8.png

newtopbaricon8.png

89 ms

crossdomain.html

crossdomain.html

6355 ms

crossdomain.html

crossdomain.html

3154 ms

request.s

request.s

1149 ms

analyse.png

analyse.png

1040 ms

ava.s

ava.s

3177 ms

nb.css

nb.css

43 ms

BlogCircleBean.getUserShowCircles.dwr

BlogCircleBean.getUserShowCircles.dwr

1128 ms

crossdomain.html

crossdomain.html

894 ms

empty.png

empty.png

16 ms

background.gif

background.gif

6 ms

player_02.gif

player_02.gif

16 ms

player_06.gif

player_06.gif

15 ms

player_16.gif

player_16.gif

15 ms

player_17.gif

player_17.gif

17 ms

stopping.gif

stopping.gif

20 ms

player_23.gif

player_23.gif

17 ms

timeline_1.gif

timeline_1.gif

17 ms

player_29.gif

player_29.gif

19 ms

analyse.png

analyse.png

907 ms

analytics.js

analytics.js

94 ms

collect

collect

61 ms

blogPhotoAd

blogPhotoAd

490 ms

close_01.png

close_01.png

23 ms

top_bg.png

top_bg.png

23 ms

bottom_bg.png

bottom_bg.png

23 ms

left_bg.png

left_bg.png

17 ms

right_bg.png

right_bg.png

14 ms

left_top.png

left_top.png

27 ms

right_top.png

right_top.png

29 ms

left_bottom.png

left_bottom.png

31 ms

right_bottom.png

right_bottom.png

30 ms

shadow.png

shadow.png

19 ms

r

r

777 ms

ad

ad

2122 ms

close2.png

close2.png

42 ms

jquery-1.4.2.js

jquery-1.4.2.js

210 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

1646 ms

SEO Factors

qdh68.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 Qdh68.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 Qdh68.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

qdh68.blog.163.com

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