Tools & Wizards About Us
player.kuwo.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

player.kuwo.cn

Page Load Speed

54.4 sec in total

First Response

11.3 sec

Resources Loaded

42.8 sec

Page Rendered

213 ms

player.kuwo.cn screenshot

About Website

Welcome to player.kuwo.cn homepage info - get ready to check Player Kuwo best content for China right away, or after learning these important things about player.kuwo.cn

酷我在线音乐播放器，百万歌曲免费在线试听，正版音乐免费下载，最新最全的歌曲搜索，歌词，试听和下载服务，即时更新的全球音乐排行榜，播放更流畅，音质更完美。

Visit player.kuwo.cn

Key Findings

We analyzed Player.kuwo.cn page load time and found that the first response time was 11.3 sec and then it took 43.1 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

player.kuwo.cn performance score

0

Network Requests Diagram

player.kuwo.cn

11317 ms

play

3536 ms

base2.css

4007 ms

loginbox2012.css

2993 ms

jquery-1.8.3.min.js

1505 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Player.kuwo.cn, 43% (32 requests) were made to Image.kuwo.cn and 16% (12 requests) were made to Topmusic.kuwo.cn. The less responsive or slowest element that took the longest time to load (19.5 sec) belongs to the original domain Player.kuwo.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.1 kB (47%)

Content Size

785.1 kB

After Optimization

414.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Player.kuwo.cn main page is 785.1 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. Images take 338.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 91.7 kB

  • Original 113.3 kB
  • After minification 101.9 kB
  • After compression 21.7 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 91.7 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 30.9 kB

  • Original 338.7 kB
  • After minification 307.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. Player Kuwo images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 195.3 kB

  • Original 265.9 kB
  • After minification 226.2 kB
  • After compression 70.6 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 195.3 kB or 73% of the original size.

CSS Optimization

-79%

Potential reduce by 53.3 kB

  • Original 67.1 kB
  • After minification 63.9 kB
  • After compression 13.9 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. Player.kuwo.cn needs all CSS files to be minified and compressed as it can save up to 53.3 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

player.kuwo.cn

player.kuwo.cn

11317 ms

play

play

3536 ms

base2.css

base2.css

4007 ms

loginbox2012.css

loginbox2012.css

2993 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1505 ms

KW_DqPlayer_v2.js

KW_DqPlayer_v2.js

1177 ms

KW_WebPlayer_v2.js

KW_WebPlayer_v2.js

833 ms

cookie.js

cookie.js

1564 ms

play1.js

play1.js

19539 ms

kwgg_372.js

kwgg_372.js

1759 ms

kwgg_212.js

kwgg_212.js

2158 ms

stat_1.js

stat_1.js

433 ms

l_bg.gif

l_bg.gif

822 ms

init.htm

init.htm

1812 ms

h5hezuo_qr.png

h5hezuo_qr.png

11334 ms

webmusic.jpg

webmusic.jpg

1381 ms

down1125.gif

down1125.gif

818 ms

head_bg.jpg

head_bg.jpg

1263 ms

logo.png

logo.png

825 ms

serach.gif

serach.gif

813 ms

sc.png

sc.png

1221 ms

home2.png

home2.png

1224 ms

loading.gif

loading.gif

1232 ms

pic50.png

pic50.png

1240 ms

pic150.jpg

pic150.jpg

1686 ms

pic50.jpg

pic50.jpg

1689 ms

search_logo.png

search_logo.png

1697 ms

all.jpg

all.jpg

1607 ms

web_player_ip.jpg

web_player_ip.jpg

1634 ms

zhaoge_summer_hz_webplayer_jiaodian.htm

zhaoge_summer_hz_webplayer_jiaodian.htm

3997 ms

btn3.png

btn3.png

1683 ms

btn20.png

btn20.png

2153 ms

btn1.png

btn1.png

4650 ms

btn4.png

btn4.png

2067 ms

bot.jpg

bot.jpg

2508 ms

jindu1.gif

jindu1.gif

2095 ms

jindu2.gif

jindu2.gif

2533 ms

scheduleBtn.png

scheduleBtn.png

2456 ms

shou.png

shou.png

2504 ms

fen.png

fen.png

2552 ms

play_share.png

play_share.png

2879 ms

mic_button.gif

mic_button.gif

2912 ms

xunhuan.png

xunhuan.png

2910 ms

prev.png

prev.png

2983 ms

play.png

play.png

2995 ms

next.png

next.png

3265 ms

sound.png

sound.png

3300 ms

soundjindu.png

soundjindu.png

3307 ms

soundhuan.png

soundhuan.png

3373 ms

index.htm

index.htm

748 ms

personalAd.js

personalAd.js

1462 ms

tuijian.png

tuijian.png

3824 ms

index.htm

index.htm

1448 ms

h.js

h.js

668 ms

shell_v2.js

shell_v2.js

2452 ms

PlayCheckIp

PlayCheckIp

2407 ms

hm.gif

hm.gif

344 ms

1460138592268x473_0.jpg

1460138592268x473_0.jpg

2844 ms

ip_domain

ip_domain

2197 ms

cookie.js

cookie.js

1677 ms

logger.js

logger.js

269 ms

bds_s_v2.js

bds_s_v2.js

1092 ms

zhaoge_summer_600.css

zhaoge_summer_600.css

794 ms

zhaoge_summer_hz_webplay.js

zhaoge_summer_hz_webplay.js

1508 ms

bdsstyle.css

bdsstyle.css

1212 ms

getnum

getnum

3676 ms

load.gif

load.gif

403 ms

1458394440777.jpg

1458394440777.jpg

1193 ms

1-1.gif

1-1.gif

2558 ms

trp.gif

trp.gif

907 ms

left_icon.png

left_icon.png

1553 ms

right_icon.png

right_icon.png

1011 ms

focusBtn.png

focusBtn.png

1303 ms

1458355829487.jpg

1458355829487.jpg

4063 ms

focusBtnH.png

focusBtnH.png

1544 ms

SEO Factors

player.kuwo.cn SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

player.kuwo.cn

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