Tools & Wizards About Us
fanxing.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fanxing.com

酷狗直播 | 就是歌手多

Page Load Speed

40.6 sec in total

First Response

2.7 sec

Resources Loaded

37.3 sec

Page Rendered

579 ms

fanxing.com screenshot

About Website

Welcome to fanxing.com homepage info - get ready to check Fanxing best content for China right away, or after learning these important things about fanxing.com

酷狗直播，是酷狗音乐的直播平台，提供歌手、主播的视频直播，打造歌手明星的演唱会直播、数亿粉丝的聊天交友互动、高清流畅的直播体验，是一个音乐直播平台。酷狗直播，就是歌手多。

Visit fanxing.com

Key Findings

We analyzed Fanxing.com page load time and found that the first response time was 2.7 sec and then it took 37.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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

fanxing.com performance score

0

Network Requests Diagram

fanxing.com

2722 ms

fanxing.kugou.com

1247 ms

kguser.js

1467 ms

KgAck.js

3973 ms

index_b7be9c1.css

3733 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fanxing.com, 34% (29 requests) were made to S3.fx.kgimg.com and 29% (25 requests) were made to P3.fx.kgimg.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Imge.kugou.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 660.9 kB (31%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fanxing.com main page is 2.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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 223.0 kB

  • Original 269.4 kB
  • After minification 228.5 kB
  • After compression 46.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. This page needs HTML code to be minified as it can gain 40.9 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 223.0 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 168.3 kB

  • Original 1.5 MB
  • After minification 1.3 MB

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, Fanxing needs image optimization as it can save up to 168.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 189.9 kB

  • Original 280.4 kB
  • After minification 280.4 kB
  • After compression 90.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 189.9 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 79.6 kB

  • Original 99.2 kB
  • After minification 98.7 kB
  • After compression 19.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. Fanxing.com needs all CSS files to be minified and compressed as it can save up to 79.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (8%)

Requests Now

83

After Optimization

76

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fanxing.com

fanxing.com

2722 ms

fanxing.kugou.com

fanxing.kugou.com

1247 ms

kguser.js

kguser.js

1467 ms

KgAck.js

KgAck.js

3973 ms

index_b7be9c1.css

index_b7be9c1.css

3733 ms

head_ae9cf3d.css

head_ae9cf3d.css

3738 ms

jquery.min_18e9830.js

jquery.min_18e9830.js

2487 ms

kg_d8ec61b.js

kg_d8ec61b.js

2498 ms

head_a0cbf47.js

head_a0cbf47.js

2280 ms

picWall2015_d2b2e56.js

picWall2015_d2b2e56.js

1974 ms

logoNom_7777652.jpg

logoNom_7777652.jpg

3501 ms

menu-arrow_1b603fd.png

menu-arrow_1b603fd.png

1819 ms

yellow_warn2_b8d73e7.png

yellow_warn2_b8d73e7.png

2249 ms

bg2013_2015_f530136.png

bg2013_2015_f530136.png

3909 ms

yellow_warn_0473de0.png

yellow_warn_0473de0.png

1813 ms

footer1_369dc54.png

footer1_369dc54.png

2257 ms

20160407202308301853.jpg

20160407202308301853.jpg

4344 ms

topStar.png

topStar.png

3575 ms

blank.png

blank.png

3521 ms

20160328163229696170.png

20160328163229696170.png

3762 ms

20160328160858311848.png

20160328160858311848.png

3765 ms

20160328155113415942.png

20160328155113415942.png

4144 ms

20160405195523782079.jpg

20160405195523782079.jpg

4380 ms

20160407203033467713.jpg

20160407203033467713.jpg

4446 ms

20160406212505587180.jpg

20160406212505587180.jpg

4648 ms

20160405200415631361.jpg

20160405200415631361.jpg

5111 ms

20160401094656478070.jpg

20160401094656478070.jpg

4819 ms

20160328211831759397.jpg

20160328211831759397.jpg

5014 ms

4068.jpg

4068.jpg

5059 ms

4019.jpg

4019.jpg

5082 ms

4074.jpg

4074.jpg

5283 ms

4070.jpg

4070.jpg

5529 ms

4072.jpg

4072.jpg

5490 ms

4075.jpg

4075.jpg

5741 ms

4071.jpg

4071.jpg

5535 ms

4073.jpg

4073.jpg

5786 ms

loading.gif

loading.gif

5731 ms

footer2_abcdbc5.png

footer2_abcdbc5.png

6192 ms

indexIcon2015_06a0934.png

indexIcon2015_06a0934.png

3686 ms

fx_loading_c785dd3.gif

fx_loading_c785dd3.gif

2246 ms

bg2013_d41139f.png

bg2013_d41139f.png

8004 ms

index_z_b4fd8c0.png

index_z_b4fd8c0.png

8573 ms

footer_logo_16e645b.gif

footer_logo_16e645b.gif

2198 ms

serveraddr.serviceweb.kugou.com

serveraddr.serviceweb.kugou.com

236 ms

hm.js

hm.js

467 ms

song

song

736 ms

1794 ms

1773 ms

1763 ms

0_5

0_5

1352 ms

T1nPdCBC_s1RCvBVdK.jpg

T1nPdCBC_s1RCvBVdK.jpg

1825 ms

T1gPZCBsDg1RCvBVdK.jpg

T1gPZCBsDg1RCvBVdK.jpg

1823 ms

T1hGdCB7xs1RCvBVdK.jpg

T1hGdCB7xs1RCvBVdK.jpg

1829 ms

T1AGZCByVs1RCvBVdK.jpg

T1AGZCByVs1RCvBVdK.jpg

1635 ms

T1lvCCBsdg1RCvBVdK.jpg

T1lvCCBsdg1RCvBVdK.jpg

1662 ms

T1nIKCBgV_1RCvBVdK.jpg

T1nIKCBgV_1RCvBVdK.jpg

1928 ms

T1cPZCBCKb1RCvBVdK.jpg

T1cPZCBCKb1RCvBVdK.jpg

2310 ms

T1APZCBmhQ1RCvBVdK.jpg

T1APZCBmhQ1RCvBVdK.jpg

2337 ms

T1zPKCB4Jg1RCvBVdK.jpg

T1zPKCB4Jg1RCvBVdK.jpg

2492 ms

T1SGKCBTLg1RCvBVdK.jpg

T1SGKCBTLg1RCvBVdK.jpg

3401 ms

T1rvdCBCbs1RCvBVdK.jpg

T1rvdCBCbs1RCvBVdK.jpg

2514 ms

T1jvJCB5_j1RCvBVdK.jpg

T1jvJCB5_j1RCvBVdK.jpg

3273 ms

hm.gif

hm.gif

252 ms

export.js

export.js

253 ms

T1CxJyBgD_1RCvBVdK.jpg

T1CxJyBgD_1RCvBVdK.jpg

920 ms

T1wKCsB7YT1RCvBVdK.jpg

T1wKCsB7YT1RCvBVdK.jpg

924 ms

T18ODCB5Kg1RCvBVdK.jpg

T18ODCB5Kg1RCvBVdK.jpg

890 ms

T1msdyBmxQ1RCvBVdK.jpg

T1msdyBmxQ1RCvBVdK.jpg

19955 ms

T1PdxCBKLQ1RCvBVdK.jpg

T1PdxCBKLQ1RCvBVdK.jpg

3111 ms

T1LOYsBsW_1RCvBVdK.jpg_300x300.jpg

T1LOYsBsW_1RCvBVdK.jpg_300x300.jpg

1133 ms

20141030200159888497.jpg

20141030200159888497.jpg

218 ms

T1kxEsB4JT1RCvBVdK.jpg_300x300.jpg

T1kxEsB4JT1RCvBVdK.jpg_300x300.jpg

911 ms

T1NdLyBjEg1RCvBVdK.jpg_300x300.jpg

T1NdLyBjEg1RCvBVdK.jpg_300x300.jpg

692 ms

T1wu_yB5Wv1RCvBVdK.jpg_300x300.jpg

T1wu_yB5Wv1RCvBVdK.jpg_300x300.jpg

967 ms

T1m6LsB4dT1RCvBVdK.jpg_300x300.jpg

T1m6LsB4dT1RCvBVdK.jpg_300x300.jpg

744 ms

T1OCYsBvdg1RCvBVdK.jpg_300x300.jpg

T1OCYsBvdg1RCvBVdK.jpg_300x300.jpg

802 ms

T10z_sB5_v1RCvBVdK.jpg_300x300.jpg

T10z_sB5_v1RCvBVdK.jpg_300x300.jpg

1421 ms

T1iXDCBsEv1RCvBVdK.jpg_300x300.jpg

T1iXDCBsEv1RCvBVdK.jpg_300x300.jpg

1696 ms

T1zixyBmZv1RCvBVdK.jpg_300x300.jpg

T1zixyBmZv1RCvBVdK.jpg_300x300.jpg

1736 ms

20150512142145441997.jpg

20150512142145441997.jpg

750 ms

20140919180053764444.jpg

20140919180053764444.jpg

485 ms

20150707184128317491.jpg

20150707184128317491.jpg

495 ms

T1nvhCBjWb1RCvBVdK.jpg

T1nvhCBjWb1RCvBVdK.jpg

579 ms

T1tGDCBvJb1RCvBVdK.jpg

T1tGDCBvJb1RCvBVdK.jpg

576 ms

T15PCCB7Vg1RCvBVdK.jpg

T15PCCB7Vg1RCvBVdK.jpg

2043 ms

T1aGYCB_Cj1RCvBVdK.jpg

T1aGYCB_Cj1RCvBVdK.jpg

1093 ms

SEO Factors

fanxing.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanxing.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 Fanxing.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

fanxing.com

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