Tools & Wizards About Us
cookchen.blog.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cookchen.blog.com

cookchen | Writing away with Blog.com

Page Load Speed

5.7 sec in total

First Response

1.7 sec

Resources Loaded

2.7 sec

Page Rendered

1.3 sec

cookchen.blog.com screenshot

About Website

Welcome to cookchen.blog.com homepage info - get ready to check Cookchen Blog best content for China right away, or after learning these important things about cookchen.blog.com

Writing away with Blog.com

Visit cookchen.blog.com

Key Findings

We analyzed Cookchen.blog.com page load time and found that the first response time was 1.7 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

cookchen.blog.com performance score

0

Network Requests Diagram

cookchen.blog.com

1721 ms

style.css

222 ms

admin-bar.css

213 ms

blogcom-admin-bar.css

215 ms

sociable.css

222 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 57% of them (28 requests) were addressed to the original Cookchen.blog.com, 10% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Cookchen.blog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.1 kB (50%)

Content Size

565.6 kB

After Optimization

283.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cookchen.blog.com main page is 565.6 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. 45% of websites need less resources to load. Javascripts take 242.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 94.1 kB

  • Original 122.8 kB
  • After minification 119.2 kB
  • After compression 28.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 94.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 310 B

  • Original 141.6 kB
  • After minification 141.3 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. Cookchen Blog images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 139.6 kB

  • Original 242.8 kB
  • After minification 236.3 kB
  • After compression 103.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 139.6 kB or 57% of the original size.

CSS Optimization

-82%

Potential reduce by 48.1 kB

  • Original 58.4 kB
  • After minification 44.6 kB
  • After compression 10.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. Cookchen.blog.com needs all CSS files to be minified and compressed as it can save up to 48.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (80%)

Requests Now

41

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cookchen.blog.com

cookchen.blog.com

1721 ms

style.css

style.css

222 ms

admin-bar.css

admin-bar.css

213 ms

blogcom-admin-bar.css

blogcom-admin-bar.css

215 ms

sociable.css

sociable.css

222 ms

nggallery.css

nggallery.css

227 ms

shutter-reloaded.css

shutter-reloaded.css

228 ms

cssreset-context.css

cssreset-context.css

13 ms

base.css

base.css

314 ms

twitter.css

twitter.css

317 ms

google.css

google.css

329 ms

browserid.css

browserid.css

324 ms

facebook.css

facebook.css

337 ms

l10n.js

l10n.js

339 ms

jquery.js

jquery.js

526 ms

sociable.js

sociable.js

421 ms

plusone.js

plusone.js

36 ms

widgets.js

widgets.js

8 ms

pinit.js

pinit.js

61 ms

shutter-reloaded.js

shutter-reloaded.js

429 ms

swfobject.js

swfobject.js

438 ms

ngg.js

ngg.js

447 ms

base.js

base.js

449 ms

twitter.js

twitter.js

566 ms

google.js

google.js

566 ms

browserid.js

browserid.js

567 ms

include.js

include.js

43 ms

facebook.js

facebook.js

572 ms

audio-player.js

audio-player.js

572 ms

include.js

include.js

35 ms

admin-bar.js

admin-bar.js

550 ms

quant.js

quant.js

7 ms

css

css

25 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

96 ms

pinit_main.js

pinit_main.js

127 ms

ados.js

ados.js

62 ms

ga.js

ga.js

62 ms

ginko.jpg

ginko.jpg

495 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

54 ms

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

55 ms

cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf

cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf

56 ms

c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf

c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf

55 ms

QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf

QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf

55 ms

ados

ados

33 ms

__utm.gif

__utm.gif

17 ms

__utm.gif

__utm.gif

33 ms

pixel;r=724901665;a=p-b3DDIGtNmjMZA;fpan=1;fpa=P0-655345792-1458473163115;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458473163114;tzo=-180;ref=;url=http%3A%2F%2Fcookchen.blog.com%2F;ogl=site_name.cookchen%2Ctype.blog%2Ctitle.cookchen%2Curl.http%3A%2F%2Fcookchen%252Eblog%252Ecom%2Cdescription.Writing%20away%20with%20Blog%252Ecom%2Cimage.http%3A%2F%2Fblog%252Ecom%2Fwp-content%2Favatars%2Fblog%2Fdefault-avatar-80%252Epng

pixel;r=724901665;a=p-b3DDIGtNmjMZA;fpan=1;fpa=P0-655345792-1458473163115;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458473163114;tzo=-180;ref=;url=http%3A%2F%2Fcookchen.blog.com%2F;ogl=site_name.cookchen%2Ctype.blog%2Ctitle.cookchen%2Curl.http%3A%2F%2Fcookchen%252Eblog%252Ecom%2Cdescription.Writing%20away%20with%20Blog%252Ecom%2Cimage.http%3A%2F%2Fblog%252Ecom%2Fwp-content%2Favatars%2Fblog%2Fdefault-avatar-80%252Epng

28 ms

admin-bar-bg.png

admin-bar-bg.png

108 ms

bc-avatar.png

bc-avatar.png

116 ms

SEO Factors

cookchen.blog.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cookchen.blog.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cookchen.blog.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

cookchen.blog.com

Open Graph data is detected on the main page of Cookchen Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: