Tools & Wizards About Us
featuresblogs.chicagotribune.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

featuresblogs.chicagotribune.com

TV Listings, News & Reviews - Chicago Tribune

Page Load Speed

2 sec in total

First Response

168 ms

Resources Loaded

1.7 sec

Page Rendered

104 ms

featuresblogs.chicagotribune.com screenshot

About Website

Click here to check amazing Featuresblogs Chicago Tribune content for United States. Otherwise, check out these important facts you probably never knew about featuresblogs.chicagotribune.com

TV listings, news and reviews from the Chicago Tribune. Find TV reviews of latest episodes and new shows. Get TV schedules for Chicago.

Visit featuresblogs.chicagotribune.com

Key Findings

We analyzed Featuresblogs.chicagotribune.com page load time and found that the first response time was 168 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

featuresblogs.chicagotribune.com performance score

0

Network Requests Diagram

featuresblogs.chicagotribune.com

168 ms

prototype.js

15 ms

scriptaculous.js

12 ms

tabinterface.js

9 ms

AC_RunActiveContent.js

12 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 10% of them (5 requests) were addressed to the original Featuresblogs.chicagotribune.com, 25% (13 requests) were made to Chicagotribune.com and 13% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (257 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 620.1 kB (70%)

Content Size

879.9 kB

After Optimization

259.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Featuresblogs.chicagotribune.com main page is 879.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. 60% of websites need less resources to load. Javascripts take 525.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.9 kB

  • Original 19.3 kB
  • After minification 18.1 kB
  • After compression 5.4 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 13.9 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 441 B

  • Original 29.4 kB
  • After minification 29.0 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. Featuresblogs Chicago Tribune images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 337.9 kB

  • Original 525.7 kB
  • After minification 514.1 kB
  • After compression 187.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 337.9 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 267.9 kB

  • Original 305.5 kB
  • After minification 269.7 kB
  • After compression 37.6 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. Featuresblogs.chicagotribune.com needs all CSS files to be minified and compressed as it can save up to 267.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (75%)

Requests Now

48

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

featuresblogs.chicagotribune.com

featuresblogs.chicagotribune.com

168 ms

prototype.js

prototype.js

15 ms

scriptaculous.js

scriptaculous.js

12 ms

tabinterface.js

tabinterface.js

9 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

12 ms

cookies.js

cookies.js

48 ms

menu.js

menu.js

112 ms

reset.css

reset.css

35 ms

common.css

common.css

157 ms

market.css

market.css

35 ms

styles.css

styles.css

198 ms

s_code_trb.js

s_code_trb.js

34 ms

quant.js

quant.js

10 ms

print.css

print.css

157 ms

ct_small_blog.gif

ct_small_blog.gif

4 ms

base-weblog.css

base-weblog.css

233 ms

asterisk-style.css

asterisk-style.css

142 ms

tribune.css

tribune.css

197 ms

30_black.gif

30_black.gif

7 ms

watcher;tile=1;dcopt=ist;ptype=sf;sz=728x90;ord=3139446822460741

watcher;tile=1;dcopt=ist;ptype=sf;sz=728x90;ord=3139446822460741

60 ms

46895467.png

46895467.png

9 ms

46895467.png

46895467.png

8 ms

7476.js

7476.js

75 ms

lidar.js

lidar.js

9 ms

sync

sync

19 ms

76230-2.js

76230-2.js

185 ms

show_ads.js

show_ads.js

5 ms

ca-pub-5190935653373739.js

ca-pub-5190935653373739.js

63 ms

zrt_lookup.html

zrt_lookup.html

148 ms

show_ads_impl.js

show_ads_impl.js

97 ms

emily.html

emily.html

49 ms

moatad.js

moatad.js

50 ms

ga.js

ga.js

116 ms

stats

stats

194 ms

pixel;r=15794476;a=p-fcYWUmj5YbYKM;tags=typepad.extended;fpan=1;fpa=P0-1485461647-1456783445689;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456783445687;tzo=-180;ref=;url=http%3A%2F%2Ffeaturesblogs.chicagotribune.com%2F;ogl=

pixel;r=15794476;a=p-fcYWUmj5YbYKM;tags=typepad.extended;fpan=1;fpa=P0-1485461647-1456783445689;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456783445687;tzo=-180;ref=;url=http%3A%2F%2Ffeaturesblogs.chicagotribune.com%2F;ogl=

106 ms

beacon.js

beacon.js

51 ms

sp.gz.js

sp.gz.js

98 ms

ads

ads

257 ms

osd.js

osd.js

46 ms

i

i

30 ms

__utm.gif

__utm.gif

36 ms

r

r

28 ms

js

js

153 ms

img

img

66 ms

pixel

pixel

44 ms

push

push

40 ms

ck-confirm

ck-confirm

147 ms

Q116_Wu_Com_Awareness_V3_D_728x90_EN_US.jpg

Q116_Wu_Com_Awareness_V3_D_728x90_EN_US.jpg

40 ms

lidar.js

lidar.js

23 ms

sbhK2lTE.js

sbhK2lTE.js

32 ms

cTrvNaRi.html

cTrvNaRi.html

6 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

17 ms

SEO Factors

featuresblogs.chicagotribune.com SEO score

0

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 Featuresblogs.chicagotribune.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 Featuresblogs.chicagotribune.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

featuresblogs.chicagotribune.com

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