29.2 sec in total
1.6 sec
26.4 sec
1.3 sec
Visit duowan.com now to see the best up-to-date Duowan content for China and also check out these interesting facts you probably never knew about duowan.com
Visit duowan.comWe analyzed Duowan.com page load time and found that the first response time was 1.6 sec and then it took 27.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
duowan.com performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value60.7 s
0/100
25%
Value14.2 s
1/100
10%
Value2,520 ms
4/100
30%
Value0.752
6/100
15%
Value6.6 s
57/100
10%
1557 ms
3335 ms
1914 ms
4072 ms
1193 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Duowan.com, 21% (35 requests) were made to Assets.dwstatic.com and 12% (20 requests) were made to Gt.yy.com. The less responsive or slowest element that took the longest time to load (6.7 sec) relates to the external source Stat.game.yy.com.
Page size can be reduced by 1.2 MB (28%)
4.1 MB
3.0 MB
In fact, the total size of Duowan.com main page is 4.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. 60% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 281.3 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 38.7 kB, which is 12% 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 281.3 kB or 87% of the original size.
Potential reduce by 227.0 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. Duowan images are well optimized though.
Potential reduce by 195.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 195.4 kB or 69% of the original size.
Potential reduce by 457.7 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. Duowan.com needs all CSS files to be minified and compressed as it can save up to 457.7 kB or 84% of the original size.
Number of requests can be reduced by 79 (53%)
150
71
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duowan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and as a result speed up the page load time.
duowan.com
1557 ms
www.duowan.com
3335 ms
yy-f2e-header-duowan.min
1914 ms
global.css
4072 ms
g
1193 ms
g
1206 ms
g
1248 ms
g
1209 ms
g
1207 ms
g
1325 ms
g
1490 ms
g
2584 ms
g
1523 ms
g
1534 ms
g
1578 ms
g
1796 ms
g
1831 ms
g
1879 ms
g
4256 ms
g
1934 ms
g
2287 ms
entry.js
3936 ms
main.js
3938 ms
g
2326 ms
adstat.1.0.0.js
1264 ms
duowanFooter.js
94 ms
1460111872629.jpg
3707 ms
1460080801587.jpg
1013 ms
1460078567803.jpg
1126 ms
1460082718734.jpg
1230 ms
1460084218009.jpg
928 ms
1460083783553.jpg
1929 ms
201604071428009438.jpeg
1169 ms
201604061403345478.jpeg
1131 ms
201604081154068996.jpeg
1173 ms
1460115549955.jpg
956 ms
1459908780785.jpg
1018 ms
1456986547719.jpg
962 ms
1460082482977.jpg
860 ms
1459840439621.jpg
1026 ms
1460080317233.jpg
855 ms
1459995947940.jpg
858 ms
1460084377770.jpg
856 ms
1460022474391.jpg
917 ms
1459994624519.jpg
3688 ms
1460082264291.jpg
3689 ms
1460025187911.jpg
3805 ms
1460084481120.jpg
3685 ms
1460082939149.jpg
3686 ms
1460082535738.png
3898 ms
1460080881836.jpg
3822 ms
1460106257698.jpg
3766 ms
1460082243724.jpg
1041 ms
1460022559345.jpg
1042 ms
1460010948468.jpeg
1042 ms
global.png
120 ms
blank.png
96 ms
1459495925860.jpg
1330 ms
1459400769472.jpg
1208 ms
1459931421007.jpeg
1249 ms
1460096486033.jpg
1817 ms
1456986563458.jpg
1822 ms
1459503351273_1223512015.jpg
4854 ms
bg_loading.gif
50 ms
bg_wonderful.png
56 ms
1460081542092_1000504976.jpg
4665 ms
1458207909521_2007378499.jpg
4655 ms
bg_week.png
45 ms
bg_line.png
55 ms
1459414625209_1742719071.jpg
4865 ms
1460082013183_1402052940.jpg
4609 ms
1460081570724_298817210.jpg
4345 ms
1460081595448_1607863019.jpg
4855 ms
1459414040951_1036100499.jpg
4793 ms
1459414165629_478998674.jpg
5024 ms
1458208280539_1036100499.jpg
5041 ms
1458208310768_478998674.jpg
4918 ms
1456121794449_298817210.jpg
5021 ms
1456121814726_1607863019.jpg
5022 ms
1460081746877_515623657.jpg
5314 ms
1459414699294_1739024987.jpg
5300 ms
seajs-style.js&nm&20150507
52 ms
duowan.js
45 ms
market_count.js
91 ms
statistics.js
90 ms
footer-sprite.png
53 ms
jquery.js&nm&20150507
131 ms
main.js
49 ms
j.gif
2641 ms
statistics&f=stat-default.js,detector.js,webuseroper.js,stat-area-0.js&nm&20150507
48 ms
jquery.min.js
45 ms
main.js
64 ms
main.js
173 ms
h.js
2405 ms
dwtv&f=flash2video.js,ua.js,mp4.js&nm&20150529
110 ms
dwudbproxy.js&nm&20150507
91 ms
jquery.lazyload.min.js&nm&20150507
90 ms
dwpod.js&nm&20150507
92 ms
jquery.placeholder.min.js&nm&20150507
90 ms
carousel.js&nm&20150507
91 ms
tabs.js&nm&20150507
91 ms
cookie.js&nm&20150507
114 ms
cache.php
913 ms
moment.min.js
123 ms
popbox.js
101 ms
getActGotNumber
1060 ms
getActGotNumber
1045 ms
getActGotNumber
1047 ms
getActGotNumber
1047 ms
getActGotNumber
1244 ms
getActGotNumber
3672 ms
index.php
1382 ms
tip.js&nm&20150507
55 ms
main.js
54 ms
udb.sdk.pcweb.popup.min.js
2290 ms
mustache.js&nm&20150507
158 ms
easing.js&nm&20150507
46 ms
index.php
6184 ms
tip.css&nm&20150507.css
79 ms
cstorage.js&nm&20150507
116 ms
filter.js&nm&20150507
115 ms
home_recommend_live_web_1459424726.jpg
4781 ms
home_recommend_live_web_1456480290.jpg
4710 ms
20dbba14dc34b8610ffa9ce24cda238e5302.jpg
878 ms
53927f453d4ec13692c9845268caf0d4310.jpg
790 ms
9d55920a1b5ce3e73a40407241c313d2474.jpg
829 ms
bc440a5b6d90e5a8f7b6ad80e2bbff727766.jpg
877 ms
yy-f2e-duowan.min
57 ms
gdc_duowan
1136 ms
hm.gif
492 ms
data.do
6737 ms
ad.png
340 ms
g
684 ms
tips.duowan.com
1310 ms
xqlogin.sdk.css
410 ms
data.do
5720 ms
data.do
6059 ms
t.gif
1173 ms
1ae4aefd72d419e03e6048859ad70f2f6298.jpg
51 ms
cstorage-proxy.html
47 ms
301a31df05ed58dfb797cf16dd0220131503.jpg
51 ms
c.gif
525 ms
cm.gif
4677 ms
s
1970 ms
t.gif
914 ms
tanx
347 ms
bj_1.jpg
1496 ms
ya.1.3.2-min.js
53 ms
c.gif
477 ms
bj_3.jpg
1523 ms
bj_2.jpg
1578 ms
s
5199 ms
data.do
490 ms
data.do
384 ms
data.do
406 ms
data.do
727 ms
data.do
1689 ms
data.do
775 ms
data.do
784 ms
data.do
899 ms
data.do
913 ms
data.do
1082 ms
data.do
1152 ms
data.do
1188 ms
data.do
1385 ms
data.do
1364 ms
data.do
1436 ms
data.do
2679 ms
hm.gif
463 ms
duowan.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
duowan.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
duowan.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duowan.com 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 Duowan.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.
duowan.com
Open Graph description is not detected on the main page of Duowan. 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: