1.8 sec in total
56 ms
1.2 sec
574 ms
Click here to check amazing Gcfb content for United States. Otherwise, check out these important facts you probably never knew about gcfb.net
Welcome to Granite City Food & Brewery. Come in for brunch, lunch, happy hour or dinner. Enjoy the best craft beer, scratch food and Lawless Brunch in town.
Visit gcfb.netWe analyzed Gcfb.net page load time and found that the first response time was 56 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
gcfb.net performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value46.1 s
0/100
25%
Value26.8 s
0/100
10%
Value980 ms
28/100
30%
Value0.099
90/100
15%
Value31.2 s
0/100
10%
56 ms
367 ms
50 ms
71 ms
54 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gcfb.net, 67% (41 requests) were made to Gcfb.com and 20% (12 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (367 ms) relates to the external source Gcfb.com.
Page size can be reduced by 760.7 kB (35%)
2.1 MB
1.4 MB
In fact, the total size of Gcfb.net main page is 2.1 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 48.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 48.0 kB or 84% of the original size.
Potential reduce by 2.0 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. Gcfb images are well optimized though.
Potential reduce by 601.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 601.2 kB or 76% of the original size.
Potential reduce by 109.6 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. Gcfb.net needs all CSS files to be minified and compressed as it can save up to 109.6 kB or 83% of the original size.
Number of requests can be reduced by 28 (61%)
46
18
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gcfb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
gcfb.net
56 ms
www.gcfb.com
367 ms
wp-emoji-release.min.js
50 ms
styles.css
71 ms
bwg_frontend.css
54 ms
font-awesome.css
61 ms
jquery.mCustomScrollbar.css
50 ms
font-awesome.min.css
10 ms
style.css
63 ms
jquery.js
199 ms
jquery-migrate.min.js
76 ms
bwg_frontend.js
87 ms
jquery.mobile.js
85 ms
jquery.mCustomScrollbar.concat.min.js
129 ms
jquery.fullscreen-0.4.1.js
93 ms
bwg_gallery_box.js
135 ms
3DEngine.js
131 ms
Sphere.js
97 ms
guc5qqw.js
155 ms
scripts.js
122 ms
modernizr.custom.js
170 ms
jquery.ui.js
231 ms
conversion.js
14 ms
jquery.form.min.js
156 ms
scripts.js
152 ms
jquery.raty.js
229 ms
classie.js
182 ms
sidebarEffects.js
227 ms
mobile-nav.js
181 ms
combined.min.js
263 ms
1f5
129 ms
analytics.js
55 ms
BB_2016-copy-195x300.jpg
55 ms
bgHeader.jpg
46 ms
logo.jpg
46 ms
bgAlpha.jpg
177 ms
div.png
45 ms
bgParallax.jpg
178 ms
prlxOverlay.png
175 ms
bgCharlie.jpg
68 ms
mClub.png
75 ms
bgDelta.jpg
236 ms
tweetcon.jpg
177 ms
bgFox.jpg
206 ms
logoFtr.jpg
206 ms
l-MSMxIEfwLLJ7fy_UP0EyIn-KBHEtgTnrGFEphO2obffHPsgsMWeMI6MK6f5Mb.eot
30 ms
QkzV5dk_fdS_CQOrBGXMFDjyJvG0TNSSVrTqMPmy2UMff4kQgsMWeMI6MK6f5MS.eot
129 ms
fontawesome-webfont.woff
21 ms
fontawesome-webfont.woff
162 ms
HAemasxFXabfJmGdadgXczS3GTHT7-UfeZEXnyoDSGGffHPfggMWeMI6MK6f5Mb.eot
160 ms
2jJouV8i7vFJedC_pljaZyXlY5zyD0TTFpD1Ooh19V6ffHAfggMWeMI6MK6f5MS.eot
196 ms
D1vR5oxD0zl78xZeXSUAR4CmCfvnOyS7CLzHLzh3LPvffwcRgsMWeMI6MK6f5Mb.eot
196 ms
qKosTcGsDKMpJu95MfH7TJjZYk9NWgFzwlYTqw1qSkwffwKRgsMWeMI6MK6f5MS.eot
197 ms
mM7aTAUPqQ81W_f6fhp9fZNRsJLDznpcrKWjIj00sbXffVEgggMWeMI6MK6f5Mw.eot
196 ms
122 ms
collect
22 ms
99 ms
7hcYKMQHY3-yb3NROf2mf8PlSjom6y3wEbPugPJjNjGffJxjMUMWeMI6MK6f5MI.eot
52 ms
M61aAJHnvdeI3oK3kKv0jX0uNIJ5CqtA40gultdvcK6ffH-fggMWeMI6MK6f5Mq.eot
60 ms
3_ao6QnM67fFKxfrdUgz5JHDTsPLIwASiczdCO-ucAJffH-sgsMWeMI6MK6f5Mj.eot
91 ms
slider-promo-greatwolf1.jpg
60 ms
gcfb.net 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
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.
gcfb.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
gcfb.net SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gcfb.net 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 Gcfb.net 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.
gcfb.net
Open Graph description is not detected on the main page of Gcfb. 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: