Tools & Wizards About Us
talkingdata.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

talkingdata.com

TalkingData-移动.数据.价值

Page Load Speed

28.7 sec in total

First Response

3.7 sec

Resources Loaded

24.2 sec

Page Rendered

777 ms

talkingdata.com screenshot

About Website

Welcome to talkingdata.com homepage info - get ready to check Talking Data best content for China right away, or after learning these important things about talkingdata.com

TalkingData Mobile Big Data Platform；We offer the best-in-class data analytics products&services and the most insightful mobile industry analysis to accelerate your success with the value of Data.

Visit talkingdata.com

Key Findings

We analyzed Talkingdata.com page load time and found that the first response time was 3.7 sec and then it took 25 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.

Performance Metrics

talkingdata.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.3 s

93/100

10%

Network Requests Diagram

talkingdata.com

3734 ms

www.talkingdata.com

1464 ms

www.talkingdata.com

3928 ms

index-en_us.min.css

1153 ms

index.min.js

4206 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 80% of them (33 requests) were addressed to the original Talkingdata.com, 12% (5 requests) were made to Appindex.talkingdata.com and 5% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (13.8 sec) belongs to the original domain Talkingdata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.5 kB (27%)

Content Size

802.8 kB

After Optimization

584.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Talkingdata.com main page is 802.8 kB. 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 569.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 34.5 kB

  • Original 41.8 kB
  • After minification 31.9 kB
  • After compression 7.3 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 9.9 kB, which is 24% 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 34.5 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 49.8 kB

  • Original 569.2 kB
  • After minification 519.4 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. Talking Data images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 93.1 kB

  • Original 142.4 kB
  • After minification 142.3 kB
  • After compression 49.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 93.1 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 41.1 kB

  • Original 49.4 kB
  • After minification 49.4 kB
  • After compression 8.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. Talkingdata.com needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (10%)

Requests Now

31

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

talkingdata.com

talkingdata.com

3734 ms

www.talkingdata.com

www.talkingdata.com

1464 ms

www.talkingdata.com

www.talkingdata.com

3928 ms

index-en_us.min.css

index-en_us.min.css

1153 ms

index.min.js

index.min.js

4206 ms

kf5.js

kf5.js

10 ms

bg-home-banner.jpg

bg-home-banner.jpg

3375 ms

logo-en_us.png

logo-en_us.png

1771 ms

icon-menuOnChoose.png

icon-menuOnChoose.png

1781 ms

icon-menuOnChoose.png

icon-menuOnChoose.png

4275 ms

pic-line.png

pic-line.png

2860 ms

icon-news-breviary.png

icon-news-breviary.png

2219 ms

1453260223645.jpg

1453260223645.jpg

2022 ms

pic-telescope.png

pic-telescope.png

2418 ms

logo-bottom-white.png

logo-bottom-white.png

4795 ms

logo-bottom.png

logo-bottom.png

844 ms

wechat-code.png

wechat-code.png

3450 ms

index-large.png

index-large.png

3786 ms

index-middle.png

index-middle.png

7709 ms

bg-timeline.png

bg-timeline.png

9163 ms

pic-eye.png

pic-eye.png

5675 ms

icon-news.png

icon-news.png

5200 ms

pic-bookrack.png

pic-bookrack.png

6611 ms

bg-bottomCloud.png

bg-bottomCloud.png

7133 ms

index-partner.png

index-partner.png

7628 ms

icon_round.png

icon_round.png

8084 ms

icon-contact.png

icon-contact.png

10169 ms

icon-social.png

icon-social.png

13065 ms

plus-icon.png

plus-icon.png

9916 ms

kefa-webfont.woff

kefa-webfont.woff

13827 ms

ranking.html

ranking.html

1185 ms

ranking.html

ranking.html

775 ms

ranking.html

ranking.html

756 ms

ranking.html

ranking.html

773 ms

main.js

main.js

10308 ms

hm.js

hm.js

10157 ms

time=4249

time=4249

4 ms

sprite.png

sprite.png

9270 ms

www.talkingdata.com

www.talkingdata.com

10541 ms

ranking.html

ranking.html

716 ms

hm.gif

hm.gif

342 ms

Accessibility Review

talkingdata.com accessibility score

71

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

talkingdata.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

talkingdata.com SEO score

81

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Talkingdata.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Talkingdata.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

talkingdata.com

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