Tools & Wizards About Us
mobile.chicagotribune.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobile.chicagotribune.com

Chicago Tribune: Chicago news, sports, weather, entertainment - Chicago Tribune

Page Load Speed

601 ms in total

First Response

109 ms

Resources Loaded

299 ms

Page Rendered

193 ms

mobile.chicagotribune.com screenshot

About Website

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

Chicago Tribune

Visit mobile.chicagotribune.com

Key Findings

We analyzed Mobile.chicagotribune.com page load time and found that the first response time was 109 ms and then it took 492 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

mobile.chicagotribune.com performance score

0

Network Requests Diagram

mobile.chicagotribune.com

109 ms

fonts.css

7 ms

app.css

27 ms

modernizr.js

15 ms

socialize.js

12 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 19% of them (3 requests) were addressed to the original Mobile.chicagotribune.com, 44% (7 requests) were made to D2zurjx5226n47.cloudfront.net and 6% (1 request) were made to Cdn.gigya.com. The less responsive or slowest element that took the longest time to load (109 ms) belongs to the original domain Mobile.chicagotribune.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.9 kB (41%)

Content Size

441.3 kB

After Optimization

258.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-66%

Potential reduce by 9.0 kB

  • Original 13.6 kB
  • After minification 12.8 kB
  • After compression 4.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 9.0 kB or 66% of the original size.

Image Optimization

-1%

Potential reduce by 885 B

  • Original 173.8 kB
  • After minification 172.9 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. Mobile Chicago Tribune images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 119.1 kB

  • Original 192.4 kB
  • After minification 192.4 kB
  • After compression 73.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 119.1 kB or 62% of the original size.

CSS Optimization

-88%

Potential reduce by 53.9 kB

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

Requests Breakdown

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

Requests Now

15

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobile.chicagotribune.com

mobile.chicagotribune.com

109 ms

fonts.css

fonts.css

7 ms

app.css

app.css

27 ms

modernizr.js

modernizr.js

15 ms

socialize.js

socialize.js

12 ms

app.js

app.js

24 ms

thirdpartyservice

thirdpartyservice

100 ms

activityi;src=4555615;type=appla0;cat=appla0;ord=6412407616153.359

activityi;src=4555615;type=appla0;cat=appla0;ord=6412407616153.359

44 ms

panel-bg-intro.jpg

panel-bg-intro.jpg

13 ms

svg-icon-app.svg

svg-icon-app.svg

66 ms

svg-icon-app.svg

svg-icon-app.svg

9 ms

panel-example-intro.png

panel-example-intro.png

21 ms

icons.woff

icons.woff

13 ms

sp.gz.js

sp.gz.js

9 ms

i

i

4 ms

nr-885.min.js

nr-885.min.js

18 ms

SEO Factors

mobile.chicagotribune.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.chicagotribune.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Mobile.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

mobile.chicagotribune.com

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