chicago.com

chicago.com is SSL secured

Free website and domain report on chicago.com

Last Updated: 16th November, 2020 Update Now
Overview

Snoop Summary for chicago.com

This is a free and comprehensive report about chicago.com. The domain chicago.com is currently hosted on a server located in United States with the IP address 151.101.194.159, where the local currency is USD and English is the local language. If chicago.com was to be sold it would possibly be worth $732 USD (based on the daily revenue potential of the website over a 24 month period). Chicago.com is somewhat popular with an estimated 347 daily unique visitors. This report was last updated 16th November, 2020.

About chicago.com

Site Preview: chicago.com chicago.com
Title: Chicago.com – More good stuff to come
Description: Comprehensive guide to the city of Chicago including hotels, real estate, tickets and events.
Keywords and Tags: chicago, illinois, localities, north america, popular, regional, tourism, travel, travel guides, united states
Related Terms: capgemini chicago, chicago dj, chicago footnotes, chicago pd, chicago pd s04e08, chicago skyscraperpage, chicago steakhouses
Fav Icon:
Age: Over 28 years old
Domain Created: 29th March, 1995
Domain Updated: 7th July, 2017
Domain Expires: 30th March, 2024
Review

Snoop Score

2/5

Valuation

$732 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,800,974
Alexa Reach: <0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 347
Monthly Visitors: 10,562
Yearly Visitors: 126,655
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $30 USD
Yearly Revenue: $361 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: chicago.com 11
Domain Name: chicago 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.02 seconds
Load Time Comparison: Faster than 74% of sites

PageSpeed Insights

Avg. (All Categories) 83
Performance 96
Accessibility 98
Best Practices 79
SEO 100
Progressive Web App 44
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
96

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for chicago.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 100 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.025
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive chicago.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://chicago.com/
0
85.936000104994
600
0
301
text/html
https://chicago.com/
86.339000146836
223.28000003472
7762
22781
200
text/html
Document
https://chicago.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.2
237.8730000928
279.45600007661
9939
53907
200
text/css
Stylesheet
https://chicago.com/wp-includes/css/dist/block-library/theme.min.css?ver=5.5.2
238.01400000229
254.45500016212
1481
2218
200
text/css
Stylesheet
https://chicago.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.2.2
238.14400006086
319.53700003214
1475
1920
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Noto+Sans%3A400italic%2C700italic%2C400%2C700%7CNoto+Serif%3A400italic%2C700italic%2C400%2C700%7CInconsolata%3A400%2C700&subset=latin%2Clatin-ext&display=fallback
238.36000007577
256.30800006911
2312
25441
200
text/css
Stylesheet
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
238.65499999374
317.81000015326
17408
27728
200
text/css
Stylesheet
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
239.05299999751
344.05199997127
18204
105197
200
text/css
Stylesheet
https://chicago.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20190102
239.26199995913
315.53600006737
3051
12709
200
text/css
Stylesheet
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
239.42500003614
305.97300012596
37859
96873
200
application/javascript
Script
https://www.google.com/recaptcha/api.js
239.63600001298
245.80200016499
1236
850
200
text/javascript
Script
https://chicago.com/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.2.2
239.86500012688
456.69599995017
5014
14105
200
application/javascript
Script
https://chicago.com/wp-content/themes/twentyfifteen/js/skip-link-focus-fix.js?ver=20141028
240.17200013623
298.20400010794
1179
753
200
application/javascript
Script
https://chicago.com/wp-content/themes/twentyfifteen/js/functions.js?ver=20171218
240.2890000958
306.68999999762
2438
4612
200
application/javascript
Script
https://chicago.com/wp-includes/js/wp-embed.min.js?ver=5.5.2
240.81999994814
300.84199993871
1504
1434
200
application/javascript
Script
https://chicago.com/wp-includes/js/wp-emoji-release.min.js?ver=5.5.2
345.63699993305
363.17300004885
5827
14246
200
application/javascript
Script
https://fonts.gstatic.com/s/notosans/v11/o-0NIpQlx3QUlC5A4PNjXhFVZNyBx2pqPA.woff2
376.97500013746
380.05700008944
10683
10116
200
font/woff2
Font
https://fonts.gstatic.com/s/notosans/v11/o-0IIpQlx3QUlC5A4PNr5TRASf6M7Q.woff2
377.65000015497
381.25700014643
10858
10292
200
font/woff2
Font
https://fonts.gstatic.com/s/notoserif/v9/ga6Iaw1J5X9T9RW6j9bNfFcWaDq8fMU.woff2
378.75599996187
381.66499999352
13761
13192
200
font/woff2
Font
https://fonts.gstatic.com/s/notoserif/v9/ga6Law1J5X9T9RW6j9bNdOwzfReece9LOoc.woff2
379.51500015333
382.4640000239
14225
13660
200
font/woff2
Font
https://www.chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
389.94300016202
526.44899999723
628
0
301
text/html
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
391.93799998611
402.44400012307
134118
342600
200
text/javascript
Script
https://usage.cct.org/piwik.js
392.29100011289
422.11899999529
0
0
-1
Script
486.22400010936
525.41100000963
14360
14360
200
application/font-woff
Font
https://chicago.com/wp-content/plugins/contact-form-7/images/ajax-loader.gif
508.50900006481
524.98200000264
1438
847
200
image/gif
Image
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=raclo9apa2ga
521.88999997452
610.08800007403
12138
21913
200
text/html
Document
https://chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
527.66300016083
623.46699996851
7500
6902
200
image/gif
Image
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
624.01599995792
637.40699994378
26064
51104
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
624.28300012834
639.20600013807
134118
342600
200
text/javascript
Script
694.93800005876
695.12400007807
0
14613
200
image/png
Image
695.93199994415
695.98000007682
0
1725
200
image/png
Image
https://www.gstatic.com/recaptcha/api2/logo_48.png
696.94399996661
699.714000104
2781
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
698.4020001255
701.25399995595
11315
10748
200
font/woff2
Font
https://www.google.com/js/bg/y1-OJJtZ3LPr1iATWTEwePQ2hSzGt4PIJEhvarT0gRw.js
716.72100014985
720.01800010912
6749
14147
200
text/javascript
Script
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc
736.27400002442
742.22000013106
850
102
200
text/javascript
Other
https://www.google.com/recaptcha/api2/bframe?hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&cb=pp4wp78q3ssj
850.02100002021
934.46200015023
2007
8033
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
945.71799994446
945.83999994211
26064
51104
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
945.95100008883
946.03300001472
134118
342600
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
1011.1269999761
1011.2010000739
11315
10748
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
253.822
9.147
265.104
34.322
377.876
18.146
396.035
21.923
428.524
10.851
465.974
28.082
494.998
56.338
555.225
11.082
640.549
7.876
690.294
65.523
755.856
5.201
767.542
45.712
813.326
22.058
835.463
6.877
843.115
25.275
870.098
7.338
880.903
11.957
893.168
12.42
909.832
11.607
929.169
5.745
934.931
5.693
964.855
6.325
973.585
64.421
1044.154
9.878
1076.463
12.259
1327.043
12.835
1340.241
9.164
1527.551
39.449
1577.733
101.739
1779.732
109.951
1890.94
10.643
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Chicago.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Chicago.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Chicago.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18204
3477
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Chicago.com should consider minifying JS files.
Remove unused CSS — Potential savings of 57 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Chicago.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
26064
26050
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
17408
17408
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18204
14619
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 140 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://chicago.com/
137.936
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Chicago.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://chicago.com/
190
https://chicago.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Chicago.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 662 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
37859
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
26064
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
26064
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18204
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
17408
https://fonts.gstatic.com/s/notoserif/v9/ga6Law1J5X9T9RW6j9bNdOwzfReece9LOoc.woff2
14225
https://fonts.gstatic.com/s/notoserif/v9/ga6Iaw1J5X9T9RW6j9bNfFcWaDq8fMU.woff2
13761
Uses efficient cache policy on static assets — 15 resources found
Chicago.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/api2/logo_48.png
604800000
2781
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
2592000000
37859
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
2592000000
18204
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
2592000000
17408
https://chicago.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.2
2592000000
9939
https://chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
2592000000
7500
https://chicago.com/wp-includes/js/wp-emoji-release.min.js?ver=5.5.2
2592000000
5827
https://chicago.com/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.2.2
2592000000
5014
https://chicago.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20190102
2592000000
3051
https://chicago.com/wp-content/themes/twentyfifteen/js/functions.js?ver=20171218
2592000000
2438
https://chicago.com/wp-includes/js/wp-embed.min.js?ver=5.5.2
2592000000
1504
https://chicago.com/wp-includes/css/dist/block-library/theme.min.css?ver=5.5.2
2592000000
1481
https://chicago.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.2.2
2592000000
1475
https://chicago.com/wp-content/plugins/contact-form-7/images/ajax-loader.gif
2592000000
1438
https://chicago.com/wp-content/themes/twentyfifteen/js/skip-link-focus-fix.js?ver=20141028
2592000000
1179
Avoids an excessive DOM size — 112 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
112
Maximum DOM Depth
13
Maximum Child Elements
8
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Chicago.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=raclo9apa2ga
419.605
398.468
1.791
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
211.032
148.555
47.07
https://chicago.com/
95.123
35.379
2.073
Unattributable
57.947
2.324
0.152
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
662.334
Other
79.838
Script Parsing & Compilation
58.53
Style & Layout
53.906
Parse HTML & CSS
24.177
Garbage Collection
16.243
Rendering
12.243
Keep request counts low and transfer sizes small — 36 requests • 662 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
36
678019
Script
12
464160
Stylesheet
9
105998
Font
6
72157
Document
3
21907
Image
3
11719
Other
3
2078
Media
0
0
Third-party
19
554712
Minimize third-party usage — Third-party code blocked the main thread for 110 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
22980
110.698
457263
0
74469
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0067047837508059
0.0061886952323607
 
0.0044936316627742
0.0040440557457515
0.0039943392557993
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=raclo9apa2ga
1483
110
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=raclo9apa2ga
1381
102
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
1190
66
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
640
64
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Eliminate render-blocking resources — Potential savings of 440 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Chicago.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://chicago.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.2
9939
110
https://chicago.com/wp-includes/css/dist/block-library/theme.min.css?ver=5.5.2
1481
150
https://chicago.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.2.2
1475
150
https://fonts.googleapis.com/css?family=Noto+Sans%3A400italic%2C700italic%2C400%2C700%7CNoto+Serif%3A400italic%2C700italic%2C400%2C700%7CInconsolata%3A400%2C700&subset=latin%2Clatin-ext&display=fallback
2312
230
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
17408
230
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18204
230
https://chicago.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20190102
3051
150
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
37859
230
Remove unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
75705

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.8519998304546
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
0.074000097811222
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of chicago.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Chicago.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Chicago.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
79

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that chicago.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
WordPress
5.5.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://chicago.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://usage.cct.org/piwik.js
Failed to load resource: net::ERR_CONNECTION_FAILED
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for chicago.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of chicago.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
44

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of chicago.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of chicago.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://chicago.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 73
Performance 48
Accessibility 98
Best Practices 71
SEO 100
Progressive Web App 46
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
48

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for chicago.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 3.2 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.028
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Chicago.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Chicago.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Chicago.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18202
3477
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Chicago.com should consider minifying JS files.
Remove unused CSS — Potential savings of 59 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Chicago.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
26064
26050
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
17408
17408
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18202
16990
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 20 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://chicago.com/
19.104
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Chicago.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://chicago.com/
630
https://chicago.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Chicago.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 652 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
37858
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
26064
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
26064
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18202
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
17408
https://fonts.gstatic.com/s/notoserif/v9/ga6Law1J5X9T9RW6j9bNdOwzfReece9LOoc.woff2
14225
https://fonts.gstatic.com/s/notoserif/v9/ga6Iaw1J5X9T9RW6j9bNfFcWaDq8fMU.woff2
13761
Uses efficient cache policy on static assets — 15 resources found
Chicago.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/api2/logo_48.png
604800000
2781
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
2592000000
37858
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
2592000000
18202
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
2592000000
17408
https://chicago.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.2
2592000000
9940
https://chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
2592000000
7498
https://chicago.com/wp-includes/js/wp-emoji-release.min.js?ver=5.5.2
2592000000
5827
https://chicago.com/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.2.2
2592000000
5011
https://chicago.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20190102
2592000000
3050
https://chicago.com/wp-content/themes/twentyfifteen/js/functions.js?ver=20171218
2592000000
2439
https://chicago.com/wp-includes/js/wp-embed.min.js?ver=5.5.2
2592000000
1504
https://chicago.com/wp-includes/css/dist/block-library/theme.min.css?ver=5.5.2
2592000000
1482
https://chicago.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.2.2
2592000000
1475
https://chicago.com/wp-content/plugins/contact-form-7/images/ajax-loader.gif
2592000000
1438
https://chicago.com/wp-content/themes/twentyfifteen/js/skip-link-focus-fix.js?ver=20141028
2592000000
1179
Avoids an excessive DOM size — 110 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
110
Maximum DOM Depth
13
Maximum Child Elements
8
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Chicago.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 35 requests • 652 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
35
667290
Script
12
464239
Stylesheet
9
105985
Font
5
61302
Document
3
22016
Image
3
11717
Other
3
2031
Media
0
0
Third-party
18
544026
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.015621082808016
0.003781973687484
0.002884717518662
0.0026934989908803
0.0025291029715204
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 13 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=v3dfh46b6kvj
6194
387
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=v3dfh46b6kvj
5828
366
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
4650
297
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
2070
237
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
5440
188
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
5272
168
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=v3dfh46b6kvj
5685
143
https://chicago.com/
1110
137
https://www.google.com/js/bg/y1-OJJtZ3LPr1iATWTEwePQ2hSzGt4PIJEhvarT0gRw.js
7140
97
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
4947
89
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
3870
72
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=v3dfh46b6kvj
5628
57
https://chicago.com/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.2.2
4590
51
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://chicago.com/
0
16.056000022218
588
0
301
text/html
https://chicago.com/
16.505000181496
34.611000213772
7761
22781
200
text/html
Document
https://chicago.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.2
50.251000095159
75.005999999121
9940
53907
200
text/css
Stylesheet
https://chicago.com/wp-includes/css/dist/block-library/theme.min.css?ver=5.5.2
50.398000050336
66.74600020051
1482
2218
200
text/css
Stylesheet
https://chicago.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.2.2
50.943000009283
68.713000044227
1475
1920
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Noto+Sans%3A400italic%2C700italic%2C400%2C700%7CNoto+Serif%3A400italic%2C700italic%2C400%2C700%7CInconsolata%3A400%2C700&subset=latin%2Clatin-ext&display=fallback
51.170000107959
65.080000087619
2300
25441
200
text/css
Stylesheet
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
51.373000023887
72.655000025406
17408
27728
200
text/css
Stylesheet
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
51.875000121072
116.14500009455
18202
105197
200
text/css
Stylesheet
https://chicago.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20190102
52.149000111967
71.317000081763
3050
12709
200
text/css
Stylesheet
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
52.484000101686
125.52800006233
37858
96873
200
application/javascript
Script
https://www.google.com/recaptcha/api.js
52.733000135049
59.009000193328
1318
850
200
text/javascript
Script
https://chicago.com/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.2.2
52.886000135913
70.885000051931
5011
14105
200
application/javascript
Script
https://chicago.com/wp-content/themes/twentyfifteen/js/skip-link-focus-fix.js?ver=20141028
53.090000059456
69.555000169203
1179
753
200
application/javascript
Script
https://chicago.com/wp-content/themes/twentyfifteen/js/functions.js?ver=20171218
53.367000073195
74.599000159651
2439
4612
200
application/javascript
Script
https://chicago.com/wp-includes/js/wp-embed.min.js?ver=5.5.2
53.588000126183
118.09700005688
1504
1434
200
application/javascript
Script
https://chicago.com/wp-includes/js/wp-emoji-release.min.js?ver=5.5.2
122.68300005235
139.14200011641
5827
14246
200
application/javascript
Script
https://fonts.gstatic.com/s/notosans/v11/o-0NIpQlx3QUlC5A4PNjXhFVZNyBx2pqPA.woff2
159.14300014265
163.02400012501
10682
10116
200
font/woff2
Font
https://fonts.gstatic.com/s/notoserif/v9/ga6Law1J5X9T9RW6j9bNdOwzfReece9LOoc.woff2
160.1410000585
163.42900018208
14225
13660
200
font/woff2
Font
https://fonts.gstatic.com/s/notoserif/v9/ga6Iaw1J5X9T9RW6j9bNfFcWaDq8fMU.woff2
161.12900013104
165.92600010335
13761
13192
200
font/woff2
Font
163.46300020814
179.30100020021
14360
14360
200
application/font-woff
Font
https://www.chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
173.98900003172
224.27200013772
604
0
301
text/html
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
176.27300019376
188.04900022224
134118
342600
200
text/javascript
Script
https://usage.cct.org/piwik.js
176.67600000277
218.48300006241
0
0
-1
Script
https://chicago.com/wp-content/plugins/contact-form-7/images/ajax-loader.gif
218.27600011602
234.34800002724
1438
847
200
image/gif
Image
https://chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
224.73100014031
244.36400015838
7498
6902
200
image/gif
Image
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=v3dfh46b6kvj
281.02100011893
331.97400020435
12235
21941
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
346.16700001061
354.63600000367
26064
51104
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
346.38500004075
356.90500005148
134118
342600
200
text/javascript
Script
421.38000018895
421.62300017662
0
14613
200
image/png
Image
422.74700012058
422.80700011179
0
1725
200
image/png
Image
https://www.gstatic.com/recaptcha/api2/logo_48.png
423.92000020482
426.59900011495
2781
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
426.41200008802
429.37500006519
11317
10748
200
font/woff2
Font
https://www.google.com/js/bg/y1-OJJtZ3LPr1iATWTEwePQ2hSzGt4PIJEhvarT0gRw.js
447.98000017181
450.9810002055
6749
14147
200
text/javascript
Script
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc
467.2230000142
476.15500004031
839
102
200
text/javascript
Other
https://www.google.com/recaptcha/api2/bframe?hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&cb=9ztj68dx8yah
578.88800022192
626.44900009036
2020
8565
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/styles__ltr.css
639.34200000949
639.42200015299
26064
51104
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
639.5050000865
639.5780001767
134118
342600
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
699.82400001027
699.92300006561
11317
10748
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
63.953
9.748
76.158
34.232
159.92
17.881
177.814
23.34
210.533
8.677
219.585
25.744
251.501
7.602
267.032
41.948
362.139
8.096
411.71
74.179
485.913
5.364
498.156
47.117
545.341
24.282
569.738
5.335
575.934
22.244
599.561
5.54
613.928
12.111
626.099
5.375
631.529
11.857
645.782
11.644
657.442
6.669
666.204
59.358
745.874
11.41
812.514
12.114
954.608
14.292
969.525
7.678
1154.7
35.752
1190.589
91.459
1363.526
96.75
1460.347
9.889
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 3.2 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 7.2 s
The time taken for the page to become fully interactive.

Other

First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.

Diagnostics

Reduce JavaScript execution time — 2.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&co=aHR0cHM6Ly9jaGljYWdvLmNvbTo0NDM.&hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&size=normal&cb=v3dfh46b6kvj
1614.496
1534.704
7.92
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
800.34
556.048
177.316
https://chicago.com/
359.248
127.384
9.164
Unattributable
220.824
9.544
0.904
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
127.944
113.804
6.192
https://www.google.com/recaptcha/api2/bframe?hl=en&v=rCr6uVkhcBxHr-Uhry4bcSYc&k=6LcV1BAUAAAAAJne2b_IyBstcJNiZ2qWeVH9J8wc&cb=9ztj68dx8yah
96.68
51.084
5.312
https://www.google.com/js/bg/y1-OJJtZ3LPr1iATWTEwePQ2hSzGt4PIJEhvarT0gRw.js
87.184
78.544
7.376
https://chicago.com/wp-content/themes/twentyfifteen/js/functions.js?ver=20171218
61.24
47.94
1.256
Minimize main-thread work — 3.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2536.456
Other
309.368
Script Parsing & Compilation
224.516
Style & Layout
197.74
Parse HTML & CSS
95.688
Garbage Collection
60.68
Rendering
35.296

Metrics

Largest Contentful Paint — 4.6 s
The timing of the largest text or image that is painted.
Total Blocking Time — 1,340 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 7.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 390 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 160 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive chicago.com as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 6381 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,600 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Chicago.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://chicago.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.2
9940
630
https://chicago.com/wp-includes/css/dist/block-library/theme.min.css?ver=5.5.2
1482
480
https://chicago.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.2.2
1475
480
https://fonts.googleapis.com/css?family=Noto+Sans%3A400italic%2C700italic%2C400%2C700%7CNoto+Serif%3A400italic%2C700italic%2C400%2C700%7CInconsolata%3A400%2C700&subset=latin%2Clatin-ext&display=fallback
2300
780
https://chicago.com/wp-content/themes/twentyfifteen/genericons/genericons.css?ver=3.2
17408
1080
https://chicago.com/wp-content/themes/twentyfifteen/style.css?ver=20190507
18202
1080
https://chicago.com/wp-content/themes/twentyfifteen/css/blocks.css?ver=20190102
3050
630
https://chicago.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
37858
1080
Remove unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
134118
75860

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.9629999771714
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
0.099000055342913
Reduce the impact of third-party code — Third-party code blocked the main thread for 1,070 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
23161
857.908
457263
209.668
63602
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://www.gstatic.com/recaptcha/releases/rCr6uVkhcBxHr-Uhry4bcSYc/recaptcha__en.js
line: 215
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of chicago.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Chicago.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Chicago.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
71

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that chicago.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
WordPress
5.5.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://chicago.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.chicago.com/wp-content/uploads/2017/01/TrustLogo300-300x144.gif
300 x 144
300 x 144
788 x 378

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://usage.cct.org/piwik.js
Failed to load resource: net::ERR_CONNECTION_FAILED
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for chicago.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of chicago.com on mobile screens.
Document uses legible font sizes — 98.52% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.rc-anchor-normal .rc-anchor-pt, .rc-anchor-invisible .rc-anchor-pt, .rc-anchor-compact .rc-anchor-pt
0.87%
8px
.rc-anchor-logo-text
0.61%
10px
98.52%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
46

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of chicago.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of chicago.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://chicago.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 151.101.194.159
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
FASTLY
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Network Solutions, LLC 162.159.133.53
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4.3/5
WOT Trustworthiness: 87/100
WOT Child Safety: 51/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: chicago.com
Issued By: Let's Encrypt Authority X3
Valid From: 25th September, 2020
Valid To: 24th December, 2020
Subject: CN = chicago.com
Hash: 7fca7805
Issuer: CN = Let's Encrypt Authority X3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04E05C9C4E452056DB1E3A6775DC5348E1BD
Serial Number (Hex): 04E05C9C4E452056DB1E3A6775DC5348E1BD
Valid From: 25th September, 2024
Valid To: 24th December, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://ocsp.int-x3.letsencrypt.org
CA Issuers - URI:http://cert.int-x3.letsencrypt.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
Timestamp : Sep 25 03:02:46.127 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D0:C8:4D:BB:9C:35:23:DE:91:3D:EC:
7D:CE:0D:12:CC:94:49:BE:FB:39:B3:D7:6C:32:B7:8C:
CB:A2:56:EB:85:02:20:5D:CE:D0:66:4F:93:6E:48:C0:
2C:60:98:4B:33:A6:50:01:45:7C:5A:7A:8B:C6:97:22:
1E:92:34:B3:52:C8:09
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Sep 25 03:02:46.424 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:CC:1C:D3:33:25:9D:48:5E:BC:D0:98:
5A:49:41:0D:2E:09:67:0E:0D:F8:49:31:25:C7:6F:82:
C9:6B:FC:73:9F:02:21:00:D2:A4:88:B7:24:F3:E6:42:
C4:F3:7D:90:49:71:BF:57:04:63:1B:7D:2E:10:C2:13:
B1:67:C3:18:AB:AF:1E:72
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.chicago.com
DNS:chicago.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
chicago.com. 151.101.194.159 IN 299

NS Records

Host Nameserver Class TTL
chicago.com. dns1.stabletransit.com. IN 299
chicago.com. dns2.stabletransit.com. IN 299

MX Records

Priority Host Server Class TTL
0 chicago.com. chicago-com.mail.protection.outlook.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
chicago.com. ns.rackspace.com. tpfluger.cct.org. 3599

TXT Records

Host Value Class TTL
chicago.com. MS=ms38383429 IN 3659
chicago.com. v=spf1 IN 3659

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Server: Flywheel/5.1.0
Date: 16th November, 2020
Connection: keep-alive
Content-Length: 22781
Link: <https://chicago.com/>; rel=shortlink
X-XSS-Protection: 1
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
X-FW-Server: Flywheel/5.1.0
X-FW-Dynamic: TRUE
X-FW-Hash: 5f67qglmku
X-FW-Version: 5.0.0
X-Cacheable: YES
Fastly-Restarts: 1
Accept-Ranges: bytes
X-Served-By: cache-ewr18135-EWR
X-Cache: HIT
X-Cache-Hits: 1
X-Timer: S1605541998.124634,VS0,VE1
Vary: Accept-Encoding, Accept-Encoding
X-FW-Serve: TRUE
X-FW-Static: NO
X-FW-Type: VISIT

Whois Lookup

Created: 29th March, 1995
Changed: 7th July, 2017
Expires: 30th March, 2024
Registrar: Network Solutions, LLC
Status: clientTransferProhibited
Nameservers: dns1.stabletransit.com
dns2.stabletransit.com
Owner Name: PERFECT PRIVACY, LLC
Owner Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Owner Post Code: 32256
Owner City: Jacksonville
Owner State: FL
Owner Country: US
Owner Phone: +1.5707088780
Owner Email: uy7x78k55xs@networksolutionsprivateregistration.com
Admin Name: PERFECT PRIVACY, LLC
Admin Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Admin Post Code: 32256
Admin City: Jacksonville
Admin State: FL
Admin Country: US
Admin Phone: +1.5707088780
Admin Email: uy7x78k55xs@networksolutionsprivateregistration.com
Tech Name: PERFECT PRIVACY, LLC
Tech Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Tech Post Code: 32256
Tech City: Jacksonville
Tech State: FL
Tech Country: US
Tech Phone: +1.5707088780
Tech Email: uy7x78k55xs@networksolutionsprivateregistration.com
Full Whois: Domain Name: CHICAGO.COM
Registry Domain ID: 324579_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://networksolutions.com
Updated Date: 2017-07-07T19:03:09Z
Creation Date: 1995-03-29T05:00:00Z
Registrar Registration Expiration Date: 2024-03-30T04:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: PERFECT PRIVACY, LLC
Registrant Organization:
Registrant Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Registrant City: Jacksonville
Registrant State/Province: FL
Registrant Postal Code: 32256
Registrant Country: US
Registrant Phone: +1.5707088780
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: uy7x78k55xs@networksolutionsprivateregistration.com
Registry Admin ID:
Admin Name: PERFECT PRIVACY, LLC
Admin Organization:
Admin Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Admin City: Jacksonville
Admin State/Province: FL
Admin Postal Code: 32256
Admin Country: US
Admin Phone: +1.5707088780
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: uy7x78k55xs@networksolutionsprivateregistration.com
Registry Tech ID:
Tech Name: PERFECT PRIVACY, LLC
Tech Organization:
Tech Street: 5335 Gate Parkway care of Network Solutions PO Box 459
Tech City: Jacksonville
Tech State/Province: FL
Tech Postal Code: 32256
Tech Country: US
Tech Phone: +1.5707088780
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: uy7x78k55xs@networksolutionsprivateregistration.com
Name Server: DNS1.STABLETRANSIT.COM
Name Server: DNS2.STABLETRANSIT.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-11-16T15:53:19Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en


This listing is a Network Solutions Private Registration. Mail
correspondence to this address must be sent via USPS Express Mail(TM) or
USPS Certified Mail(R); all other mail will not be processed. Be sure to
include the registrant's domain name in the address.

The data in Networksolutions.com's WHOIS database is provided to you by
Networksolutions.com for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. Networksolutions.com makes this information available "as is," and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that,
under no circumstances will you use this data to: (1) allow, enable,
or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to Networksolutions.com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of Networksolutions.com.
Networksolutions.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
dns1.stabletransit.com 69.20.95.4
dns2.stabletransit.com 65.61.188.4
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$1,021 USD 1/5
$790 USD 2/5
0/5
$1,000 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$432 USD 1/5
$6,790 USD 2/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$10,754 USD 3/5
$2,690 USD 2/5
$3,707 USD 2/5
$1,462 USD 2/5