Tools & Wizards About Us
blog.talkingdata.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.talkingdata.net

TalkingData's Blog – 现在开始，用数据说话。

Page Load Speed

42.1 sec in total

First Response

9.8 sec

Resources Loaded

31 sec

Page Rendered

1.4 sec

blog.talkingdata.net screenshot

About Website

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

TalkingData博客

Visit blog.talkingdata.net

Key Findings

We analyzed Blog.talkingdata.net page load time and found that the first response time was 9.8 sec and then it took 32.3 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. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

blog.talkingdata.net performance score

0

Network Requests Diagram

blog.talkingdata.net

9781 ms

style.css

853 ms

normalize.min.css

1776 ms

main.css

1591 ms

prettyPhoto.css

1587 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 90% of them (37 requests) were addressed to the original Blog.talkingdata.net, 7% (3 requests) were made to Static.duoshuo.com and 2% (1 request) were made to Tdblog.duoshuo.com. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain Blog.talkingdata.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.5 kB (34%)

Content Size

821.9 kB

After Optimization

539.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.talkingdata.net main page is 821.9 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. 25% of websites need less resources to load. Images take 471.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.1 kB

  • Original 42.1 kB
  • After minification 38.9 kB
  • After compression 10.0 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 32.1 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 21.3 kB

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

JavaScript Optimization

-70%

Potential reduce by 138.3 kB

  • Original 197.1 kB
  • After minification 175.8 kB
  • After compression 58.8 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 138.3 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 90.9 kB

  • Original 110.9 kB
  • After minification 96.4 kB
  • After compression 20.1 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. Blog.talkingdata.net needs all CSS files to be minified and compressed as it can save up to 90.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (50%)

Requests Now

30

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog 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 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

blog.talkingdata.net

blog.talkingdata.net

9781 ms

style.css

style.css

853 ms

normalize.min.css

normalize.min.css

1776 ms

main.css

main.css

1591 ms

prettyPhoto.css

prettyPhoto.css

1587 ms

superfish.css

superfish.css

824 ms

flexslider.css

flexslider.css

1256 ms

embed.js

embed.js

286 ms

jquery.js

jquery.js

7202 ms

embed.default.css

embed.default.css

135 ms

embed.compat.js

embed.compat.js

347 ms

jquery-migrate.min.js

jquery-migrate.min.js

2132 ms

modernizr-2.6.1-respond-1.1.0.min.js

modernizr-2.6.1-respond-1.1.0.min.js

844 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

2924 ms

superfish.js

superfish.js

435 ms

custom.js

custom.js

5981 ms

jquery.fitvids.js

jquery.fitvids.js

3554 ms

jquery.flexslider.js

jquery.flexslider.js

3230 ms

bk_header.png

bk_header.png

3693 ms

blog-logo.png

blog-logo.png

908 ms

social.png

social.png

1327 ms

1004x3621121.jpg

1004x3621121.jpg

5777 ms

1004x362112.jpg

1004x362112.jpg

7152 ms

DMP1.jpg

DMP1.jpg

19926 ms

1004x362%E5%8D%9A%E5%AE%A2banner.jpg

1004x362%E5%8D%9A%E5%AE%A2banner.jpg

10798 ms

1004x36211.jpg

1004x36211.jpg

14701 ms

123.jpg

123.jpg

7805 ms

556f173f20de8d8b218b637b-2-hd.jpg

556f173f20de8d8b218b637b-2-hd.jpg

15796 ms

QQ%E6%88%AA%E5%9B%BE20160406134728.png

QQ%E6%88%AA%E5%9B%BE20160406134728.png

19922 ms

150727f14nv4drvrf1sszd.jpg

150727f14nv4drvrf1sszd.jpg

10054 ms

1.jpg

1.jpg

15877 ms

23.png

23.png

19922 ms

%E5%88%9B%E6%84%8F.png

%E5%88%9B%E6%84%8F.png

19921 ms

Leo%E4%BB%8B%E7%BB%8D%E5%85%AC%E5%8F%B82.jpg

Leo%E4%BB%8B%E7%BB%8D%E5%85%AC%E5%8F%B82.jpg

19922 ms

1447119064900.jpg

1447119064900.jpg

17439 ms

%E5%B9%BB%E7%81%AF%E7%89%8712.jpg

%E5%B9%BB%E7%81%AF%E7%89%8712.jpg

19921 ms

searchsubmit.gif

searchsubmit.gif

19888 ms

comments.png

comments.png

19887 ms

continue.png

continue.png

19888 ms

widget_title.png

widget_title.png

19887 ms

counts.json

counts.json

998 ms

SEO Factors

blog.talkingdata.net SEO score

0

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 Blog.talkingdata.net 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 Blog.talkingdata.net 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

blog.talkingdata.net

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