93.8 sec in total
6.3 sec
85.8 sec
1.7 sec
Visit 366ec.cn now to see the best up-to-date 366 Ec content for China and also check out these interesting facts you probably never knew about 366ec.cn
销售不败是一款移动OA-CRM管理工具,可实现企业“客户、业绩、协同”的移动化管理。产品聚焦企业日常12项管理流程,通过移动互联技术,简化管理流程,让企业管理 “简洁、及时、有趣、可沉淀”。
Visit 366ec.cnWe analyzed 366ec.cn page load time and found that the first response time was 6.3 sec and then it took 87.5 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 49 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
366ec.cn performance score
6319 ms
3454 ms
2234 ms
19661 ms
5957 ms
Our browser made a total of 184 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 366ec.cn, 58% (107 requests) were made to 366ec.com and 7% (12 requests) were made to Qiao.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source 366ec.com.
Page size can be reduced by 696.4 kB (53%)
1.3 MB
607.5 kB
In fact, the total size of 366ec.cn main page is 1.3 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. 45% of websites need less resources to load. Javascripts take 565.4 kB which makes up the majority of the site volume.
Potential reduce by 47.4 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 47.4 kB or 73% of the original size.
Potential reduce by 172.8 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, 366 Ec needs image optimization as it can save up to 172.8 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 383.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 383.6 kB or 68% of the original size.
Potential reduce by 92.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. 366ec.cn needs all CSS files to be minified and compressed as it can save up to 92.7 kB or 81% of the original size.
Number of requests can be reduced by 56 (43%)
131
75
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 366 Ec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
366ec.cn
6319 ms
www.366ec.com
3454 ms
basic.css
2234 ms
index.css
19661 ms
Dialog.css
5957 ms
ECF.js
5995 ms
ECF.TEngine.js
4320 ms
Public.js
7471 ms
ECF.Dialog.js
8550 ms
ECF.Page.js
5200 ms
ECF.Forms.js
8973 ms
jquery.min.js
16050 ms
index.js
7209 ms
site.js
7719 ms
index.css
20251 ms
Layer.js
7725 ms
ECF.TEngine.js
9354 ms
wpa.php
869 ms
Location.axd
7405 ms
labelLimit.js
8512 ms
mvl.js
19877 ms
logo.png
1939 ms
wechat_code.PNG
2279 ms
%E5%AE%B6%E5%B1%85%E7%94%B5%E5%95%86%E4%B8%93%E9%A2%98banner.png
19854 ms
ban-%E5%A4%9A%E5%95%86%E6%88%B7%E5%85%A5%E9%A9%BB%E5%95%86%E5%9F%8E03.png
13546 ms
B2B%20O2O%20%E6%96%B0%20banner%202.png
19854 ms
B2B%20O2O%20%E6%96%B0%20banner.png
19856 ms
%E9%94%80%E5%94%AE%E4%B8%8D%E8%B4%A5%20BANNER.png
17145 ms
p24.png
11575 ms
p26.png
19849 ms
p28.png
19849 ms
p30.png
19850 ms
p27.png
19850 ms
p29.png
19851 ms
p29_1.png
19852 ms
p25.png
19851 ms
p29_2.png
19852 ms
p29_3.png
19852 ms
p29_4.png
19853 ms
p29_5.png
19854 ms
p29_6.png
19854 ms
p29_7.png
19855 ms
p32.png
19855 ms
p38.png
19856 ms
p37.png
19857 ms
1.png
19857 ms
2.png
19858 ms
3.png
19857 ms
4.png
19854 ms
5.png
19855 ms
6.png
19856 ms
7.png
19856 ms
8.png
19856 ms
9.png
19850 ms
10.png
19850 ms
11.png
19850 ms
index.php
7691 ms
12.png
19953 ms
h.js
608 ms
21.gif
1195 ms
lxb.js
2556 ms
b.js
847 ms
hm.gif
271 ms
api.js
1360 ms
Panel.js
2823 ms
localStorage.js
2373 ms
13.png
19916 ms
14.png
19577 ms
bsl.js
2707 ms
bpa.js
1851 ms
lxb.gif
531 ms
log.gif
246 ms
_l.js
287 ms
log.gif
271 ms
contains.js
586 ms
weiboShow.css
802 ms
skin02.css
802 ms
gaea_1_19.js
785 ms
bpaId
881 ms
r.cgi
1131 ms
crmqq.php
15927 ms
wpa_first_heart_beat.php
3575 ms
Enter.php
2364 ms
main_icon_invite_mess_api.js
4847 ms
main.css
788 ms
fix.css
681 ms
version.js
714 ms
0
918 ms
806fe8c4jw1f2p9ksvucdj203c01qjr5.jpg
210 ms
806fe8c4jw1f210g6522xj20c81lxdtl.jpg
310 ms
806fe8c4jw1f1fz8xzs1xj20c815njz6.jpg
345 ms
806fe8c4jw1f1bdmoxlr2j20d007t0ua.jpg
272 ms
icon_user.png
137 ms
btns_bg.png
135 ms
icon_follow.png
139 ms
593793e5gw1f14h5q9m8vj20g40augn2.jpg
51 ms
806fe8c4jw1f0e4m9ekucj20c81ly10s.jpg
1315 ms
806fe8c4jw1f115p44hh3j20c826lwy5.jpg
44 ms
806fe8c4jw1f060idiezkj20c82zg17o.jpg
1240 ms
806fe8c4jw1ezvc9qqekvj20ci07it8y.jpg
102 ms
806fe8c4jw1ezop1gzoh6j209z05zt9a.jpg
107 ms
suda.js
98 ms
806fe8c4jw1ez2hkf7yzqj209a07q748.jpg
78 ms
806fe8c4jw1ezaimgmu5fj20dw08c3zf.jpg
80 ms
806fe8c4jw1ez71le542cj20du08b3zv.jpg
767 ms
806fe8c4jw1ez19drwvn3j20d709ymxe.jpg
762 ms
show.js
21 ms
bg_trans.png
28 ms
icon_tips.png
9 ms
tmp.gif
1413 ms
01.jpg
3338 ms
m-webim-lite.css
336 ms
m-webim-lite.js
1931 ms
Refresh.php
278 ms
stat.gif
662 ms
mess-text.png
665 ms
messbtn.png
676 ms
mess.gif
804 ms
btn.png
2588 ms
15.png
9639 ms
1.png
8611 ms
Refresh.php
560 ms
2.png
10190 ms
3.png
9925 ms
4.png
10528 ms
5.png
4486 ms
6.png
7947 ms
7.png
7768 ms
8.png
14065 ms
9.png
8678 ms
10.png
10298 ms
11.png
13538 ms
12.png
19989 ms
13.png
10839 ms
14.png
11103 ms
15.png
14118 ms
1.png
13056 ms
2.png
12636 ms
3.png
16607 ms
4.png
18928 ms
5.png
17434 ms
6.png
14593 ms
7.png
19979 ms
8.png
15126 ms
9.png
16742 ms
10.png
18875 ms
11.png
17842 ms
12.png
19893 ms
13.png
18381 ms
14.png
18915 ms
15.png
19974 ms
1.png
19973 ms
2.png
19842 ms
3.png
20004 ms
Refresh.php
270 ms
4.png
19631 ms
5.png
20000 ms
6.png
19998 ms
7.png
19696 ms
8.png
19506 ms
Refresh.php
263 ms
9.png
19015 ms
10.png
16902 ms
11.png
19217 ms
hb.crm2.qq.com
558 ms
12.png
16596 ms
13.png
17351 ms
14.png
15406 ms
15.png
20290 ms
cooper.png
20159 ms
copyright.png
19893 ms
Refresh.php
304 ms
ico_index_01.png
17271 ms
ico_index_02.png
15155 ms
hb.crm2.qq.com
540 ms
ico_index_03.png
16539 ms
Refresh.php
269 ms
hb.crm2.qq.com
19707 ms
Refresh.php
286 ms
hb.crm2.qq.com
1569 ms
Refresh.php
281 ms
hb.crm2.qq.com
571 ms
Refresh.php
313 ms
hb.crm2.qq.com
574 ms
366ec.cn SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 366ec.cn 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 366ec.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.
366ec.cn
Open Graph description is not detected on the main page of 366 Ec. 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: