Tools & Wizards About Us
52fuyu.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

52fuyu.com

富裕信息网APP下载页

Page Load Speed

22.3 sec in total

First Response

1.8 sec

Resources Loaded

20.2 sec

Page Rendered

268 ms

52fuyu.com screenshot

About Website

Click here to check amazing 52 Fuyu content. Otherwise, check out these important facts you probably never knew about 52fuyu.com

富裕信息网APP下载

Visit 52fuyu.com

Key Findings

We analyzed 52fuyu.com page load time and found that the first response time was 1.8 sec and then it took 20.4 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

52fuyu.com performance score

0

Network Requests Diagram

forum.php

1841 ms

style_1_common.css

558 ms

style_1_forum_index.css

564 ms

style.css

565 ms

common.js

572 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 41% of them (39 requests) were addressed to the original 52fuyu.com, 56% (53 requests) were made to 52fuyu.com.hk01.51cdngo.com and 2% (2 requests) were made to Tcss.qq.com. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source 52fuyu.com.hk01.51cdngo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.4 kB (56%)

Content Size

302.6 kB

After Optimization

133.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 50.2 kB

  • Original 63.1 kB
  • After minification 61.4 kB
  • After compression 12.9 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 50.2 kB or 79% of the original size.

Image Optimization

-16%

Potential reduce by 16.6 kB

  • Original 101.8 kB
  • After minification 85.2 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. Obviously, 52 Fuyu needs image optimization as it can save up to 16.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 55.9 kB

  • Original 76.8 kB
  • After minification 64.4 kB
  • After compression 20.9 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 55.9 kB or 73% of the original size.

CSS Optimization

-77%

Potential reduce by 46.8 kB

  • Original 60.9 kB
  • After minification 59.0 kB
  • After compression 14.2 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. 52fuyu.com needs all CSS files to be minified and compressed as it can save up to 46.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (25%)

Requests Now

55

After Optimization

41

  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 52 Fuyu. 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

forum.php

forum.php

1841 ms

style_1_common.css

style_1_common.css

558 ms

style_1_forum_index.css

style_1_forum_index.css

564 ms

style.css

style.css

565 ms

common.js

common.js

572 ms

forum.js

forum.js

581 ms

logging.js

logging.js

584 ms

title.js

title.js

836 ms

ping.js

ping.js

937 ms

1251125.js

1251125.js

1031 ms

style_1_common.css

style_1_common.css

7156 ms

style_1_forum_index.css

style_1_forum_index.css

5336 ms

style.css

style.css

5335 ms

common.js

common.js

5740 ms

forum.js

forum.js

6276 ms

logging.js

logging.js

5743 ms

title.js

title.js

5898 ms

logo.png

logo.png

284 ms

bgimg.jpg

bgimg.jpg

1537 ms

qq_login.gif

qq_login.gif

286 ms

list.gif

list.gif

289 ms

collapsed_no.gif

collapsed_no.gif

298 ms

forum.gif

forum.gif

286 ms

forum_new.gif

forum_new.gif

295 ms

c2cd2de0f345943ba9821e3b18eb084b.jpg

c2cd2de0f345943ba9821e3b18eb084b.jpg

560 ms

d6402fd5ed1d536d5c8f2a69932d0999.jpg

d6402fd5ed1d536d5c8f2a69932d0999.jpg

567 ms

fdff4746aa6b3adf21e17114ba5b80e0.jpg

fdff4746aa6b3adf21e17114ba5b80e0.jpg

569 ms

78877217a28b6fc4dc049ca0f5b4cbb4.jpg

78877217a28b6fc4dc049ca0f5b4cbb4.jpg

570 ms

11cfc4cce45915ee5495821fc65391ab.jpg

11cfc4cce45915ee5495821fc65391ab.jpg

583 ms

8af667fdfe4e41ae2bf724ea0779166a.jpg

8af667fdfe4e41ae2bf724ea0779166a.jpg

587 ms

3fd68e9dafeaa19ce3ee3e0aa06ba352.jpg

3fd68e9dafeaa19ce3ee3e0aa06ba352.jpg

836 ms

1fc6848aaa54690a80b31763c5e499b4.jpg

1fc6848aaa54690a80b31763c5e499b4.jpg

844 ms

5231729564ed2a5203c63b22fe0b6c5c.jpg

5231729564ed2a5203c63b22fe0b6c5c.jpg

845 ms

5d9c400b89796ba94a1f5960dc203980.jpg

5d9c400b89796ba94a1f5960dc203980.jpg

847 ms

0b279faac018fc82c52129aefc288673.jpg

0b279faac018fc82c52129aefc288673.jpg

869 ms

a16f51cb91ac12212d7f618c0d46443b.jpg

a16f51cb91ac12212d7f618c0d46443b.jpg

876 ms

d95fe3da0b94338af7adb9fffd5a4e20.jpg

d95fe3da0b94338af7adb9fffd5a4e20.jpg

1110 ms

6f319ebc80731ac8d65f55235accd129.jpg

6f319ebc80731ac8d65f55235accd129.jpg

1121 ms

collapsed_yes.gif

collapsed_yes.gif

1135 ms

px.png

px.png

1448 ms

pn.png

pn.png

585 ms

nv.png

nv.png

430 ms

qmenu.png

qmenu.png

443 ms

nv_a.png

nv_a.png

426 ms

search.png

search.png

1060 ms

arrwd.gif

arrwd.gif

862 ms

search.png

search.png

874 ms

pt_item.png

pt_item.png

1012 ms

chart.png

chart.png

1464 ms

titlebg.png

titlebg.png

1492 ms

dot.gif

dot.gif

1641 ms

title.png

title.png

1727 ms

listbg.gif

listbg.gif

1040 ms

NzE1Mjc5MQ==.js

NzE1Mjc5MQ==.js

353 ms

scrolltop.png

scrolltop.png

6619 ms

logo.png

logo.png

4485 ms

qq_login.gif

qq_login.gif

2404 ms

forum.gif

forum.gif

1931 ms

list.gif

list.gif

2053 ms

forum_new.gif

forum_new.gif

2683 ms

collapsed_no.gif

collapsed_no.gif

2516 ms

c2cd2de0f345943ba9821e3b18eb084b.jpg

c2cd2de0f345943ba9821e3b18eb084b.jpg

3446 ms

d6402fd5ed1d536d5c8f2a69932d0999.jpg

d6402fd5ed1d536d5c8f2a69932d0999.jpg

2893 ms

fdff4746aa6b3adf21e17114ba5b80e0.jpg

fdff4746aa6b3adf21e17114ba5b80e0.jpg

3536 ms

78877217a28b6fc4dc049ca0f5b4cbb4.jpg

78877217a28b6fc4dc049ca0f5b4cbb4.jpg

4562 ms

11cfc4cce45915ee5495821fc65391ab.jpg

11cfc4cce45915ee5495821fc65391ab.jpg

3658 ms

8af667fdfe4e41ae2bf724ea0779166a.jpg

8af667fdfe4e41ae2bf724ea0779166a.jpg

3830 ms

3fd68e9dafeaa19ce3ee3e0aa06ba352.jpg

3fd68e9dafeaa19ce3ee3e0aa06ba352.jpg

4448 ms

1fc6848aaa54690a80b31763c5e499b4.jpg

1fc6848aaa54690a80b31763c5e499b4.jpg

4277 ms

5231729564ed2a5203c63b22fe0b6c5c.jpg

5231729564ed2a5203c63b22fe0b6c5c.jpg

4365 ms

5d9c400b89796ba94a1f5960dc203980.jpg

5d9c400b89796ba94a1f5960dc203980.jpg

5872 ms

0b279faac018fc82c52129aefc288673.jpg

0b279faac018fc82c52129aefc288673.jpg

5001 ms

a16f51cb91ac12212d7f618c0d46443b.jpg

a16f51cb91ac12212d7f618c0d46443b.jpg

5142 ms

d95fe3da0b94338af7adb9fffd5a4e20.jpg

d95fe3da0b94338af7adb9fffd5a4e20.jpg

5053 ms

6f319ebc80731ac8d65f55235accd129.jpg

6f319ebc80731ac8d65f55235accd129.jpg

5363 ms

listbg.gif

listbg.gif

5257 ms

collapsed_yes.gif

collapsed_yes.gif

6144 ms

71_avatar_small.jpg

71_avatar_small.jpg

333 ms

28_avatar_small.jpg

28_avatar_small.jpg

335 ms

91_avatar_small.jpg

91_avatar_small.jpg

557 ms

34_avatar_small.jpg

34_avatar_small.jpg

542 ms

noavatar_small.gif

noavatar_small.gif

582 ms

40_avatar_small.jpg

40_avatar_small.jpg

343 ms

32_avatar_small.jpg

32_avatar_small.jpg

344 ms

33_avatar_small.jpg

33_avatar_small.jpg

543 ms

71_avatar_small.jpg

71_avatar_small.jpg

2212 ms

28_avatar_small.jpg

28_avatar_small.jpg

2217 ms

34_avatar_small.jpg

34_avatar_small.jpg

1967 ms

91_avatar_small.jpg

91_avatar_small.jpg

1978 ms

noavatar_small.gif

noavatar_small.gif

1931 ms

40_avatar_small.jpg

40_avatar_small.jpg

1984 ms

32_avatar_small.jpg

32_avatar_small.jpg

4322 ms

02_avatar_small.jpg

02_avatar_small.jpg

292 ms

33_avatar_small.jpg

33_avatar_small.jpg

2049 ms

02_avatar_small.jpg

02_avatar_small.jpg

1831 ms

SEO Factors

52fuyu.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 52fuyu.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 52fuyu.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

52fuyu.com

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