2.7 sec in total
35 ms
1.5 sec
1.2 sec
Click here to check amazing 360 CHICAGO content for United States. Otherwise, check out these important facts you probably never knew about 360chicago.com
Experience panoramic views of Chicago's skyline and Lake Michigan from 1,030 feet above Magnificent Mile. Visit 360 CHICAGO, a premier observation deck in the windy city.
Visit 360chicago.comWe analyzed 360chicago.com page load time and found that the first response time was 35 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
360chicago.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value9.6 s
0/100
25%
Value6.1 s
45/100
10%
Value3,480 ms
2/100
30%
Value0.006
100/100
15%
Value20.7 s
2/100
10%
35 ms
319 ms
26 ms
189 ms
233 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 88% of them (70 requests) were addressed to the original 360chicago.com, 5% (4 requests) were made to Cdn.userway.org and 1% (1 request) were made to Cdn-4.convertexperiments.com. The less responsive or slowest element that took the longest time to load (533 ms) relates to the external source Google.com.
Page size can be reduced by 458.7 kB (25%)
1.8 MB
1.4 MB
In fact, the total size of 360chicago.com main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 261.0 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 261.0 kB or 79% of the original size.
Potential reduce by 42.1 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. 360 CHICAGO images are well optimized though.
Potential reduce by 155.6 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 155.6 kB or 51% of the original size.
Number of requests can be reduced by 26 (35%)
75
49
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 360 CHICAGO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
360chicago.com
35 ms
360chicago.com
319 ms
72d23b52a0e2.google-fonts.css
26 ms
front.used.css
189 ms
jquery.min.js
233 ms
newrelic.js
40 ms
10043105-10044935.js
22 ms
316.css
194 ms
315.css
223 ms
406.css
218 ms
188.css
261 ms
23.css
275 ms
9.css
390 ms
universal.css
450 ms
swiper-bundle.min.js
18 ms
lazyload.min.js
390 ms
aos.js
340 ms
fancybox.min.js
479 ms
fancybox-init-4.js
442 ms
gtm.js
66 ms
Logo-360-Chicago-White.svg
114 ms
Logo-360-Chicago-Green.svg
128 ms
homepage-hero-desktop-1.jpg
28 ms
icon-star-white.svg
37 ms
icon-arrow-black.svg
40 ms
icon-play-button-white.svg
37 ms
icon-arrow-white.svg
39 ms
icon-arrow-circle-white-left.svg
34 ms
icon-arrow-circle-white-right.svg
37 ms
icon-checkmark.svg
15 ms
382TungstenNarrow.woff
256 ms
6378TungstenNarrow.woff
276 ms
2380TungstenNarrow.woff
274 ms
building-illustration-gray.svg
27 ms
widget.js
174 ms
icon-menu.svg
17 ms
icon-menu-black.svg
18 ms
logo-tripadvisor-white.svg
19 ms
logo-facebook-white.svg
33 ms
logo-google-white.svg
30 ms
homepage-clouds-01.png
35 ms
homepage-views-02.jpg
43 ms
homepage-views-03.jpg
59 ms
homepage-views-04.jpg
51 ms
homepage-views-05.jpg
62 ms
homepage-views-06.jpg
71 ms
homepage-views-07.jpg
74 ms
homepage-tilt-bkg-desktop.jpg
76 ms
homepage-tilt-feature.png
88 ms
homepage-clouds-02.png
93 ms
Logo-CloudBar-Black.svg
91 ms
homepage-cloudbar-01-2.jpg
108 ms
homepage-cloudbar-02-1.jpg
109 ms
homepage-cloudbar-03.jpg
107 ms
homepage-cloudbar-04.jpg
120 ms
homeapge-events-fireworks.jpg
124 ms
homeapge-events-sky-yoga.jpg
122 ms
homeapge-events-cloudwalk.jpg
138 ms
tickets-sip-tilt-view-card-3.jpg
137 ms
tickets-sip-view-card-3.jpg
139 ms
tickets-tilt-view-card.jpg
149 ms
tickets-general-admission-card.jpg
154 ms
tickets-citypass-card.jpg
153 ms
app-magnicity-360-768x512-1.jpg
161 ms
citypass-card.jpg
193 ms
groups-vertical-1.jpg
194 ms
groups-vertical-2.jpg
194 ms
groups-vertical-3.jpg
195 ms
body_wh.svg
145 ms
place
533 ms
icon-facebook-white.svg
179 ms
icon-instagram-white.svg
180 ms
icon-youtube-white.svg
187 ms
icon-x-white.svg
190 ms
icon-tiktok-white.svg
173 ms
Logo-Magnicity-White.svg
188 ms
widget_app_1721460856032.js
24 ms
HbHGU9aP7m
337 ms
en-US.json
8 ms
js
29 ms
360chicago.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
360chicago.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
360chicago.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 360chicago.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that 360chicago.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
360chicago.com
Open Graph data is detected on the main page of 360 CHICAGO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: