Tools & Wizards About Us
52flin.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

52flin.com

风林火山交流论坛 - 网购导航

Page Load Speed

23.6 sec in total

First Response

966 ms

Resources Loaded

20.6 sec

Page Rendered

2 sec

52flin.com screenshot

About Website

Visit 52flin.com now to see the best up-to-date 52 Flin content and also check out these interesting facts you probably never knew about 52flin.com

风林火山交流论坛_电脑爱好者学习与交流的平台，风林火山网购导航_汇集 淘宝特卖、天猫超市、聚划算、优惠?涣烊　⒌忍员ψ钚禄莼疃?

Visit 52flin.com

Key Findings

We analyzed 52flin.com page load time and found that the first response time was 966 ms and then it took 22.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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

52flin.com performance score

0

Network Requests Diagram

52flin.com

966 ms

wind-reset.css

197 ms

pw_ajax.js

202 ms

picplayer.js

519 ms

Deploy.js

486 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 81% of them (61 requests) were addressed to the original 52flin.com, 4% (3 requests) were made to Pagerank.webmasterhome.cn and 1% (1 request) were made to S95.cnzz.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Init.phpwind.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.6 kB (29%)

Content Size

261.2 kB

After Optimization

185.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 52flin.com main page is 261.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. 20% of websites need less resources to load. Images take 169.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 54.5 kB

  • Original 69.0 kB
  • After minification 66.0 kB
  • After compression 14.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 54.5 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 4.9 kB

  • Original 169.2 kB
  • After minification 164.3 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. 52 Flin images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 14.1 kB

  • Original 20.1 kB
  • After minification 16.6 kB
  • After compression 6.0 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 14.1 kB or 70% of the original size.

CSS Optimization

-73%

Potential reduce by 2.1 kB

  • Original 2.9 kB
  • After minification 2.3 kB
  • After compression 785 B

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. 52flin.com needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (49%)

Requests Now

69

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

52flin.com

52flin.com

966 ms

wind-reset.css

wind-reset.css

197 ms

pw_ajax.js

pw_ajax.js

202 ms

picplayer.js

picplayer.js

519 ms

Deploy.js

Deploy.js

486 ms

stat.php

stat.php

3207 ms

global.js

global.js

412 ms

init.php

init.php

19636 ms

gg1.jpg

gg1.jpg

3512 ms

logo.gif

logo.gif

2027 ms

finebbs.gif

finebbs.gif

19079 ms

tykk.gif

tykk.gif

6894 ms

MyRank

MyRank

14957 ms

headbg.png

headbg.png

355 ms

logo.png

logo.png

652 ms

navbg.png

navbg.png

363 ms

nav-globle-current.png

nav-globle-current.png

348 ms

main.png

main.png

363 ms

anc.png

anc.png

632 ms

rss.png

rss.png

648 ms

hbg.gif

hbg.gif

657 ms

cate_fold.gif

cate_fold.gif

657 ms

old.gif

old.gif

655 ms

85.jpg

85.jpg

662 ms

new.gif

new.gif

728 ms

2.jpg

2.jpg

658 ms

57.jpg

57.jpg

655 ms

12.jpg

12.jpg

653 ms

82.jpg

82.jpg

651 ms

15.jpg

15.jpg

653 ms

42.jpg

42.jpg

652 ms

41.jpg

41.jpg

651 ms

86.gif

86.gif

683 ms

78.jpg

78.jpg

651 ms

28.jpg

28.jpg

649 ms

29.jpg

29.jpg

679 ms

31.jpg

31.jpg

648 ms

55.jpg

55.jpg

708 ms

32.jpg

32.jpg

709 ms

39.jpg

39.jpg

708 ms

34.jpg

34.jpg

727 ms

35.jpg

35.jpg

721 ms

36.jpg

36.jpg

769 ms

share.gif

share.gif

795 ms

birth.gif

birth.gif

804 ms

1.jpg

1.jpg

3321 ms

2.jpg

2.jpg

7164 ms

3.jpg

3.jpg

4473 ms

4.jpg

4.jpg

3322 ms

3.jpg

3.jpg

2145 ms

logo.gif

logo.gif

2238 ms

lan.gif

lan.gif

2304 ms

80_4_b20f4a032fae7b0.gif

80_4_b20f4a032fae7b0.gif

2451 ms

online.gif

online.gif

618 ms

3.gif

3.gif

650 ms

4.gif

4.gif

546 ms

5.gif

5.gif

877 ms

72.gif

72.gif

634 ms

71.gif

71.gif

622 ms

63.gif

63.gif

621 ms

70.gif

70.gif

380 ms

69.gif

69.gif

365 ms

68.gif

68.gif

457 ms

67.gif

67.gif

454 ms

6.gif

6.gif

451 ms

focus1.gif

focus1.gif

487 ms

focus2.gif

focus2.gif

1389 ms

stat.htm

stat.htm

401 ms

core.php

core.php

1117 ms

9.gif

9.gif

4272 ms

pic1.gif

pic1.gif

1883 ms

app.gif

app.gif

3941 ms

492 ms

mypagerank.asp

mypagerank.asp

506 ms

1pagerank3.gif

1pagerank3.gif

1234 ms

SEO Factors

52flin.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 52flin.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 52flin.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

52flin.com

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