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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

22 sec in total

First Response

2.9 sec

Resources Loaded

18.9 sec

Page Rendered

235 ms

fengzheng369.blog.163.com screenshot

About Website

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

Visit fengzheng369.blog.163.com

Key Findings

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

Performance Metrics

fengzheng369.blog.163.com performance score

0

Network Requests Diagram

fengzheng369.blog.163.com

2935 ms

c.css

44 ms

b.css

5969 ms

6630133180817252049.jpg

534 ms

xcode.png

17 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fengzheng369.blog.163.com, 26% (21 requests) were made to Img.bimg.126.net and 22% (18 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 604.3 kB (63%)

Content Size

966.2 kB

After Optimization

361.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 83.6 kB

  • Original 106.0 kB
  • After minification 106.0 kB
  • After compression 22.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 83.6 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 10.1 kB

  • Original 152.9 kB
  • After minification 142.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. Fengzheng 369 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.5 kB

  • Original 521.7 kB
  • After minification 521.6 kB
  • After compression 163.1 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.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 152.0 kB

  • Original 185.7 kB
  • After minification 181.6 kB
  • After compression 33.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. Fengzheng369.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (50%)

Requests Now

80

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fengzheng369.blog.163.com

fengzheng369.blog.163.com

2935 ms

c.css

c.css

44 ms

b.css

b.css

5969 ms

6630133180817252049.jpg

6630133180817252049.jpg

534 ms

xcode.png

xcode.png

17 ms

1.0.0.js

1.0.0.js

92 ms

pc.js

pc.js

20 ms

ph.js

ph.js

18 ms

5770799972522187428.jpg

5770799972522187428.jpg

479 ms

icon.png

icon.png

44 ms

5779244221823515636.jpg

5779244221823515636.jpg

474 ms

5779244221823515635.jpg

5779244221823515635.jpg

514 ms

5776992422009831185.jpg

5776992422009831185.jpg

521 ms

5776992422009831184.jpg

5776992422009831184.jpg

536 ms

5776992422009831186.jpg

5776992422009831186.jpg

538 ms

5780088646753648775.jpg

5780088646753648775.jpg

707 ms

5776992422009831187.jpg

5776992422009831187.jpg

709 ms

5776992422009831188.jpg

5776992422009831188.jpg

756 ms

5776992422009831189.jpg

5776992422009831189.jpg

778 ms

5776992422009831191.jpg

5776992422009831191.jpg

801 ms

5776992422009831190.jpg

5776992422009831190.jpg

806 ms

5791347645822068511.jpg

5791347645822068511.jpg

942 ms

5791347645822068509.jpg

5791347645822068509.jpg

944 ms

5791347645822068513.jpg

5791347645822068513.jpg

994 ms

5780933071683780524.jpg

5780933071683780524.jpg

1055 ms

5791347645822068515.jpg

5791347645822068515.jpg

1065 ms

5791347645822068517.jpg

5791347645822068517.jpg

1073 ms

5791347645822068546.jpg

5791347645822068546.jpg

1177 ms

5791347645822068549.jpg

5791347645822068549.jpg

1177 ms

5791347645822068547.jpg

5791347645822068547.jpg

1232 ms

lnkbar.png

lnkbar.png

35 ms

image.png

image.png

35 ms

arrow24.png

arrow24.png

35 ms

newtopbaricon8.png

newtopbaricon8.png

35 ms

crossdomain.html

crossdomain.html

741 ms

crossdomain.html

crossdomain.html

489 ms

request.s

request.s

534 ms

analyse.png

analyse.png

599 ms

ava.s

ava.s

884 ms

Photo4BlogBean.getPhotoDailyStatistic.dwr

Photo4BlogBean.getPhotoDailyStatistic.dwr

512 ms

crossdomain.html

crossdomain.html

514 ms

ava.s

ava.s

2963 ms

analyse.png

analyse.png

588 ms

analytics.js

analytics.js

10 ms

collect

collect

14 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

776 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1413 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1467 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2523 ms

blogPhotoAd

blogPhotoAd

304 ms

close_01.png

close_01.png

7 ms

top_bg.png

top_bg.png

47 ms

bottom_bg.png

bottom_bg.png

15 ms

left_bg.png

left_bg.png

15 ms

right_bg.png

right_bg.png

11 ms

left_top.png

left_top.png

37 ms

right_top.png

right_top.png

15 ms

left_bottom.png

left_bottom.png

35 ms

right_bottom.png

right_bottom.png

15 ms

shadow.png

shadow.png

9 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1598 ms

r

r

467 ms

ad

ad

503 ms

ava.s

ava.s

471 ms

ava.s

ava.s

1163 ms

ava.s

ava.s

1406 ms

ava.s

ava.s

2855 ms

ava.s

ava.s

3229 ms

ava.s

ava.s

1481 ms

ava.s

ava.s

1918 ms

ava.s

ava.s

2338 ms

ava.s

ava.s

6319 ms

ava.s

ava.s

4817 ms

ava.s

ava.s

2334 ms

ava.s

ava.s

4148 ms

ava.s

ava.s

3298 ms

ava.s

ava.s

5180 ms

ava.s

ava.s

9474 ms

jquery-1.4.2.js

jquery-1.4.2.js

7 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

2044 ms

close2.png

close2.png

3 ms

SEO Factors

fengzheng369.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 Fengzheng369.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 Fengzheng369.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

fengzheng369.blog.163.com

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