Tools & Wizards About Us
chicago.bcg.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

chicago.bcg.com

Contact Us | Chicago, Illinois | BCG

Page Load Speed

1.1 sec in total

First Response

74 ms

Resources Loaded

875 ms

Page Rendered

189 ms

chicago.bcg.com screenshot

About Website

Visit chicago.bcg.com now to see the best up-to-date Chicago BCG content for India and also check out these interesting facts you probably never knew about chicago.bcg.com

Find directions, telephone numbers, and meet key contacts for BCG's Chicago office.

Visit chicago.bcg.com

Key Findings

We analyzed Chicago.bcg.com page load time and found that the first response time was 74 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

chicago.bcg.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value22,220 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value40.4 s

0/100

10%

Network Requests Diagram

chicago.bcg.com

74 ms

styles557.css

217 ms

menu557.css

419 ms

bcgdotcom557.css

335 ms

local557.css

70 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 94% of them (29 requests) were addressed to the original Chicago.bcg.com, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (419 ms) belongs to the original domain Chicago.bcg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.8 kB (67%)

Content Size

894.9 kB

After Optimization

299.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chicago.bcg.com main page is 894.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 674.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 14.8 kB

  • Original 20.1 kB
  • After minification 16.8 kB
  • After compression 5.3 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 3.3 kB, which is 17% 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 14.8 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 5.1 kB

  • Original 62.0 kB
  • After minification 56.8 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. Chicago BCG images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 459.8 kB

  • Original 674.6 kB
  • After minification 664.6 kB
  • After compression 214.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 459.8 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 116.1 kB

  • Original 138.3 kB
  • After minification 115.2 kB
  • After compression 22.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. Chicago.bcg.com needs all CSS files to be minified and compressed as it can save up to 116.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (29%)

Requests Now

28

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chicago BCG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

chicago.bcg.com

chicago.bcg.com

74 ms

styles557.css

styles557.css

217 ms

menu557.css

menu557.css

419 ms

bcgdotcom557.css

bcgdotcom557.css

335 ms

local557.css

local557.css

70 ms

colorbox557.css

colorbox557.css

72 ms

bcgdotcomscript_min31061.js

bcgdotcomscript_min31061.js

108 ms

AC_RunActiveContent16822.js

AC_RunActiveContent16822.js

72 ms

WebResource.axd

WebResource.axd

102 ms

analytics.js

analytics.js

74 ms

major_bg_vert.jpg

major_bg_vert.jpg

202 ms

file13033.gif

file13033.gif

15 ms

file11683.png

file11683.png

12 ms

file153145.png

file153145.png

11 ms

file153888.png

file153888.png

12 ms

logo_final.gif

logo_final.gif

62 ms

Chicago_Sprite.gif

Chicago_Sprite.gif

128 ms

content_top_bar.gif

content_top_bar.gif

192 ms

content_bg.gif

content_bg.gif

117 ms

bullet_off.gif

bullet_off.gif

59 ms

sprite_general.gif

sprite_general.gif

191 ms

vertical_form_bg.png

vertical_form_bg.png

179 ms

content_bottom_bar.gif

content_bottom_bar.gif

169 ms

collect

collect

31 ms

colorbox_controls.png

colorbox_controls.png

49 ms

colorbox_border.png

colorbox_border.png

183 ms

colorbox_loading_background.png

colorbox_loading_background.png

108 ms

colorbox_loading.gif

colorbox_loading.gif

240 ms

bcghenserifhead-webfont.woff

bcghenserifhead-webfont.woff

133 ms

bcghensansbold-webfont.woff

bcghensansbold-webfont.woff

135 ms

print557.css

print557.css

6 ms

Accessibility Review

chicago.bcg.com accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

chicago.bcg.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

chicago.bcg.com SEO score

82

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chicago.bcg.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 Chicago.bcg.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

chicago.bcg.com

Open Graph description is not detected on the main page of Chicago BCG. 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: