18.5 sec in total
3.7 sec
14.5 sec
375 ms
Welcome to dahei.com homepage info - get ready to check Dahei best content for United States right away, or after learning these important things about dahei.com
Visit dahei.comWe analyzed Dahei.com page load time and found that the first response time was 3.7 sec and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dahei.com performance score
3699 ms
1700 ms
18 ms
29 ms
19 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 89% of them (91 requests) were addressed to the original Dahei.com, 2% (2 requests) were made to Static.anquan.org and 2% (2 requests) were made to Oz.cnzz.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Dahei.com.
Page size can be reduced by 291.2 kB (66%)
441.3 kB
150.1 kB
In fact, the total size of Dahei.com main page is 441.3 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. 45% of websites need less resources to load. Javascripts take 310.9 kB which makes up the majority of the site volume.
Potential reduce by 19.0 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 19.0 kB or 77% of the original size.
Potential reduce by 8.6 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. Obviously, Dahei needs image optimization as it can save up to 8.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 222.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 222.5 kB or 72% of the original size.
Potential reduce by 41.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. Dahei.com needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 80% of the original size.
Number of requests can be reduced by 15 (15%)
98
83
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dahei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
dahei.com
3699 ms
www.dahei.com
1700 ms
global.css
18 ms
layout.css
29 ms
tan.css
19 ms
home.css
39 ms
jquery.js
26 ms
jquery.xdomainajax.js
25 ms
Dahei.Devel.js
26 ms
Dahei.Common.js
34 ms
md5.js
34 ms
syspop.js
34 ms
stat.js
186 ms
marquee.js
13 ms
welcome_music.js
519 ms
z_stat.php
1400 ms
aq_auth.js
1681 ms
repeat.jpg
72 ms
mainB.png
23 ms
wrapBg.png
67 ms
blank.gif
20 ms
putDesk.png
661 ms
logo.jpg
68 ms
navBg.png
69 ms
navOn.png
73 ms
daheiyouxi.jpg
679 ms
mianM.png
426 ms
ucBg.jpg
429 ms
line.png
114 ms
ucInput.jpg
431 ms
logOff.png
445 ms
checkBg.gif
681 ms
logBtnIco.png
446 ms
loRegBg.jpg
453 ms
gameGuide.gif
729 ms
ico.gif
455 ms
1-1851-150jyjx.jpg
2148 ms
1-1468-1029ws.jpg
1494 ms
newsBg.png
1878 ms
line0122.gif
1824 ms
point0122.gif
1211 ms
serstate1.gif
741 ms
newSer0218.jpg
752 ms
boxBg.gif
2711 ms
ts_logo.png
1495 ms
ts_ico.jpg
1512 ms
spanLine.gif
2259 ms
ws_logo.png
2145 ms
ws_ico.jpg
2144 ms
jyjx_logo.png
2712 ms
jyjx_ico.jpg
2156 ms
tqsg_logo.png
2154 ms
tqsg_ico.jpg
2144 ms
zhtx_logo.png
2446 ms
zhtx_ico.jpg
2197 ms
btn.jpg
2120 ms
ts_ico.png
2201 ms
ws_ico.png
2561 ms
jyjx_ico.png
2205 ms
tqsg_ico.png
2692 ms
zhtx_ico.png
2644 ms
ajer_ico.png
2082 ms
ajer_logo.png
3673 ms
lunhui_ico.png
2576 ms
lunhui_logo.png
2289 ms
mhj_ico.png
3838 ms
mhj_logo.png
2295 ms
ts_gift(1).jpg
2302 ms
jyjx_gift.jpg
2383 ms
ws_gift.jpg
2401 ms
index_diamond.jpg
3023 ms
line2.gif
3497 ms
btn0122.gif
3395 ms
our.jpg
5496 ms
footLogo.png
2558 ms
stat.htm
187 ms
core.php
967 ms
authentication.png
2568 ms
loading.gif
2956 ms
9.gif
810 ms
stat.htm
187 ms
blank.htm
2120 ms
2152 ms
1789 ms
9.gif
713 ms
backTop.gif
1888 ms
csFloat.gif
1919 ms
csClose.gif
1931 ms
ws_ico2.jpg
3159 ms
ajer_ico2.jpg
4286 ms
ts_ico2.jpg
2580 ms
dotted.gif
2390 ms
zhtx_ico2.jpg
2420 ms
sgxm_ico2.jpg
2697 ms
jyjx_ico2.jpg
2730 ms
subOn.png
2588 ms
subOff.png
2866 ms
app.gif
4783 ms
app.gif
969 ms
sm_83x30_gray.png
4831 ms
1-1851-150jyjxc.jpg
1082 ms
corner_bg.gif
1179 ms
dahei.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 Dahei.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 Dahei.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.
dahei.com
Open Graph description is not detected on the main page of Dahei. 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: