16.3 sec in total
832 ms
14.9 sec
651 ms
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.comWe analyzed Dataeye.com page load time and found that the first response time was 832 ms and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dataeye.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.7 s
33/100
25%
Value13.1 s
2/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
832 ms
1817 ms
932 ms
938 ms
1398 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Dataeye.com, 2% (1 request) were made to Zgsdk.37degree.com and 2% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (8.9 sec) belongs to the original domain Dataeye.com.
Page size can be reduced by 312.3 kB (31%)
1.0 MB
699.5 kB
In fact, the total size of Dataeye.com main page is 1.0 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. 30% of websites need less resources to load. Images take 641.8 kB which makes up the majority of the site volume.
Potential reduce by 16.6 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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.6 kB or 72% of the original size.
Potential reduce by 64.5 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. Data Eye images are well optimized though.
Potential reduce by 231.3 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 231.3 kB or 67% of the original size.
Number of requests can be reduced by 5 (10%)
51
46
The browser has sent 51 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 6 to 1 for JavaScripts and as a result speed up the page load time.
dataeye.com
832 ms
www.dataeye.com
1817 ms
slick.css
932 ms
slick-theme.css
938 ms
css.css
1398 ms
require.js
4589 ms
core-base.js
2505 ms
app-base.js
999 ms
app.js
2368 ms
analytics.js
1308 ms
zhuge-lastest.min.js
3598 ms
logo.png
1335 ms
hot.gif
1444 ms
bg-repeat.png
3738 ms
bg.png
3153 ms
slogan-en.png
2419 ms
arrow.png
3350 ms
circle.png
4059 ms
tracking-big.png
4060 ms
store-big.png
4270 ms
game-big.png
4624 ms
html-big.png
4276 ms
dmp-big.png
4723 ms
icon.png
5274 ms
bg-s-en.jpg
5753 ms
icon-b.png
5300 ms
arrow-s-up.png
5334 ms
people.png
5531 ms
icon-s.png
5984 ms
01.png
6560 ms
02.png
6578 ms
03.png
6571 ms
04.png
6738 ms
05.png
6966 ms
06.png
7289 ms
07.png
7821 ms
08.png
7946 ms
09.png
7948 ms
china_mobile.jpg
7693 ms
coolpad.jpg
7949 ms
tencent.jpg
8281 ms
ksyun.jpg
8687 ms
tcl.jpg
8783 ms
fontawesome-webfont.woff
8874 ms
360.jpg
7845 ms
collect
47 ms
letv.jpg
7611 ms
adups.jpg
8404 ms
collect
85 ms
ga-audiences
47 ms
lie_bao.jpg
8485 ms
itools.png
7557 ms
btn_qq.png
6846 ms
weixin.gif
7313 ms
3
3615 ms
newGovIcon.gif
7050 ms
dataeye.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
Image elements do not have [alt] attributes
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.
dataeye.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dataeye.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
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 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.
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: