Tools & Wizards About Us
chicagobrickco.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

chicagobrickco.com

Masonry contractors Chicago | Tuckpointing Contractor - Chicago Brick Co.

Page Load Speed

3.7 sec in total

First Response

203 ms

Resources Loaded

2.7 sec

Page Rendered

855 ms

chicagobrickco.com screenshot

About Website

Click here to check amazing Chicago Brick Co content. Otherwise, check out these important facts you probably never knew about chicagobrickco.com

"The Chicago Brick Co. is a full-service masonry, tuckpointing, and brick repairing contractor located in Chicago, IL."

Visit chicagobrickco.com

Key Findings

We analyzed Chicagobrickco.com page load time and found that the first response time was 203 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

chicagobrickco.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

chicagobrickco.com

203 ms

chicagobrickco.com

247 ms

4621b474b6622427d9a84e9afaa58943.css

70 ms

jquery.min.js

47 ms

gallery.js

40 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 91% of them (69 requests) were addressed to the original Chicagobrickco.com, 5% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Chicagobrickco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 384.4 kB (7%)

Content Size

5.4 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chicagobrickco.com main page is 5.4 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. 60% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 98.8 kB

  • Original 120.4 kB
  • After minification 99.8 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 20.6 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 98.8 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 285.4 kB

  • Original 5.1 MB
  • After minification 4.9 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. Chicago Brick Co images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 234 B

  • Original 56.9 kB
  • After minification 56.9 kB
  • After compression 56.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 52.4 kB
  • After minification 52.4 kB
  • After compression 52.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. Chicagobrickco.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (51%)

Requests Now

63

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chicagobrickco.com

chicagobrickco.com

203 ms

chicagobrickco.com

chicagobrickco.com

247 ms

4621b474b6622427d9a84e9afaa58943.css

4621b474b6622427d9a84e9afaa58943.css

70 ms

jquery.min.js

jquery.min.js

47 ms

gallery.js

gallery.js

40 ms

isotope.js

isotope.js

2262 ms

refine-portfolio-public.js

refine-portfolio-public.js

2293 ms

js

js

130 ms

css

css

33 ms

email-decode.min.js

email-decode.min.js

16 ms

scripts.js

scripts.js

21 ms

pointed-popup.js

pointed-popup.js

64 ms

classie.js

classie.js

63 ms

owl.carousel.min.js

owl.carousel.min.js

68 ms

index.js

index.js

72 ms

index.js

index.js

73 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

74 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

73 ms

functions.js

functions.js

76 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

78 ms

script.min.js

script.min.js

210 ms

lazyload.min.js

lazyload.min.js

79 ms

css

css

17 ms

innerpage-back.jpg

innerpage-back.jpg

34 ms

y_name.png

y_name.png

33 ms

phone.png

phone.png

34 ms

location.png

location.png

37 ms

mail.png

mail.png

36 ms

featured-work.jpeg

featured-work.jpeg

53 ms

1439884715.jpg

1439884715.jpg

359 ms

featured-work2.jpeg

featured-work2.jpeg

62 ms

Screen-Shot-2020-09-30-at-12.09.26-PM.png

Screen-Shot-2020-09-30-at-12.09.26-PM.png

70 ms

1456417969.jpg

1456417969.jpg

81 ms

featured-work3.png

featured-work3.png

91 ms

arrow.png

arrow.png

94 ms

loca_footer.png

loca_footer.png

107 ms

phone_footer.png

phone_footer.png

152 ms

printer.png

printer.png

120 ms

footer_mail.png

footer_mail.png

155 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

39 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

53 ms

banner-1.jpg

banner-1.jpg

585 ms

mob-push-menu.jpg

mob-push-menu.jpg

125 ms

logo.png

logo.png

131 ms

location.png

location.png

137 ms

call.png

call.png

158 ms

thum2-338x205.jpg

thum2-338x205.jpg

317 ms

thum4-338x205.jpg

thum4-338x205.jpg

397 ms

thum5-338x205.jpg

thum5-338x205.jpg

539 ms

featured-work2-385x234.jpeg

featured-work2-385x234.jpeg

557 ms

featured-work-385x234.jpeg

featured-work-385x234.jpeg

626 ms

Screen-Shot-2020-09-30-at-12.09.26-PM-385x234.png

Screen-Shot-2020-09-30-at-12.09.26-PM-385x234.png

1019 ms

featured-work3-385x234.png

featured-work3-385x234.png

938 ms

2.png

2.png

741 ms

2-hover.png

2-hover.png

779 ms

3.png

3.png

904 ms

3-hover.png

3-hover.png

936 ms

4.png

4.png

1072 ms

4-hover.png

4-hover.png

1093 ms

5.png

5.png

1084 ms

5-hover.png

5-hover.png

1176 ms

1-blog.png

1-blog.png

1440 ms

2-1.png

2-1.png

1405 ms

3-1.png

3-1.png

1083 ms

site-img.png

site-img.png

1088 ms

img1.jpg

img1.jpg

1240 ms

arrow.png

arrow.png

1224 ms

footerlogo.png

footerlogo.png

1239 ms

close.png

close.png

1230 ms

Nexa-bold.otf

Nexa-bold.otf

1186 ms

Nexa-Light.woff

Nexa-Light.woff

1435 ms

SegoePrint.woff

SegoePrint.woff

1201 ms

9de6e833c2a290e3ff99bc3bd95af039-webfont.woff

9de6e833c2a290e3ff99bc3bd95af039-webfont.woff

1420 ms

futurabt.otf

futurabt.otf

1307 ms

Accessibility Review

chicagobrickco.com accessibility score

74

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

High

Links do not have a discernible name

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

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

chicagobrickco.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

chicagobrickco.com SEO score

89

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

High

Tap targets are not sized appropriately

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 Chicagobrickco.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 Chicagobrickco.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

chicagobrickco.com

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