Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

datayes.com

通联数据—AI赋能投资

Page Load Speed

9.7 sec in total

First Response

804 ms

Resources Loaded

8.3 sec

Page Rendered

674 ms

About Website

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.com

Key Findings

We 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.

Performance Metrics

datayes.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value53.1 s

0/100

25%

SI (Speed Index)

Value28.0 s

0/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.325

35/100

15%

TTI (Time to Interactive)

Value46.4 s

0/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 286.6 kB (6%)

Content Size

4.8 MB

After Optimization

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.

HTML Optimization

-76%

Potential reduce by 30.4 kB

  • Original 40.2 kB
  • After minification 40.2 kB
  • After compression 9.8 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.

Image Optimization

-6%

Potential reduce by 254.8 kB

  • Original 4.6 MB
  • After minification 4.4 MB

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.

JavaScript Optimization

-1%

Potential reduce by 945 B

  • Original 157.2 kB
  • After minification 157.2 kB
  • After compression 156.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 399 B

  • Original 29.8 kB
  • After minification 29.8 kB
  • After compression 29.4 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. Datayes.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (35%)

Requests Now

74

After Optimization

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.

Accessibility Review

datayes.com accessibility score

70

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

<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

High

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

datayes.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

datayes.com SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: