1.7 sec in total
92 ms
638 ms
1000 ms
Click here to check amazing People 2013 Chicago Reader content for United States. Otherwise, check out these important facts you probably never knew about people2013.chicagoreader.com
What makes Chicago work? We selected 19 people—with passions like brewing beer or fixing bikes or curating performance art—to shed light on some of the city’s many moving parts.
Visit people2013.chicagoreader.comWe analyzed People2013.chicagoreader.com page load time and found that the first response time was 92 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster. This domain responded with an error, which can significantly jeopardize People2013.chicagoreader.com rating and web reputation
people2013.chicagoreader.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value5.3 s
22/100
25%
Value5.2 s
60/100
10%
Value290 ms
80/100
30%
Value0
100/100
15%
Value6.9 s
54/100
10%
92 ms
25 ms
80 ms
32 ms
86 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 77% of them (64 requests) were addressed to the original People2013.chicagoreader.com, 7% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (225 ms) belongs to the original domain People2013.chicagoreader.com.
Page size can be reduced by 613.3 kB (17%)
3.6 MB
3.0 MB
In fact, the total size of People2013.chicagoreader.com main page is 3.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 45.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 6.1 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.8 kB or 82% of the original size.
Potential reduce by 45.6 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. People 2013 Chicago Reader images are well optimized though.
Potential reduce by 299.8 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 299.8 kB or 75% of the original size.
Potential reduce by 222.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. People2013.chicagoreader.com needs all CSS files to be minified and compressed as it can save up to 222.2 kB or 89% of the original size.
Number of requests can be reduced by 43 (57%)
75
32
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of People 2013 Chicago Reader. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
people2013.chicagoreader.com
92 ms
style.css
25 ms
wpv-pagination.css
80 ms
css
32 ms
app.css
86 ms
datepicker.css
80 ms
jquery-ui-1.9.2.custom.min.css
81 ms
royalslider.css
76 ms
rs-default-inverted.css
76 ms
rs-gallery-with-text-thumbs.css
94 ms
wpv-views-sorting.css
96 ms
jquery.min.js
62 ms
wpv-pagination-embedded.js
94 ms
wpv-date-front-end-control.js
92 ms
modernizr.foundation.js
94 ms
jquery.reveal.js
122 ms
jquery.orbit-1.4.0.js
120 ms
jquery.customforms.js
124 ms
jquery.placeholder.min.js
120 ms
jquery.tooltips.js
123 ms
app.js
123 ms
off-canvas.js
145 ms
custom.js
145 ms
jquery-ui.js
7 ms
video.js
172 ms
38f013a07e0458db1ee84d020e47cac
143 ms
oasPeople2013.js
10 ms
jquery.ui.core.min.js
138 ms
jquery.ui.datepicker.min.js
138 ms
scripts.js
141 ms
jquery.royalslider.min.js
225 ms
analytics.js
7 ms
beacon.js
35 ms
collect
11 ms
collect
76 ms
collect
21 ms
collect
80 ms
thepeopleissue.png
190 ms
menu.png
195 ms
theR.png
191 ms
social3_01.png
194 ms
social3_02.png
192 ms
BackToTop2.png
195 ms
PeopleIssueHero1.jpg
202 ms
Arts-20001.jpg
199 ms
open-quotes-white.png
195 ms
blank.gif
196 ms
Food-2000.jpg
203 ms
open-quotes-black.png
197 ms
Citylife-20001.jpg
206 ms
Music-2000.jpg
201 ms
reader-logo-footer.png
197 ms
ooyala_storage.html
58 ms
ui-bg_glass_100_f6f6f6_1x400.png
59 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
60 ms
ui-icons_ef8c08_256x240.png
61 ms
ui-bg_glass_65_ffffff_1x400.png
63 ms
grab.png
61 ms
slide-lyra-CircleOnly.png
93 ms
slide-joe-CircleOnly.png
81 ms
slide-kellye-CircleOnly.png
85 ms
slide-amir-CircleOnly.png
85 ms
slide-jen-CircleOnly.png
131 ms
preloader.gif
90 ms
slider-arrows.png
92 ms
slide-julia-CircleOnly.png
93 ms
slide-afaf-CircleOnly.png
93 ms
slide-abby-CircleOnly.png
99 ms
slide-lamar-CircleOnly.png
93 ms
slide-max-CircleOnly.png
93 ms
slide-linda-CircleOnly.png
94 ms
slide-abe-CircleOnly.png
93 ms
slide-tomeka-CircleOnly.png
104 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
44 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
44 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
44 ms
xjAJXh38I15wypJXxuGMBtIh4imgI8P11RFo6YPCPC0.woff
42 ms
PRmiXeptR36kaC0GEAetxrsuoFAk0leveMLeqYtnfAY.woff
40 ms
PRmiXeptR36kaC0GEAetxmWeb5PoA5ztb49yLyUzH1A.woff
40 ms
slide-nate-CircleOnly.png
94 ms
slide-nnamdi-CircleOnly.png
81 ms
slide-mica-CircleOnly.png
80 ms
chartbeat.js
18 ms
people2013.chicagoreader.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
people2013.chicagoreader.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
people2013.chicagoreader.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise People2013.chicagoreader.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that People2013.chicagoreader.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.
people2013.chicagoreader.com
Open Graph data is detected on the main page of People 2013 Chicago Reader. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: