Tools & Wizards About Us
fenhongshe.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

12.2 sec in total

First Response

135 ms

Resources Loaded

12 sec

Page Rendered

142 ms

fenhongshe.net screenshot

About Website

Click here to check amazing Fenhongshe content. Otherwise, check out these important facts you probably never knew about fenhongshe.net

Visit fenhongshe.net

Key Findings

We analyzed Fenhongshe.net page load time and found that the first response time was 135 ms and then it took 12.1 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

fenhongshe.net performance score

0

Network Requests Diagram

forum.php

135 ms

style_6_common.css

129 ms

style_6_forum_index.css

139 ms

common.js

199 ms

style_6_widthauto.css

141 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 89% of them (56 requests) were addressed to the original Fenhongshe.net, 5% (3 requests) were made to Api.bjbmyj.com and 3% (2 requests) were made to Qq.zhuaqu.org.cn. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source Api.bjbmyj.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 511.2 kB (40%)

Content Size

1.3 MB

After Optimization

751.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fenhongshe.net main page is 1.3 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. 50% of websites need less resources to load. Images take 662.8 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 48.3 kB

  • Original 90.3 kB
  • After minification 87.9 kB
  • After compression 42.0 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 48.3 kB or 54% of the original size.

Image Optimization

-8%

Potential reduce by 53.9 kB

  • Original 662.8 kB
  • After minification 608.9 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. Fenhongshe images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 329.3 kB

  • Original 412.7 kB
  • After minification 276.8 kB
  • After compression 83.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 329.3 kB or 80% of the original size.

CSS Optimization

-82%

Potential reduce by 79.7 kB

  • Original 96.8 kB
  • After minification 77.7 kB
  • After compression 17.1 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. Fenhongshe.net needs all CSS files to be minified and compressed as it can save up to 79.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (15%)

Requests Now

61

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forum.php

forum.php

135 ms

style_6_common.css

style_6_common.css

129 ms

style_6_forum_index.css

style_6_forum_index.css

139 ms

common.js

common.js

199 ms

style_6_widthauto.css

style_6_widthauto.css

141 ms

forum.js

forum.js

141 ms

jquery.js

jquery.js

352 ms

load.js

load.js

190 ms

nv.js

nv.js

190 ms

d.js

d.js

189 ms

18610521.js

18610521.js

727 ms

Count.js

Count.js

5498 ms

discuz_tips.js

discuz_tips.js

2591 ms

bg.png

bg.png

127 ms

logo.png

logo.png

67 ms

search.png

search.png

69 ms

m.png

m.png

66 ms

qqlogin.png

qqlogin.png

65 ms

post1.png

post1.png

73 ms

home.png

home.png

119 ms

embg.png

embg.png

121 ms

162214pm3sna37qpaqdpsm.jpg

162214pm3sna37qpaqdpsm.jpg

248 ms

233857e3u6vnnrqgw76o2z.gif

233857e3u6vnnrqgw76o2z.gif

310 ms

3f4db997a4a0d507ff8521662e9cb799.jpg

3f4db997a4a0d507ff8521662e9cb799.jpg

234 ms

3e9908b4878db90293adbf000b22cceb.jpg

3e9908b4878db90293adbf000b22cceb.jpg

300 ms

7a5ea338d95f8041a5739453b8541af7.jpg

7a5ea338d95f8041a5739453b8541af7.jpg

316 ms

2364297b33914515413db21aafed606d.jpg

2364297b33914515413db21aafed606d.jpg

426 ms

8d310a1de3f019cba1b56cbe29e6eced.jpg

8d310a1de3f019cba1b56cbe29e6eced.jpg

374 ms

common_extra.js

common_extra.js

312 ms

6e8c755d89c181d85a89003eb837def9.jpg

6e8c755d89c181d85a89003eb837def9.jpg

358 ms

chart.png

chart.png

497 ms

collapsed_no.gif

collapsed_no.gif

507 ms

common_2_icon.png

common_2_icon.png

570 ms

common_36_icon.png

common_36_icon.png

548 ms

common_39_icon.png

common_39_icon.png

553 ms

common_44_icon.png

common_44_icon.png

622 ms

064551t2rygeildrrgvvyv.jpg

064551t2rygeildrrgvvyv.jpg

623 ms

common_40_icon.png

common_40_icon.png

578 ms

plugin.php

plugin.php

706 ms

common_42_icon.png

common_42_icon.png

573 ms

common_43_icon.png

common_43_icon.png

656 ms

common_46_icon.png

common_46_icon.png

600 ms

common_41_icon.png

common_41_icon.png

628 ms

common_45_icon.png

common_45_icon.png

647 ms

pic_nv_prev.gif

pic_nv_prev.gif

580 ms

pic_nv_next.gif

pic_nv_next.gif

617 ms

fhs.png

fhs.png

595 ms

noavatar_big.gif

noavatar_big.gif

386 ms

noavatar_big.gif

noavatar_big.gif

404 ms

noavatar_big.gif

noavatar_big.gif

435 ms

noavatar_big.gif

noavatar_big.gif

392 ms

noavatar_big.gif

noavatar_big.gif

380 ms

noavatar_big.gif

noavatar_big.gif

380 ms

noavatar_big.gif

noavatar_big.gif

401 ms

noavatar_big.gif

noavatar_big.gif

447 ms

noavatar_big.gif

noavatar_big.gif

392 ms

noavatar_big.gif

noavatar_big.gif

391 ms

noavatar_big.gif

noavatar_big.gif

381 ms

ApiSus.php

ApiSus.php

475 ms

sv.php

sv.php

6102 ms

FangkeHa.php

FangkeHa.php

4260 ms

FangkeGo.php

FangkeGo.php

538 ms

scrolltop.png

scrolltop.png

65 ms

SEO Factors

fenhongshe.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fenhongshe.net 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 Fenhongshe.net 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

fenhongshe.net

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