2.1 sec in total
32 ms
1.2 sec
844 ms
Welcome to chicagotribune.com homepage info - get ready to check Chicago Tribune best content for United States right away, or after learning these important things about chicagotribune.com
Get Chicago and Illinois news from The Chicago Tribune
Visit chicagotribune.comWe analyzed Chicagotribune.com page load time and found that the first response time was 32 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
chicagotribune.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value27.5 s
0/100
25%
Value22.5 s
0/100
10%
Value20,670 ms
0/100
30%
Value0.025
100/100
15%
Value57.2 s
0/100
10%
32 ms
10 ms
21 ms
21 ms
10 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Chicagotribune.com, 17% (12 requests) were made to Optimized-by.rubiconproject.com and 16% (11 requests) were made to Trbimg.com. The less responsive or slowest element that took the longest time to load (484 ms) relates to the external source Ads.rubiconproject.com.
Page size can be reduced by 1.8 MB (73%)
2.5 MB
666.6 kB
In fact, the total size of 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 264.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. This page needs HTML code to be minified as it can gain 52.8 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 264.4 kB or 89% of the original size.
Potential reduce by 10.2 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. Chicago Tribune images are well optimized though.
Potential reduce by 969.9 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 969.9 kB or 69% of the original size.
Potential reduce by 594.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. Chicagotribune.com needs all CSS files to be minified and compressed as it can save up to 594.4 kB or 85% of the original size.
Number of requests can be reduced by 25 (42%)
59
34
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.chicagotribune.com
32 ms
gpt.js
10 ms
lib.1q2w3_a336844d459af52a8dd3aaca105a0f7f.min.js
21 ms
main.1q2w3_79e8745a317b07cacdd462cbabd1207f.min.js
21 ms
chingux.min.js
10 ms
ctcngux.min.js
9 ms
main.1q2w3_919ab6ab527e8d7a2ae9b3786819a73b.min.css
10 ms
fonts.1q2w3_232453b090bae07860887d948fe32b10.min.css
18 ms
modules.1q2w3_b3cf596c46c0fdb9ee33b88e4c16b261.min.css
18 ms
css
59 ms
pubads_impl_81.js
53 ms
7476.js
484 ms
100x36
471 ms
gigya.js
317 ms
ngux-barkers-0.0.6.css
266 ms
jquery.min.js
265 ms
underscore-1.4.3-min.js
400 ms
bootstrap.carousel.min.js
403 ms
trb-polar.js
171 ms
450x253
136 ms
100x100
137 ms
100x100
137 ms
100x100
136 ms
100x100
136 ms
100x100
136 ms
100x56
141 ms
100x56
140 ms
150x84
140 ms
150x84
141 ms
analytics.js
130 ms
chartbeat.js
132 ms
container.html
119 ms
596.png
142 ms
4IDggkCGwIggiwCRoJQgnSChwKZAqsCsoLDgseC1wL0AvoDL4OiA6gDroAAAABAAAARgE2AAgAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEABwAAAAEAAAAAAAIABwBgAAEAAAAAAAMABwA2AAEAAAAAAAQABwB1AAEAAAAAAAUACwAVAAEAAAAAAAYABwBLAAEAAAAAAAoAGgCKAAMAAQQJAAEADgAHAAMAAQQJAAIADgBnAAMAAQQJAAMADgA9AAMAAQQJAAQADgB8AAMAAQQJAAUAFgAgAAMAAQQJAAYADgBSAAMAAQQJAAoANACkaWNvbW9vbgBpAGMAbwBtAG8AbwBuVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwaWNvbW9vbgBpAGMAbwBtAG8AbwBuaWNvbW9vbgBpAGMAbwBtAG8AbwBuUmVndWxhcgBSAGUAZwB1AGwAYQByaWNvbW9vbgBpAGMAbwBtAG8AbwBuRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
51 ms
oXhmH7eb3RbT0AB9gSCgAAAVMy9EEAAA==
51 ms
controltag
131 ms
fastlane.json
180 ms
fastlane.json
112 ms
fastlane.json
170 ms
fastlane.json
166 ms
fastlane.json
167 ms
fastlane.json
166 ms
fastlane.json
221 ms
fastlane.json
313 ms
fastlane.json
250 ms
fastlane.json
246 ms
fastlane.json
248 ms
fastlane.json
374 ms
sp.gz.js
80 ms
1-1x1.gif
69 ms
collect
49 ms
plugin.js
58 ms
ping
46 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
74 ms
i
64 ms
index.jsonp
159 ms
belizio-narrow-bold.woff
50 ms
wt
46 ms
ads
38 ms
cookie2json
13 ms
r2
6 ms
wt
51 ms
dfa98f7a4931450e9cd07f94e56afcc0
10 ms
wt
36 ms
wt
48 ms
5669d4360f43afc453484d83
30 ms
ads
109 ms
tXSgPxDl7Lk8Zr_5qX8FIfqJSHIsY8pKqTgTouATXAk.ttf
22 ms
efd6FGWWGX5Z3ztwLBrG9VBI1aZvkJLeFEwcwXkBYq0.ttf
23 ms
LAiconsA.woff
68 ms
chicagotribune.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
chicagotribune.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
chicagotribune.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
chicagotribune.com
Open Graph description is not detected on the main page of 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: