Tools & Wizards About Us
brigham.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

brigham.com

CT Brigham | Pittsfield, MA | Janitorial Supplies | Paper Products | Office Products

Page Load Speed

1.2 sec in total

First Response

79 ms

Resources Loaded

896 ms

Page Rendered

195 ms

brigham.com screenshot

About Website

Visit brigham.com now to see the best up-to-date Brigham content and also check out these interesting facts you probably never knew about brigham.com

CT Brigham is located in Pittsfield MA and we offer paper products, cleaning supplies and janitorial products in Western MA.

Visit brigham.com

Key Findings

We analyzed Brigham.com page load time and found that the first response time was 79 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 25% of websites can load faster.

Performance Metrics

brigham.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.413

24/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

brigham.com

79 ms

www.brigham.com

80 ms

catalog

14 ms

243 ms

bootstrap.min.css

105 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 37% of them (25 requests) were addressed to the original Brigham.com, 21% (14 requests) were made to Images.jmcatalog.com and 10% (7 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (367 ms) belongs to the original domain Brigham.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 627.4 kB (10%)

Content Size

6.5 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 229.5 kB

  • Original 272.8 kB
  • After minification 176.3 kB
  • After compression 43.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 96.5 kB, which is 35% 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 229.5 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 202.5 kB

  • Original 5.7 MB
  • After minification 5.5 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. Brigham images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 37.3 kB

  • Original 258.8 kB
  • After minification 258.8 kB
  • After compression 221.5 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 37.3 kB or 14% of the original size.

CSS Optimization

-55%

Potential reduce by 158.1 kB

  • Original 290.1 kB
  • After minification 284.0 kB
  • After compression 132.0 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. Brigham.com needs all CSS files to be minified and compressed as it can save up to 158.1 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (53%)

Requests Now

62

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brigham.com

brigham.com

79 ms

www.brigham.com

www.brigham.com

80 ms

catalog

catalog

14 ms

243 ms

bootstrap.min.css

bootstrap.min.css

105 ms

jquery-ui.css

jquery-ui.css

110 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

104 ms

jquery-ui.min.js

jquery-ui.min.js

122 ms

bootstrap.min.js

bootstrap.min.js

103 ms

bootbox.min.js

bootbox.min.js

138 ms

font-awesome.min.css

font-awesome.min.css

149 ms

main.min.css

main.min.css

147 ms

navbar.min.css

navbar.min.css

144 ms

items.min.css

items.min.css

145 ms

overall_Custom.css

overall_Custom.css

143 ms

navbar_top_Custom.css

navbar_top_Custom.css

148 ms

navbar_category_Custom.css

navbar_category_Custom.css

161 ms

st_Default.css

st_Default.css

158 ms

analytics.js

analytics.js

120 ms

CombinedBaseSkinClassic.css

CombinedBaseSkinClassic.css

142 ms

FormDecorator.Default.css

FormDecorator.Default.css

138 ms

Ajax.Default.css

Ajax.Default.css

137 ms

WebForms.js

WebForms.js

100 ms

ScriptResource.axd

ScriptResource.axd

127 ms

ScriptResource.axd

ScriptResource.axd

118 ms

Core.js

Core.js

108 ms

ShortCutManagerScripts.js

ShortCutManagerScripts.js

108 ms

MaterialRippleScripts.js

MaterialRippleScripts.js

108 ms

RadFormDecorator.js

RadFormDecorator.js

108 ms

Ajax.js

Ajax.js

108 ms

jQueryExternal.js

jQueryExternal.js

108 ms

OverlayScript.js

OverlayScript.js

108 ms

owl.carousel.min.css

owl.carousel.min.css

77 ms

owl.theme.default.min.css

owl.theme.default.min.css

66 ms

animate.min.css

animate.min.css

64 ms

item_sections.min.css

item_sections.min.css

61 ms

owl.carousel.min.js

owl.carousel.min.js

25 ms

css

css

34 ms

header-logo.png

header-logo.png

54 ms

KIM017713.JPG

KIM017713.JPG

239 ms

AKERS1.JPG

AKERS1.JPG

261 ms

KIM002001.JPG

KIM002001.JPG

268 ms

KIM021270.JPG

KIM021270.JPG

265 ms

SPAR8009.JPG

SPAR8009.JPG

288 ms

SPAR6019.JPG

SPAR6019.JPG

249 ms

SPAR1085.JPG

SPAR1085.JPG

248 ms

SPAR1087.JPG

SPAR1087.JPG

259 ms

SPAR9757.JPG

SPAR9757.JPG

267 ms

SPAR9756.JPG

SPAR9756.JPG

272 ms

SPAR3152.JPG

SPAR3152.JPG

272 ms

SPAR334506.JPG

SPAR334506.JPG

287 ms

SPAR711603.JPG

SPAR711603.JPG

287 ms

SPAR6031.JPG

SPAR6031.JPG

287 ms

header-logo-small.png

header-logo-small.png

50 ms

28

28

262 ms

29

29

297 ms

30

30

328 ms

31

31

287 ms

32

32

258 ms

33

33

315 ms

34

34

338 ms

35

35

358 ms

36

36

367 ms

collect

collect

69 ms

font

font

223 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

52 ms

js

js

195 ms

Accessibility Review

brigham.com accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

brigham.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

brigham.com SEO score

80

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

    EN

  • Encoding

    UTF-8

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

brigham.com

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