9.7 sec in total
804 ms
8.3 sec
674 ms
Visit datayes.com now to see the best up-to-date Datayes content for China and also check out these interesting facts you probably never knew about datayes.com
通联数据股份公司(DataYes)是由金融和高科技资深专家发起,中国万向控股有限公司投资成立的一家金融科技公司。致力于将大数据、云计算、人工智能、ai推荐等技术和量本投资等投资理念相结合,打造国际一流的、具有革命性意义的智能投资管理平台。
Visit datayes.comWe analyzed Datayes.com page load time and found that the first response time was 804 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
datayes.com performance score
name
value
score
weighting
Value16.0 s
0/100
10%
Value53.1 s
0/100
25%
Value28.0 s
0/100
10%
Value510 ms
57/100
30%
Value0.325
35/100
15%
Value46.4 s
0/100
10%
804 ms
639 ms
6 ms
520 ms
619 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 80% of them (68 requests) were addressed to the original Datayes.com, 4% (3 requests) were made to Gartner.com and 4% (3 requests) were made to Cloud-static.datayes.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Datayes.com.
Page size can be reduced by 286.6 kB (6%)
4.8 MB
4.6 MB
In fact, the total size of Datayes.com main page is 4.8 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. 40% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 30.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 30.4 kB or 76% of the original size.
Potential reduce by 254.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. Datayes images are well optimized though.
Potential reduce by 945 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 399 B
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. Datayes.com has all CSS files already compressed.
Number of requests can be reduced by 26 (35%)
74
48
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datayes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
datayes.com
804 ms
www.datayes.com
639 ms
jquery-2-e43ee6ffc5.2.0.min.js
6 ms
font-awesome-81ce96f2e2.min.css
520 ms
slick-8adebef0d1.css
619 ms
index-8693a114cf.css
877 ms
animate-81a755ceee.min.css
924 ms
jquery-66b5f43527.localize.min.js
15 ms
jquery-9e61300bb0.validate.js
15 ms
jquery-ui-e156ef43c9.js
100 ms
axios-66c5bc3238.min.js
17 ms
widget-ab5db51fe0.js
91 ms
datayes-7bc2f7aa6d.config.js
93 ms
jquery-bd55bff2a4.cookie.min.js
113 ms
publicv1-55e41d9056.js
102 ms
upload-0cb8768f1b.js
175 ms
slick-15b6d68558.min.js
114 ms
jquery-767965adc0.lazyload.js
119 ms
indexNews-fd29a17d56.js
121 ms
login-ec34c80fea.js
124 ms
publicjs-9b7666c40c.js
175 ms
wow-942b9c8853.min.js
183 ms
widget-ab5db51fe0.js
61 ms
js
62 ms
js
107 ms
weixin.png
860 ms
logo.png
707 ms
close.png
579 ms
bmwmbanner.jpg
870 ms
mobile.png
803 ms
bannerBg.png
763 ms
bmwbanner.jpg
1776 ms
slogan.png
1192 ms
banner01.png
1404 ms
light.png
1742 ms
banner02.png
1588 ms
banner03.png
1704 ms
banner04.png
1579 ms
banner05.png
2148 ms
banner06.png
2295 ms
proroboams.png
2098 ms
proroboamsen.png
2472 ms
brands.png
2508 ms
spriteIcon.png
2652 ms
proapp.png
2490 ms
prouqer.png
2882 ms
dataapi.png
3200 ms
solutionbg.png
3149 ms
spritenum.png
2890 ms
dialogarr.png
3088 ms
voice01.png
3057 ms
voice02.png
3765 ms
voice03.png
3220 ms
voice04.png
3879 ms
quot.png
3373 ms
spritebrand.png
4024 ms
code2.png
3545 ms
code.png
3830 ms
logolight.png
3707 ms
beian.png
3883 ms
952 ms
index.js
124 ms
analytics.js
16 ms
widget.css
110 ms
data
54 ms
BEBAS.ttf
3797 ms
js
33 ms
common.0411.css
10 ms
udesk.json
757 ms
icons2.png
10 ms
fontawesome-webfont.woff
3910 ms
slick.woff
3592 ms
ajax-loader.gif
3696 ms
udeskApi.js
785 ms
1.png
3460 ms
2.png
3164 ms
3.png
3298 ms
4.png
3370 ms
www.datayes.com
3173 ms
out_config
1363 ms
emotion.css
259 ms
client-btn.png
544 ms
free
1134 ms
slick.ttf
370 ms
slick.svg
689 ms
datayes.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
datayes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
datayes.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datayes.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 Datayes.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.
datayes.com
Open Graph description is not detected on the main page of Datayes. 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: