Tools & Wizards About Us

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    55% of websites

mobile.chicagotribune.com

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

Page Load Speed

2.6 sec in total

First Response

29 ms

Resources Loaded

1.8 sec

Page Rendered

763 ms

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 29 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

mobile.chicagotribune.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value26.6 s

0/100

10%

TBT (Total Blocking Time)

Value27,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.383

27/100

15%

TTI (Time to Interactive)

Value62.9 s

0/100

10%

Network Requests Diagram

mobile.chicagotribune.com

29 ms

www.chicagotribune.com

4 ms

www.chicagotribune.com

27 ms

css2

94 ms

11 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mobile.chicagotribune.com, 31% (32 requests) were made to Chicagotribune.com and 20% (21 requests) were made to Cdn59755463.blazingcdn.net. The less responsive or slowest element that took the longest time to load (707 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 686.7 kB (27%)

Content Size

2.5 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile.chicagotribune.com main page is 2.5 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. Only a small number of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 233.9 kB

  • Original 278.9 kB
  • After minification 263.4 kB
  • After compression 45.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 233.9 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 20.1 kB

  • Original 269.5 kB
  • After minification 249.4 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

-25%

Potential reduce by 427.4 kB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 1.3 MB

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 427.4 kB or 25% of the original size.

CSS Optimization

-2%

Potential reduce by 5.3 kB

  • Original 242.3 kB
  • After minification 242.3 kB
  • After compression 237.0 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (69%)

Requests Now

67

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 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 36 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

mobile.chicagotribune.com accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

SEO Factors

mobile.chicagotribune.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

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: