41.2 sec in total
10.4 sec
30.3 sec
585 ms
Visit dayoo.com now to see the best up-to-date Dayoo content for China and also check out these interesting facts you probably never knew about dayoo.com
广州日报大洋网是立足广州、辐射华南的综合性区域门户网站,为用户提供新闻、生活、论坛等20多个频道。广州日报大洋网是广州日报新媒体发展的先锋,在区域资讯服务、媒体融合发展方面已经获得显著成果。广州日报大洋网是新闻资讯服务的南大门。
Visit dayoo.comWe analyzed Dayoo.com page load time and found that the first response time was 10.4 sec and then it took 30.9 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
dayoo.com performance score
10359 ms
637 ms
6357 ms
2953 ms
717 ms
Our browser made a total of 172 requests to load all elements on the main page. We found that 8% of them (14 requests) were addressed to the original Dayoo.com, 41% (71 requests) were made to Img1.dayoo.com and 7% (12 requests) were made to Asearch.alicdn.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Beian.gov.cn.
Page size can be reduced by 1.8 MB (39%)
4.7 MB
2.9 MB
In fact, the total size of Dayoo.com main page is 4.7 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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 124.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. 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 124.3 kB or 78% of the original size.
Potential reduce by 168.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. Dayoo images are well optimized though.
Potential reduce by 642.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 642.5 kB or 70% of the original size.
Potential reduce by 899.1 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. Dayoo.com needs all CSS files to be minified and compressed as it can save up to 899.1 kB or 87% of the original size.
Number of requests can be reduced by 44 (27%)
164
120
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dayoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
dayoo.com
10359 ms
style.css
637 ms
captcha
6357 ms
2016040502.jpg
2953 ms
index.php
717 ms
dy-qr.png
555 ms
gbhqr.jpg
650 ms
logo_2.png
587 ms
blank
17 ms
other-login-icon.png
781 ms
icons.png
81 ms
mobile.css
1766 ms
jquery-1.8.2.min.js
1892 ms
1460001227383.jpg
675 ms
6c0b8441b1cb1871a0d43c.jpg
152 ms
1460001263695.jpg
675 ms
6c0b8441b1cb18715ad81c.jpg
287 ms
6c0b8441b3db1871315f12.jpg
178 ms
6c0b8441b3771871c6ed37.jpg
179 ms
6c0b8441b1cb1871416a4e.jpg
358 ms
6c0b8441b1cb18714a8455.jpg
358 ms
6c0b84455e65185490ba04.jpg
158 ms
6c0b84455dde18475a8202.jpg
89 ms
4439c4329fc318408bf704.jpg
88 ms
0250f2000002183a283e1a.jpg
234 ms
0250f2000002183a289a1c.jpg
229 ms
0250f20000021839064804.jpg
91 ms
6c0b84455da2187132c907.jpg
72 ms
6c0b84455da2187131d402.jpg
76 ms
6c0b8441b1ae186f021d07.jpg
244 ms
6c0b8441b1df185d91be01.jpg
240 ms
6c0b84455dbb1871413f05.jpg
166 ms
6c0b84455dbb1871390202.jpg
167 ms
0250f200000218686b221f.jpg
233 ms
6c0b8441b18a18584cf731.jpg
308 ms
6c0b8444dc42187152e204.jpg
237 ms
6c0b8444dc421871524b02.jpg
241 ms
0250f2000002187044f521.jpg
312 ms
6c0b8441b1941811457628.jpg
316 ms
0250f2000002186fff3620.jpg
382 ms
6c0b8441b1941859910007.jpg
381 ms
b0.png
1627 ms
6c0b84455da21871396d2c.jpg
72 ms
xixi.png
78 ms
listicon2.png
137 ms
6c0b84455da21871402d52.jpg
231 ms
6c0b84455d30187167d42f.jpg
232 ms
6c0b8444dc861853121101.jpg
132 ms
6c0b8444dc861812d5bc0f.jpg
134 ms
6c0b8444dca717d0ebdf0b.jpg
136 ms
6c0b84455e4617d0c4dc04.jpg
224 ms
6c0b84455da21871450763.jpg
297 ms
6c0b84455dc218704ded32.jpg
302 ms
6c0b84454e471871b12852.jpg
303 ms
6c0b840c4aae18703f3501.jpg
71 ms
adsbygoogle.js
12 ms
6c0b840c4aae18703f5002.jpg
76 ms
6c0b840c4aae18703f6503.jpg
70 ms
6c0b8444dc8c17eb2cc01d.jpg
142 ms
6c0b840c4aae18703fad04.jpg
74 ms
6c0b840c4aae18703fc705.jpg
72 ms
6c0b840c4aae187041ba06.jpg
140 ms
6c0b840c4aae187041f108.jpg
138 ms
6c0b840c4aae1870420709.jpg
145 ms
6c0b840c4aae1870426b0c.jpg
146 ms
6c0b840c4aae1870424d0b.jpg
147 ms
6c0b8444dc8c17eb68b826.jpg
281 ms
6c0b840c4aae187042220a.jpg
209 ms
6c0b84455dc21871533a04.jpg
282 ms
6c0b84455dc21862ecd527.jpg
284 ms
6c0b84455d2f186818b102.jpg
281 ms
6c0b84455d2f186822c210.jpg
150 ms
6c0b84454e4718700cc707.jpg
144 ms
6c0b84453e79180296f235.jpg
144 ms
6c0b84455dc2184b162403.jpg
255 ms
6c0b84455e4718682fcb04.jpg
80 ms
6c0b84455dc21871b4eb45.jpg
147 ms
ex
961 ms
tanxssp.js
330 ms
ex
869 ms
6c0b84455e47186eca2e1c.jpg
159 ms
union.js
2020 ms
6c0b84455dd5185af56d07.jpg
73 ms
6c0b84455daa18642f8103.jpg
74 ms
ca-pub-2065709201317913.js
48 ms
zrt_lookup.html
41 ms
show_ads_impl.js
71 ms
ads
225 ms
osd.js
3 ms
1808930523549773180
32 ms
abg.js
34 ms
m_js_controller.js
49 ms
googlelogo_color_112x36dp.png
29 ms
gzrb.png
382 ms
gbh.jpg
1489 ms
s
26 ms
x_button_blue2.png
44 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
3 ms
acbeacon2.html
111 ms
spf
930 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
55 ms
TB1bcNDFVXXXXaLXVXXO04pFXXX.html
112 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
53 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
53 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
55 ms
t.gif
1968 ms
tns.simba.taobao.com
775 ms
dysqqr.png
451 ms
gzck.png
2288 ms
gzrbwbz.png
803 ms
pyrbwbz.png
2670 ms
dysq.png
1091 ms
sjdy.png
1191 ms
tqyb.png
3123 ms
jw.png
1502 ms
home_b_1.gif
71 ms
logo_down.jpg
19688 ms
TB2KYVmmpXXXXaTXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
539 ms
T1.zirFt8dXXan4E_j-58-24.png
197 ms
T1jStWFuVeXXb1upjX.jpg
33 ms
tanxclick.js
34 ms
feature.htm
1036 ms
TB2JmyUmpXXXXbrXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
530 ms
TB2yQNtmXXXXXcwXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
530 ms
TB2fLbJlVXXXXcuXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
532 ms
TB2V9somXXXXXXGXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
532 ms
TB2_LqqiFXXXXaaXpXXXXXXXXXX_!!111698406-0-saturn_solar.jpg_110x90.jpg
531 ms
TB1tdr3MXXXXXXLapXXYXGcGpXX_M2.SS2_sum.jpg_110x90.jpg
774 ms
TB2RlPKlVXXXXcHXXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
546 ms
TB2NxY6mpXXXXXvXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
545 ms
TB2BrFSjVXXXXcHXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
545 ms
TB2FFsrlFXXXXcxXpXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
545 ms
TB2meXomXXXXXX3XXXXXXXXXXXX_!!0-saturn_solar.jpg_110x90.jpg
546 ms
jbzq_img_1.gif
96 ms
seallogo.dll
569 ms
beianbgs.png
20315 ms
colse.png
94 ms
jquery-1.7.2.min.js
1906 ms
dayoo.js
93 ms
slick.1.3.15.min.js
95 ms
dy.login.min.js
3478 ms
lib.js
3420 ms
jquery.cookie.js
99 ms
pre
758 ms
cnnic_en.png
3308 ms
h.js
912 ms
activity
745 ms
app.gif
884 ms
atrk.js
70 ms
ga.js
15 ms
da.js
5706 ms
hm.gif
471 ms
__utm.gif
20 ms
atrk.gif
60 ms
test.png
383 ms
page.css
724 ms
jquery.min.js
3713 ms
common.js
1826 ms
um.js
528 ms
img
1034 ms
um.json
2099 ms
getDeviceInfo
1069 ms
getDeviceInfo
1442 ms
search-logo.png
3103 ms
mark.png
778 ms
1459912364117.jpg
251 ms
webdig.js
602 ms
sta.gif
353 ms
checkTicket
469 ms
r-0af570429f30df4914601186324550.24006214831024408
578 ms
1.gif
577 ms
search-logo.png
4256 ms
dayoo.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dayoo.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 Dayoo.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.
dayoo.com
Open Graph description is not detected on the main page of Dayoo. 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: