67.6 sec in total
2.3 sec
64.7 sec
549 ms
Welcome to 366ec.com homepage info - get ready to check 366 Ec best content right away, or after learning these important things about 366ec.com
任我行科技专注于企业数字化营销及应用技术服务,为传统企业+互联网提供从轻应用、 专业级到平台级的各类专业化数字解决方案、软件系统、咨询培训与运营服务。
Visit 366ec.comWe analyzed 366ec.com page load time and found that the first response time was 2.3 sec and then it took 65.3 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 23 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
366ec.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.593
11/100
15%
Value0
0/100
10%
2307 ms
7263 ms
1436 ms
12707 ms
775 ms
Our browser made a total of 199 requests to load all elements on the main page. We found that 57% of them (114 requests) were addressed to the original 366ec.com, 6% (12 requests) were made to Qiao.baidu.com and 4% (8 requests) were made to P6.qiao.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain 366ec.com.
Page size can be reduced by 696.4 kB (53%)
1.3 MB
612.3 kB
In fact, the total size of 366ec.com 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. 50% 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.com 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 64 (38%)
168
104
The browser has sent 168 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 48 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
366ec.com
2307 ms
www.366ec.com
7263 ms
basic.css
1436 ms
index.css
12707 ms
Dialog.css
775 ms
ECF.js
9093 ms
ECF.TEngine.js
1242 ms
Public.js
2292 ms
ECF.Dialog.js
2872 ms
ECF.Page.js
2822 ms
ECF.Forms.js
2522 ms
jquery.min.js
7705 ms
index.js
3966 ms
site.js
3544 ms
index.css
14650 ms
Layer.js
3573 ms
ECF.TEngine.js
4931 ms
wpa.php
875 ms
Location.axd
2547 ms
labelLimit.js
2909 ms
mvl.js
1238 ms
logo.png
760 ms
wechat_code.PNG
5515 ms
%E5%AE%B6%E5%B1%85%E7%94%B5%E5%95%86%E4%B8%93%E9%A2%98banner.png
16742 ms
ban-%E5%A4%9A%E5%95%86%E6%88%B7%E5%85%A5%E9%A9%BB%E5%95%86%E5%9F%8E03.png
8272 ms
B2B%20O2O%20%E6%96%B0%20banner%202.png
14021 ms
B2B%20O2O%20%E6%96%B0%20banner.png
18063 ms
%E9%94%80%E5%94%AE%E4%B8%8D%E8%B4%A5%20BANNER.png
10903 ms
p24.png
5875 ms
p26.png
13586 ms
p28.png
13772 ms
p30.png
20082 ms
p27.png
19461 ms
p29.png
20082 ms
p29_1.png
19936 ms
p25.png
18653 ms
p29_2.png
20082 ms
p29_3.png
20082 ms
p29_4.png
20082 ms
p29_5.png
20083 ms
p29_6.png
20083 ms
p29_7.png
20083 ms
p32.png
20083 ms
p38.png
20083 ms
p37.png
20084 ms
1.png
20084 ms
2.png
20084 ms
3.png
20086 ms
4.png
20086 ms
5.png
20086 ms
6.png
20086 ms
7.png
20087 ms
8.png
20087 ms
9.png
20087 ms
10.png
20088 ms
11.png
20087 ms
12.png
20325 ms
mba.js
388 ms
mv.js
271 ms
b
1512 ms
t
3079 ms
t
2754 ms
index.php
2262 ms
13.png
19274 ms
h.js
717 ms
t.gif
2526 ms
ckmap.htm
651 ms
cm.gif
843 ms
21.gif
1345 ms
lxb.js
3045 ms
b.js
628 ms
hm.gif
340 ms
api.js
979 ms
weiboShow.css
34 ms
skin02.css
39 ms
gaea_1_19.js
41 ms
Panel.js
706 ms
localStorage.js
717 ms
0
1360 ms
icon_user.png
11 ms
806fe8c4jw1f2p9ksvucdj203c01qjr5.jpg
422 ms
806fe8c4jw1f210g6522xj20c81lxdtl.jpg
78 ms
806fe8c4jw1f1fz8xzs1xj20c815njz6.jpg
78 ms
806fe8c4jw1f0e4m9ekucj20c81ly10s.jpg
75 ms
806fe8c4jw1f1bdmoxlr2j20d007t0ua.jpg
66 ms
593793e5gw1f14h5q9m8vj20g40augn2.jpg
93 ms
806fe8c4jw1f115p44hh3j20c826lwy5.jpg
74 ms
btns_bg.png
7 ms
icon_follow.png
9 ms
806fe8c4jw1f060idiezkj20c82zg17o.jpg
263 ms
bsl.js
867 ms
m
532 ms
contains.js
236 ms
m
3201 ms
m
3594 ms
m
3971 ms
r.cgi
1872 ms
crmqq.php
15906 ms
wpa_first_heart_beat.php
705 ms
bpa.js
4808 ms
lxb.gif
759 ms
806fe8c4jw1ezvc9qqekvj20ci07it8y.jpg
34 ms
806fe8c4jw1ezop1gzoh6j209z05zt9a.jpg
32 ms
806fe8c4jw1ez71le542cj20du08b3zv.jpg
38 ms
suda.js
18 ms
806fe8c4jw1ezaimgmu5fj20dw08c3zf.jpg
33 ms
806fe8c4jw1ez2hkf7yzqj209a07q748.jpg
18 ms
806fe8c4jw1ez19drwvn3j20d709ymxe.jpg
34 ms
show.js
5 ms
bg_trans.png
8 ms
icon_tips.png
5 ms
Enter.php
900 ms
main_icon_invite_mess_api.js
4633 ms
main.css
2299 ms
fix.css
896 ms
version.js
2624 ms
tmp.gif
1294 ms
14.png
15661 ms
m
2588 ms
15.png
15624 ms
log.gif
479 ms
_l.js
3070 ms
1.png
15542 ms
bpaId
1019 ms
log.gif
464 ms
01.jpg
4510 ms
m-webim-lite.css
435 ms
m-webim-lite.js
3364 ms
Refresh.php
459 ms
stat.gif
863 ms
mess-text.png
777 ms
messbtn.png
863 ms
mess.gif
5060 ms
btn.png
2524 ms
2.png
10632 ms
3.png
10163 ms
4.png
11071 ms
5.png
9882 ms
Refresh.php
453 ms
6.png
5158 ms
7.png
5973 ms
8.png
5533 ms
9.png
4729 ms
10.png
7551 ms
11.png
5951 ms
12.png
5026 ms
13.png
5471 ms
14.png
4923 ms
15.png
5230 ms
1.png
7473 ms
2.png
6432 ms
3.png
8909 ms
4.png
6218 ms
5.png
7062 ms
6.png
6599 ms
7.png
7248 ms
8.png
6959 ms
9.png
8807 ms
10.png
8781 ms
11.png
10137 ms
12.png
11039 ms
13.png
7885 ms
14.png
8301 ms
15.png
8714 ms
1.png
9147 ms
2.png
9153 ms
Refresh.php
477 ms
3.png
9222 ms
4.png
11071 ms
5.png
8570 ms
6.png
8094 ms
7.png
10217 ms
8.png
8580 ms
9.png
10380 ms
10.png
7218 ms
11.png
6988 ms
12.png
7672 ms
13.png
9255 ms
14.png
8438 ms
15.png
7689 ms
show-class.png
13435 ms
p33.png
19028 ms
p34.png
9710 ms
p35.png
14064 ms
Refresh.php
416 ms
p36.png
11392 ms
cooper.png
10753 ms
copyright.png
14510 ms
show-fast-btn.png
10732 ms
hb.crm2.qq.com
541 ms
ico_index_01.png
12573 ms
ico_index_02.png
12077 ms
ico_index_03.png
12942 ms
Refresh.php
437 ms
hb.crm2.qq.com
546 ms
Refresh.php
343 ms
hb.crm2.qq.com
562 ms
Refresh.php
468 ms
hb.crm2.qq.com
611 ms
366ec.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
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
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.
366ec.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
366ec.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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 366ec.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 366ec.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.
366ec.com
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: