Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

chicago.score.org

Chicago | SCORE

Page Load Speed

1.9 sec in total

First Response

11 ms

Resources Loaded

1.5 sec

Page Rendered

399 ms

About Website

Visit chicago.score.org now to see the best up-to-date Chicago SCORE content for United States and also check out these interesting facts you probably never knew about chicago.score.org

SCORE Chicago offers FREE business advice, small business workshops, and numerous templates and tools to help you start or grow a business.

Visit chicago.score.org

Key Findings

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

Performance Metrics

chicago.score.org performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value4,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.823

0/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

chicago.score.org

11 ms

chicago.score.org

23 ms

chicago

1154 ms

gtm.js

110 ms

css_y7cp-dQ76wMH6Ik3tmkLea5etnbRLLXyPBTtG-u9ux8.css

21 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Chicago.score.org, 59% (17 requests) were made to Score.org and 7% (2 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Score.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.3 kB (17%)

Content Size

767.5 kB

After Optimization

634.2 kB

In fact, the total size of Chicago.score.org main page is 767.5 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. 25% of websites need less resources to load. Images take 482.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 95.6 kB

  • Original 131.6 kB
  • After minification 124.9 kB
  • After compression 35.9 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 95.6 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 3.6 kB

  • Original 482.7 kB
  • After minification 479.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. Chicago SCORE images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 31.7 kB

  • Original 139.8 kB
  • After minification 139.8 kB
  • After compression 108.1 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 31.7 kB or 23% of the original size.

CSS Optimization

-17%

Potential reduce by 2.3 kB

  • Original 13.4 kB
  • After minification 13.4 kB
  • After compression 11.1 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.score.org needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

18

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

Accessibility Review

chicago.score.org accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

chicago.score.org 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

chicago.score.org 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

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

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 Chicago.score.org 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 Chicago.score.org 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

Open Graph data is detected on the main page of Chicago SCORE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: