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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

18.8 sec in total

First Response

4.3 sec

Resources Loaded

14.2 sec

Page Rendered

287 ms

dgzbh.blog.163.com screenshot

About Website

Click here to check amazing Dgzbh Blog 163 content for China. Otherwise, check out these important facts you probably never knew about dgzbh.blog.163.com

Visit dgzbh.blog.163.com

Key Findings

We analyzed Dgzbh.blog.163.com page load time and found that the first response time was 4.3 sec and then it took 14.5 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

dgzbh.blog.163.com performance score

0

Network Requests Diagram

dgzbh.blog.163.com

4261 ms

c.css

582 ms

b.css

664 ms

r

1074 ms

ava.s

708 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dgzbh.blog.163.com, 15% (11 requests) were made to Imgsize.ph.126.net and 14% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Img2.126.net.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

437.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 57.2 kB

  • Original 73.0 kB
  • After minification 73.0 kB
  • After compression 15.8 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 57.2 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 15.3 kB

  • Original 214.0 kB
  • After minification 198.7 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. Dgzbh Blog 163 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 406.4 kB

  • Original 593.9 kB
  • After minification 593.9 kB
  • After compression 187.5 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 406.4 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 154.8 kB

  • Original 189.8 kB
  • After minification 184.5 kB
  • After compression 34.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. Dgzbh.blog.163.com needs all CSS files to be minified and compressed as it can save up to 154.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (44%)

Requests Now

70

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dgzbh.blog.163.com

dgzbh.blog.163.com

4261 ms

c.css

c.css

582 ms

b.css

b.css

664 ms

r

r

1074 ms

ava.s

ava.s

708 ms

6630133180817252049.jpg

6630133180817252049.jpg

5036 ms

xcode.png

xcode.png

1248 ms

1.0.0.js

1.0.0.js

1267 ms

pc.js

pc.js

592 ms

ph.js

ph.js

589 ms

goodbloghead.png

goodbloghead.png

33 ms

4564961172310468132.jpg

4564961172310468132.jpg

1257 ms

2869918862558887485.jpg

2869918862558887485.jpg

2696 ms

4022277417212311633.jpg

4022277417212311633.jpg

1258 ms

icon.png

icon.png

30 ms

lnkbar.png

lnkbar.png

32 ms

image.png

image.png

30 ms

arrow24.png

arrow24.png

30 ms

newtopbaricon8.png

newtopbaricon8.png

32 ms

rec.s

rec.s

2634 ms

crossdomain.html

crossdomain.html

800 ms

crossdomain.html

crossdomain.html

1347 ms

crossdomain.html

crossdomain.html

2257 ms

request.s

request.s

1856 ms

analyse.png

analyse.png

2773 ms

163NewsList.do

163NewsList.do

663 ms

mailEntry.do

mailEntry.do

1024 ms

analyse.png

analyse.png

971 ms

analytics.js

analytics.js

7 ms

collect

collect

18 ms

imgsize.ph.126.net

imgsize.ph.126.net

1163 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

985 ms

imgsize.ph.126.net

imgsize.ph.126.net

805 ms

imgsize.ph.126.net

imgsize.ph.126.net

803 ms

imgsize.ph.126.net

imgsize.ph.126.net

805 ms

imgsize.ph.126.net

imgsize.ph.126.net

808 ms

imgsize.ph.126.net

imgsize.ph.126.net

808 ms

imgsize.ph.126.net

imgsize.ph.126.net

871 ms

imgsize.ph.126.net

imgsize.ph.126.net

872 ms

statistic.png

statistic.png

506 ms

statistic.png

statistic.png

683 ms

blogPhotoAd

blogPhotoAd

538 ms

close_01.png

close_01.png

8 ms

top_bg.png

top_bg.png

10 ms

bottom_bg.png

bottom_bg.png

11 ms

left_bg.png

left_bg.png

12 ms

right_bg.png

right_bg.png

13 ms

left_top.png

left_top.png

14 ms

right_top.png

right_top.png

13 ms

left_bottom.png

left_bottom.png

11 ms

right_bottom.png

right_bottom.png

14 ms

shadow.png

shadow.png

12 ms

r

r

494 ms

imgsize.ph.126.net

imgsize.ph.126.net

71 ms

imgsize.ph.126.net

imgsize.ph.126.net

138 ms

imgsize.ph.126.net

imgsize.ph.126.net

72 ms

reset.css

reset.css

750 ms

ad.css

ad.css

747 ms

51e662be174440c1a9ff16081977e61c.jpg

51e662be174440c1a9ff16081977e61c.jpg

2461 ms

jquery-1.4.2.js

jquery-1.4.2.js

749 ms

scroll.js

scroll.js

746 ms

244b05ba6131405a9df0c6f4753fc804.jpg

244b05ba6131405a9df0c6f4753fc804.jpg

2459 ms

6fb1637b14fc42998f7e67a42c218e9b.jpg

6fb1637b14fc42998f7e67a42c218e9b.jpg

2459 ms

5f0713d0f8c84c25ae333e6a9b15154d.jpg

5f0713d0f8c84c25ae333e6a9b15154d.jpg

2896 ms

cabb80cb39b7476a94491c59c9f019ec.jpg

cabb80cb39b7476a94491c59c9f019ec.jpg

2517 ms

ba554616bcc7406fa8df5a72e64fab0c.jpg

ba554616bcc7406fa8df5a72e64fab0c.jpg

2528 ms

ad

ad

1072 ms

logo-24.png

logo-24.png

42 ms

discount-1.png

discount-1.png

41 ms

close2.png

close2.png

5 ms

jquery-1.4.2.js

jquery-1.4.2.js

6 ms

0321ykt-300-250.jpg

0321ykt-300-250.jpg

5074 ms

SEO Factors

dgzbh.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 Dgzbh.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 Dgzbh.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

dgzbh.blog.163.com

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