Tools & Wizards About Us
whatcombar.org screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

whatcombar.org

Whatcom County Bar Association - HOME PAGE

Page Load Speed

973 ms in total

First Response

13 ms

Resources Loaded

537 ms

Page Rendered

423 ms

whatcombar.org screenshot

About Website

Click here to check amazing Whatcom Bar content. Otherwise, check out these important facts you probably never knew about whatcombar.org

Visit whatcombar.org

Key Findings

We analyzed Whatcombar.org page load time and found that the first response time was 13 ms and then it took 960 ms 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

whatcombar.org performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

whatcombar.org

13 ms

whatcombar.wildapricot.org

50 ms

whatcombar.wildapricot.org

104 ms

combined.css

34 ms

index-9cf11fa.css

54 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Whatcombar.org, 48% (15 requests) were made to Sf.wildapricot.org and 19% (6 requests) were made to Live-sf.wildapricot.org. The less responsive or slowest element that took the longest time to load (108 ms) relates to the external source Whatcombar.wildapricot.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.4 kB (11%)

Content Size

1.1 MB

After Optimization

993.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatcombar.org main page is 1.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. 65% of websites need less resources to load. Javascripts take 653.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 75.3 kB

  • Original 86.2 kB
  • After minification 49.7 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 36.5 kB, which is 42% 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 75.3 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 6.4 kB

  • Original 183.5 kB
  • After minification 177.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. Whatcom Bar images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 38.6 kB

  • Original 653.3 kB
  • After minification 653.3 kB
  • After compression 614.7 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

-3%

Potential reduce by 5.1 kB

  • Original 196.2 kB
  • After minification 196.2 kB
  • After compression 191.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. Whatcombar.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (22%)

Requests Now

18

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatcombar.org

whatcombar.org

13 ms

whatcombar.wildapricot.org

whatcombar.wildapricot.org

50 ms

whatcombar.wildapricot.org

whatcombar.wildapricot.org

104 ms

combined.css

combined.css

34 ms

index-9cf11fa.css

index-9cf11fa.css

54 ms

shared-ui-compiled.css

shared-ui-compiled.css

59 ms

bonapagetop-compiled.js

bonapagetop-compiled.js

73 ms

index-9cf11fa.js

index-9cf11fa.js

85 ms

shared-ui-compiled.js

shared-ui-compiled.js

105 ms

General.js

General.js

70 ms

combined.js

combined.js

55 ms

layout_image_1.jpg

layout_image_1.jpg

90 ms

asyncLoadProgress.gif

asyncLoadProgress.gif

25 ms

async-load-progress-01.gif

async-load-progress-01.gif

45 ms

close.png

close.png

14 ms

loading.gif

loading.gif

13 ms

prev.png

prev.png

14 ms

next.png

next.png

14 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

21 ms

opensans-light-webfont.woff

opensans-light-webfont.woff

22 ms

opensans-semibold-webfont.woff

opensans-semibold-webfont.woff

13 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

21 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

22 ms

oswald-bold-webfont.woff

oswald-bold-webfont.woff

22 ms

oswald-regular-webfont.woff

oswald-regular-webfont.woff

23 ms

opensans-italic-webfont.woff

opensans-italic-webfont.woff

21 ms

404

404

108 ms

Adam.jpg

Adam.jpg

29 ms

Jacob%20Holland%20cropped.jpg

Jacob%20Holland%20cropped.jpg

29 ms

Caroline.jpg

Caroline.jpg

30 ms

Ian.jpg

Ian.jpg

29 ms

Accessibility Review

whatcombar.org accessibility score

79

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

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

Best Practices

whatcombar.org 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

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

whatcombar.org SEO score

81

Search Engine Optimization Advices

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

whatcombar.org

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