111.9 sec in total
6 sec
105.1 sec
731 ms
Click here to check amazing Duotoo content. Otherwise, check out these important facts you probably never knew about duotoo.com
Visit duotoo.comWe analyzed Duotoo.com page load time and found that the first response time was 6 sec and then it took 105.8 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 were 99 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
duotoo.com performance score
6025 ms
19457 ms
879 ms
6423 ms
4313 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 12% of them (19 requests) were addressed to the original Duotoo.com, 67% (110 requests) were made to Tu.duotoo.com and 4% (7 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Duotoo.com.
Page size can be reduced by 377.0 kB (62%)
611.0 kB
234.0 kB
In fact, the total size of Duotoo.com main page is 611.0 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. 35% of websites need less resources to load. Javascripts take 453.7 kB which makes up the majority of the site volume.
Potential reduce by 84.6 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 84.6 kB or 83% of the original size.
Potential reduce by 3.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. Duotoo images are well optimized though.
Potential reduce by 279.8 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 279.8 kB or 62% of the original size.
Potential reduce by 9.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. Duotoo.com needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 75% of the original size.
Number of requests can be reduced by 26 (46%)
57
31
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duotoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
duotoo.com
6025 ms
www.duotoo.com
19457 ms
tj.js
879 ms
global.css
6423 ms
index.css
4313 ms
jq.js
20432 ms
jquery.lazyload.js
1106 ms
hd.js
438 ms
duotooPC.js
3981 ms
exnbs0sp4fn.jpg
20015 ms
BodyBg.png
524 ms
close.png
3172 ms
loading.gif
3460 ms
prev.png
2188 ms
next.png
3591 ms
minHeadBg.png
2366 ms
logo.png
5807 ms
1-16040322362HF.jpg
10987 ms
lfo20aexpfy.jpg
17096 ms
yrpthng1e45.jpg
20010 ms
hey51aemc0d.jpg
20010 ms
v2tjlu4e3bs.jpg
20011 ms
mnzp.jpg
20011 ms
omny.jpg
20012 ms
nzkmn.jpg
20013 ms
hsmn.jpg
20012 ms
gzmn.jpg
20014 ms
zfmn.jpg
20015 ms
qpmn.jpg
20018 ms
jpmt1.jpg
20016 ms
jpsw.jpg
20017 ms
pd53hnfiyyp.jpg
20017 ms
1425629551_umvoHJRS.jpg
20019 ms
p2soqnt24v3.jpg
20022 ms
rq5nb5ug01q.jpg
20022 ms
pxes022snqu.jpg
20024 ms
1426645808_yaqdNbDk.jpg
20025 ms
v5hb1s21nr1.jpg
20026 ms
cia2suvwhcw.jpg
20027 ms
1426834264_aqwZmeBG.jpg
20028 ms
kcg15yvreeg.jpg
20028 ms
25lvfv0c3an.jpg
20030 ms
latqkvaqyjv.jpg
20030 ms
1pjzfysfomb.jpg
20031 ms
ye2irv3l005.jpg
20032 ms
yd1vbfj2vui.jpg
20034 ms
in4tre5r5h1.jpg
20035 ms
zfa42ciktbx.jpg
20035 ms
v21j00qlte3.jpg
20036 ms
qwjrdt3daax.jpg
20037 ms
f5qlhgukjk0.jpg
19987 ms
l5mndgsmrij.jpg
19988 ms
jqoggd5stqx.jpg
19989 ms
c.js
1070 ms
jczm
1002 ms
js
1666 ms
navLink.png
1650 ms
yuan.png
2234 ms
stat.php
4993 ms
f.js
1834 ms
hm.js
548 ms
push.js
480 ms
i.js
826 ms
hm.gif
326 ms
jczm
1978 ms
adx.php
1014 ms
reduce_bd-logo1_oper.png
495 ms
ping
541 ms
closefeedback.min.js
811 ms
reduce_promotion_oper.png
617 ms
bd_logo.png
615 ms
bg_rb.png
626 ms
stat.htm
173 ms
core.php
777 ms
9.gif
1942 ms
ls.js
279 ms
ui
739 ms
ls_flowbar.js
261 ms
home
922 ms
jquery_a4373ccd.js
526 ms
arrow_left_60_e700a3bb.png
340 ms
app.gif
2102 ms
arrow_left_50_1dfda915.png
583 ms
j1jkwzeb5v0.jpg
17133 ms
ipwrn0gqlen.jpg
12467 ms
0me2rslp2vk.jpg
9815 ms
wadzum3n2wl.jpg
5180 ms
i5wv3xqkhiy.jpg
8847 ms
3obesphibrf.jpg
8613 ms
vpoufdjzakj.jpg
15199 ms
ljs4y2imwih.jpg
14832 ms
xygleorfjr3.jpg
19992 ms
szskqifadjh.jpg
19993 ms
rhbnnfgohsb.jpg
19989 ms
fumb3gwkqsh.jpg
19988 ms
pmifuooyauq.jpg
19989 ms
4o2ekcwt1z2.jpg
19989 ms
htan5h5tgcf.jpg
19989 ms
SWR4759M.jpg
19986 ms
b2hfkkpaah0.jpg
19987 ms
xeynf4toqwc.jpg
19987 ms
oi0gyjpsse1.jpg
19986 ms
onorh4ywt5w.jpg
19987 ms
vdqm3xhb4aq.jpg
19988 ms
pydnobmfcsg.jpg
19987 ms
jduhor2l5zt.jpg
19987 ms
nwdcyff5tzr.jpg
19988 ms
mgjwbqyskh1.jpg
19988 ms
nwkh5243ep0.jpg
19988 ms
qdcor2pbrkq.jpg
19985 ms
2012041715230475324.jpg
19986 ms
2015013014023366003.png
19986 ms
2015020309195142780.jpg
19986 ms
2012042314470719022.jpg
19987 ms
14020338752577741.jpg
19987 ms
20129923231059489877.jpg
19987 ms
2012071910351843836.jpg
19987 ms
0cnvybgdyaf.jpg
19986 ms
2015020509152092843.jpg
19982 ms
2015020611451881174.png
19816 ms
aj2sv3nxhqk.jpg
20380 ms
2012092813523325811.jpg
19763 ms
2014072814222484982.jpg
20181 ms
2015022309343195169.jpg
19532 ms
suohrm2uy5d.jpg
15341 ms
14112513416767.jpg
20160 ms
14112015138969.jpg
18394 ms
14121214423483.jpg
19997 ms
14120113495474.jpg
19997 ms
14121114275388.jpg
19996 ms
14122213588619.jpg
19996 ms
14122313169911.jpg
19995 ms
14122516076909.jpg
19994 ms
14122313194124.jpg
19994 ms
14122813311880.jpg
19994 ms
14122516229138.jpg
19993 ms
15011310339079.jpg
19995 ms
14122813394370.jpg
19994 ms
14033011324434.jpg
19994 ms
15020814569552.jpg
19993 ms
15012413456976.jpg
19995 ms
17-141226111A8.jpg
20008 ms
fwltlmxpyaz.jpg
20007 ms
bc4d2bgkfbr.jpg
20007 ms
12-1412311H017.jpg
20007 ms
12-15012QH336.jpg
20006 ms
17-150204104334.jpg
20005 ms
12-1409261G340.jpg
20005 ms
zif5opnvjdq.jpg
20007 ms
17-141010155414.jpg
20006 ms
ftqmq1gz4lp.jpg
20005 ms
12-14100P93951.jpg
20006 ms
dxy04pgdnbj.jpg
20007 ms
17-150203113204.jpg
20006 ms
12-150209104526.jpg
20000 ms
12-150303150146.jpg
19998 ms
12-15022G64122.jpg
20382 ms
o.htm
724 ms
hm.gif
1137 ms
wh.js
1340 ms
ac.js
1101 ms
fp.htm
1865 ms
fp.htm
1132 ms
duotoo.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duotoo.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 Duotoo.com main page’s claimed encoding is gb2312. 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.
duotoo.com
Open Graph description is not detected on the main page of Duotoo. 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: