Tools & Wizards About Us
news.blogs.cnn.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

news.blogs.cnn.com

This Just In - CNN.com Blogs

Page Load Speed

5.5 sec in total

First Response

868 ms

Resources Loaded

3.2 sec

Page Rendered

1.4 sec

news.blogs.cnn.com screenshot

About Website

Click here to check amazing News Blogs CNN content for United States. Otherwise, check out these important facts you probably never knew about news.blogs.cnn.com

This Just In is CNN.com news blog. We'll bring you the latest news from CNN correspondents and sources around the world. We’ll cover stories that are breaking, causing ripples, or otherwise drivi...

Visit news.blogs.cnn.com

Key Findings

We analyzed News.blogs.cnn.com page load time and found that the first response time was 868 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

news.blogs.cnn.com performance score

0

Network Requests Diagram

news.blogs.cnn.com

868 ms

170 ms

bloglib-min.css

82 ms

new_thisjustin.common.css

136 ms

167 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original News.blogs.cnn.com, 31% (35 requests) were made to I.cdn.turner.com and 18% (21 requests) were made to I.cdn.cnn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Data.cnn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (63%)

Content Size

2.4 MB

After Optimization

873.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of News.blogs.cnn.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. 70% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 242.4 kB

  • Original 285.0 kB
  • After minification 267.9 kB
  • After compression 42.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. 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 242.4 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 12.4 kB

  • Original 298.4 kB
  • After minification 286.1 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. News Blogs CNN images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 1.1 MB

  • Original 1.6 MB
  • After minification 1.5 MB
  • After compression 505.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 1.1 MB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 187.9 kB

  • Original 227.3 kB
  • After minification 222.3 kB
  • After compression 39.5 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. News.blogs.cnn.com needs all CSS files to be minified and compressed as it can save up to 187.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (71%)

Requests Now

104

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

news.blogs.cnn.com

news.blogs.cnn.com

868 ms

170 ms

bloglib-min.css

bloglib-min.css

82 ms

new_thisjustin.common.css

new_thisjustin.common.css

136 ms

167 ms

179 ms

bloglib-min.js

bloglib-min.js

74 ms

twitter_banner.js

twitter_banner.js

106 ms

ajax.js

ajax.js

176 ms

swfobject-2.2.js

swfobject-2.2.js

105 ms

easing.js

easing.js

104 ms

article.js

article.js

104 ms

static-chrome-companion.min.js

static-chrome-companion.min.js

93 ms

jsmd.min.js

jsmd.min.js

46 ms

gprofiles.js

gprofiles.js

106 ms

wpgroho.js

wpgroho.js

193 ms

194 ms

load.min.js

load.min.js

44 ms

outbrain.js

outbrain.js

97 ms

w.js

w.js

104 ms

xd.sjs

xd.sjs

120 ms

controltag

controltag

31 ms

controltag.js.f8e94fa978cc2569e4b4423df4245d7e

controltag.js.f8e94fa978cc2569e4b4423df4245d7e

20 ms

cookie2json

cookie2json

25 ms

home.gif

home.gif

6 ms

4JHr5H_Y_normal.jpeg

4JHr5H_Y_normal.jpeg

30 ms

75F3HUoe_normal.png

75F3HUoe_normal.png

29 ms

klTcBowc_normal.png

klTcBowc_normal.png

29 ms

1px.gif

1px.gif

5 ms

follow.jpg

follow.jpg

102 ms

btn_close.gif

btn_close.gif

6 ms

grey_corner_TL.gif

grey_corner_TL.gif

24 ms

grey_corner_BL.gif

grey_corner_BL.gif

28 ms

1.gif

1.gif

28 ms

static-init.css

static-init.css

23 ms

background.gradient.jpg

background.gradient.jpg

60 ms

this.just.in.header.png

this.just.in.header.png

147 ms

arrow_right_sprite.png

arrow_right_sprite.png

90 ms

arrow_left_sprites.png

arrow_left_sprites.png

61 ms

top_right.png

top_right.png

57 ms

left_shadow.png

left_shadow.png

57 ms

blogscol_4x4_shadow.gif

blogscol_4x4_shadow.gif

59 ms

right_shadow.png

right_shadow.png

58 ms

blogs_posts_sprtr_7x7_shadow.gif

blogs_posts_sprtr_7x7_shadow.gif

61 ms

14x14_icon_rss.gif

14x14_icon_rss.gif

59 ms

twitter_15x12.gif

twitter_15x12.gif

58 ms

twitter_bubble_notch.png

twitter_bubble_notch.png

59 ms

calendar_bg.gif

calendar_bg.gif

7 ms

belief_sprite.gif

belief_sprite.gif

67 ms

bot.right.gif

bot.right.gif

9 ms

1.gif

1.gif

1088 ms

blogIndex.css

blogIndex.css

7 ms

vrs.js

vrs.js

26 ms

m

m

92 ms

vrt.outbrain.com

vrt.outbrain.com

87 ms

vrp.outbrain.com

vrp.outbrain.com

81 ms

hovercard.css

hovercard.css

55 ms

services.css

services.css

69 ms

chartbeat.js

chartbeat.js

66 ms

static-chrome.html

static-chrome.html

63 ms

d3t4zxd6snpsto.cloudfront.net

d3t4zxd6snpsto.cloudfront.net

38 ms

moatcontent.js

moatcontent.js

73 ms

main.js

main.js

31 ms

g.gif

g.gif

34 ms

g.gif

g.gif

29 ms

g.gif

g.gif

29 ms

ocs-notify.min.js

ocs-notify.min.js

53 ms

ping

ping

20 ms

all.js

all.js

272 ms

r2

r2

3 ms

cnn-header-minimal.min.js

cnn-header-minimal.min.js

39 ms

bid

bid

31 ms

cnn-static-chrome.min.js

cnn-static-chrome.min.js

20 ms

get

get

129 ms

static-header.html

static-header.html

33 ms

static-footer.html

static-footer.html

61 ms

menu_politics.png

menu_politics.png

20 ms

logo_cnn_nav_bottom.png

logo_cnn_nav_bottom.png

22 ms

logo_cnn_espaniol.png

logo_cnn_espaniol.png

40 ms

logo_cnn_arabic.png

logo_cnn_arabic.png

80 ms

menu_money.png

menu_money.png

15 ms

menu_style.png

menu_style.png

15 ms

menu_bleacher.png

menu_bleacher.png

16 ms

static-header.css

static-header.css

81 ms

static-edition-picker.css

static-edition-picker.css

70 ms

cnn-static-bundle.min.js

cnn-static-bundle.min.js

72 ms

cnn-static-footer-bundle.min.js

cnn-static-footer-bundle.min.js

49 ms

static-footer.css

static-footer.css

50 ms

plusone.js

plusone.js

212 ms

logo_cnn_badge_2up.png

logo_cnn_badge_2up.png

143 ms

sprite-s1dced3ff2b.png

sprite-s1dced3ff2b.png

148 ms

domestic.json

domestic.json

1264 ms

video_icon.gif

video_icon.gif

112 ms

ob_logo_16x16.png

ob_logo_16x16.png

100 ms

cnnsans-regular.woff

cnnsans-regular.woff

84 ms

cnnsans-medium.woff

cnnsans-medium.woff

83 ms

cnnsans-light.woff

cnnsans-light.woff

83 ms

cnnsans-thin.woff

cnnsans-thin.woff

82 ms

cnnsans-bold.woff

cnnsans-bold.woff

84 ms

cnnsans-heavy.woff

cnnsans-heavy.woff

81 ms

cnnsans-black.woff

cnnsans-black.woff

310 ms

cnn-icons.woff

cnn-icons.woff

83 ms

comScore.htm

comScore.htm

5 ms

beacon.js

beacon.js

4 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

knockout-2.1.0.js

knockout-2.1.0.js

4 ms

model.js

model.js

29 ms

widgets.js

widgets.js

165 ms

in.js

in.js

164 ms

236 ms

xd_arbiter.php

xd_arbiter.php

215 ms

xd_arbiter.php

xd_arbiter.php

422 ms

widgetGlobalEvent

widgetGlobalEvent

39 ms

secureAnonymousFramework

secureAnonymousFramework

28 ms

SEO Factors

news.blogs.cnn.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 News.blogs.cnn.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 News.blogs.cnn.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

news.blogs.cnn.com

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