Tools & Wizards About Us
dataeye.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

dataeye.com

DataEye_全球移动广告营销情报中心

Page Load Speed

14.7 sec in total

First Response

693 ms

Resources Loaded

13 sec

Page Rendered

1.1 sec

dataeye.com screenshot

About Website

Visit dataeye.com now to see the best up-to-date Data Eye content for China and also check out these interesting facts you probably never knew about dataeye.com

DataEye,行业领先的移动营销数据分析工具,提供移动广告投放分析,手游数据分析,广告投放效果监测等服务,为行业提供优秀的数据化垂直解决方案。

Visit dataeye.com

Key Findings

We analyzed Dataeye.com page load time and found that the first response time was 693 ms and then it took 14 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dataeye.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

dataeye.com

693 ms

dataeye.com

925 ms

www.dataeye.com

1338 ms

www.dataeye.com

237 ms

home.css

227 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 93% of them (57 requests) were addressed to the original Dataeye.com, 3% (2 requests) were made to Www-cdn.dataeye.com and 3% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Dataeye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.9 kB (11%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images

In fact, the total size of Dataeye.com main page is 2.4 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. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 168.2 kB

  • Original 237.3 kB
  • After minification 226.8 kB
  • After compression 69.1 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 168.2 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 83.7 kB

  • Original 2.1 MB
  • After minification 2.0 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. Data Eye images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 6 (11%)

Requests Now

57

After Optimization

51

  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

dataeye.com

dataeye.com

693 ms

dataeye.com

dataeye.com

925 ms

www.dataeye.com

www.dataeye.com

1338 ms

www.dataeye.com

www.dataeye.com

237 ms

home.css

home.css

227 ms

iconfont.js

iconfont.js

1121 ms

require.js

require.js

891 ms

jquery.js

jquery.js

1121 ms

bootstrap.css

bootstrap.css

2346 ms

swiper.css

swiper.css

2585 ms

hm.js

hm.js

1258 ms

bg.png

bg.png

3568 ms

1.png

1.png

3591 ms

2.png

2.png

5594 ms

3.png

3.png

4966 ms

adxray.png

adxray.png

1543 ms

oversea.png

oversea.png

956 ms

cloud.png

cloud.png

1431 ms

tidea.png

tidea.png

3398 ms

report.png

report.png

1763 ms

title-bg.png

title-bg.png

1984 ms

1.png

1.png

2205 ms

2.png

2.png

2427 ms

scenes.png

scenes.png

2868 ms

bg.png

bg.png

5544 ms

1.png

1.png

3636 ms

2.png

2.png

3783 ms

3.png

3.png

3811 ms

4.png

4.png

3872 ms

5.png

5.png

4008 ms

6.png

6.png

4033 ms

7.png

7.png

4110 ms

8.png

8.png

4231 ms

9.png

9.png

4255 ms

10.png

10.png

4348 ms

11.png

11.png

4456 ms

12.png

12.png

4477 ms

13.png

13.png

4586 ms

14.png

14.png

4679 ms

15.png

15.png

4698 ms

16.png

16.png

4823 ms

17.png

17.png

4904 ms

18.png

18.png

4921 ms

19.png

19.png

5062 ms

20.png

20.png

5129 ms

21.png

21.png

5143 ms

22.png

22.png

5189 ms

home.js

home.js

4348 ms

hm.gif

hm.gif

308 ms

footer.js

footer.js

3926 ms

23.png

23.png

3827 ms

24.png

24.png

3655 ms

25.png

25.png

3558 ms

26.png

26.png

3375 ms

27.png

27.png

3163 ms

28.png

28.png

2776 ms

29.png

29.png

2385 ms

30.png

30.png

2209 ms

qr-wxkf.png

qr-wxkf.png

2443 ms

qrcode.png

qrcode.png

2180 ms

swiper.js

swiper.js

1634 ms

Accessibility Review

dataeye.com accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

dataeye.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dataeye.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

dataeye.com

Open Graph description is not detected on the main page of Data Eye. 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: