Tools & Wizards About Us
312chicago.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

312chicago.com

312 Chicago - 312 Chicago

Page Load Speed

21 sec in total

First Response

37 ms

Resources Loaded

20.4 sec

Page Rendered

598 ms

312chicago.com screenshot

About Website

Welcome to 312chicago.com homepage info - get ready to check 312 Chicago best content for United States right away, or after learning these important things about 312chicago.com

Visit 312chicago.com

Key Findings

We analyzed 312chicago.com page load time and found that the first response time was 37 ms and then it took 21 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

312chicago.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

312chicago.com

37 ms

312chicago.com

50 ms

style.min.css

9 ms

css

49 ms

pum-site-styles.css

15 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 37% of them (23 requests) were addressed to the original 312chicago.com, 38% (24 requests) were made to Fonts.gstatic.com and 11% (7 requests) were made to Live-312-chicago.pantheonsite.io. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Opentable.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.1 kB (5%)

Content Size

3.8 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 312chicago.com main page is 3.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. 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 41.8 kB

  • Original 52.5 kB
  • After minification 50.3 kB
  • After compression 10.7 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 41.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 47.9 kB

  • Original 3.4 MB
  • After minification 3.4 MB

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. 312 Chicago images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 50.8 kB

  • Original 244.0 kB
  • After minification 244.0 kB
  • After compression 193.2 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 50.8 kB or 21% of the original size.

CSS Optimization

-27%

Potential reduce by 33.6 kB

  • Original 125.0 kB
  • After minification 124.8 kB
  • After compression 91.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 312chicago.com needs all CSS files to be minified and compressed as it can save up to 33.6 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (65%)

Requests Now

31

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 312 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 10 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

312chicago.com

312chicago.com

37 ms

312chicago.com

312chicago.com

50 ms

style.min.css

style.min.css

9 ms

css

css

49 ms

pum-site-styles.css

pum-site-styles.css

15 ms

style-static.min.css

style-static.min.css

19 ms

style.css

style.css

17 ms

jquery.min.js

jquery.min.js

19 ms

jquery-migrate.min.js

jquery-migrate.min.js

18 ms

multistep-admin.min.js

multistep-admin.min.js

43 ms

css2

css2

64 ms

jvz8obn.css

jvz8obn.css

118 ms

et-core-unified-tb-43-tb-68-32.min.css

et-core-unified-tb-43-tb-68-32.min.css

49 ms

et-core-unified-32.min.css

et-core-unified-32.min.css

44 ms

et-core-unified-tb-43-tb-68-deferred-32.min.css

et-core-unified-tb-43-tb-68-deferred-32.min.css

48 ms

loader

loader

20213 ms

scripts.min.js

scripts.min.js

48 ms

frontend-bundle.min.js

frontend-bundle.min.js

47 ms

core.min.js

core.min.js

47 ms

pum-site-scripts.js

pum-site-scripts.js

47 ms

common.js

common.js

53 ms

jquery.fitvids.js

jquery.fitvids.js

54 ms

sticky-elements.js

sticky-elements.js

57 ms

css

css

50 ms

312-Chicago-Logo.png

312-Chicago-Logo.png

44 ms

home-dining-room-square.jpg

home-dining-room-square.jpg

82 ms

home-private-table-square.jpg

home-private-table-square.jpg

78 ms

home-dining-room-view-square.jpg

home-dining-room-view-square.jpg

76 ms

p.css

p.css

79 ms

DSC08742.jpg

DSC08742.jpg

23 ms

homepage-events-specials.jpg

homepage-events-specials.jpg

19 ms

DSC08671.jpg

DSC08671.jpg

10 ms

subscribe-loader.gif

subscribe-loader.gif

7 ms

homepage-private-dining.jpg

homepage-private-dining.jpg

8 ms

S6uyw4BMUTPHvxk.ttf

S6uyw4BMUTPHvxk.ttf

17 ms

S6u9w4BMUTPHh7USew8.ttf

S6u9w4BMUTPHh7USew8.ttf

24 ms

S6u8w4BMUTPHh30wWw.ttf

S6u8w4BMUTPHh30wWw.ttf

68 ms

S6u9w4BMUTPHh6UVew8.ttf

S6u9w4BMUTPHh6UVew8.ttf

69 ms

S6u9w4BMUTPHh50Xew8.ttf

S6u9w4BMUTPHh50Xew8.ttf

69 ms

MADE-Cannes.otf

MADE-Cannes.otf

16 ms

92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf

15 ms

92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf

13 ms

92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf

15 ms

92zPtBhPNqw79Ij1E865zBUv7mwjJQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mwjJQVG.ttf

15 ms

92zPtBhPNqw79Ij1E865zBUv7myjJAVG.ttf

92zPtBhPNqw79Ij1E865zBUv7myjJAVG.ttf

36 ms

92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf

36 ms

92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf

34 ms

92zPtBhPNqw79Ij1E865zBUv7mwjIgVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mwjIgVG.ttf

36 ms

92zPtBhPNqw79Ij1E865zBUv7mwKIgVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mwKIgVG.ttf

36 ms

d

d

15 ms

d

d

15 ms

d

d

33 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

34 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

36 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

36 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

37 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

37 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

38 ms

modules.woff

modules.woff

14 ms

Accessibility Review

312chicago.com accessibility score

80

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

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

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

312chicago.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

312chicago.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 312chicago.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 312chicago.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

312chicago.com

Open Graph description is not detected on the main page of 312 Chicago. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: