Tools & Wizards About Us
corr.us screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

corr.us

Granite Wellness Centers

Page Load Speed

1.9 sec in total

First Response

136 ms

Resources Loaded

1.6 sec

Page Rendered

182 ms

corr.us screenshot

About Website

Click here to check amazing Corr content. Otherwise, check out these important facts you probably never knew about corr.us

Granite Wellness Centers saves and improves lives through substance use treatment & behavioral health services in Placer & Nevada counties

Visit corr.us

Key Findings

We analyzed Corr.us page load time and found that the first response time was 136 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

corr.us performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.088

92/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

corr.us

136 ms

www.granitewellness.org

505 ms

fonts.css

88 ms

leaflet.min.css

123 ms

style.min.css

247 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Corr.us, 75% (27 requests) were made to Granitewellness.org and 14% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (796 ms) relates to the external source Granitewellness.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 729.9 kB (63%)

Content Size

1.2 MB

After Optimization

423.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Corr.us main page is 1.2 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. 40% of websites need less resources to load. CSS take 603.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 44.5 kB

  • Original 54.9 kB
  • After minification 53.4 kB
  • After compression 10.4 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 44.5 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 7.0 kB

  • Original 212.3 kB
  • After minification 205.3 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. Corr images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 207.2 kB

  • Original 282.5 kB
  • After minification 265.8 kB
  • After compression 75.2 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 207.2 kB or 73% of the original size.

CSS Optimization

-78%

Potential reduce by 471.2 kB

  • Original 603.3 kB
  • After minification 573.0 kB
  • After compression 132.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. Corr.us needs all CSS files to be minified and compressed as it can save up to 471.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (86%)

Requests Now

29

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

corr.us

corr.us

136 ms

www.granitewellness.org

www.granitewellness.org

505 ms

fonts.css

fonts.css

88 ms

leaflet.min.css

leaflet.min.css

123 ms

style.min.css

style.min.css

247 ms

cleantalk-public.min.css

cleantalk-public.min.css

189 ms

styles.css

styles.css

256 ms

style.css

style.css

334 ms

dashicons.min.css

dashicons.min.css

311 ms

genericons.css

genericons.css

319 ms

font-awesome.min.css

font-awesome.min.css

373 ms

all.min.css

all.min.css

383 ms

all.min.css

all.min.css

460 ms

ngg_k2.css

ngg_k2.css

436 ms

framework-min.css

framework-min.css

507 ms

shutter-reloaded.css

shutter-reloaded.css

498 ms

style.css

style.css

524 ms

ofd4pbk.css

ofd4pbk.css

150 ms

jquery.min.js

jquery.min.js

622 ms

jquery-migrate.min.js

jquery-migrate.min.js

570 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

652 ms

shutter-reloaded.js

shutter-reloaded.js

637 ms

owl.carousel.min.js

owl.carousel.min.js

685 ms

navigation.js

navigation.js

751 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

752 ms

hoverIntent.min.js

hoverIntent.min.js

752 ms

maxmegamenu.js

maxmegamenu.js

774 ms

public.js

public.js

783 ms

gwc_logo_plum.png

gwc_logo_plum.png

796 ms

p.css

p.css

31 ms

emma-simpson-mNGaaLeWEp0-unsplash-scaled-e1665607578787.jpg

emma-simpson-mNGaaLeWEp0-unsplash-scaled-e1665607578787.jpg

263 ms

d

d

22 ms

d

d

68 ms

d

d

29 ms

wARDj0u

wARDj0u

3 ms

d

d

66 ms

Accessibility Review

corr.us accessibility score

98

Accessibility Issues

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

corr.us 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

SEO Factors

corr.us SEO score

92

Search Engine Optimization Advices

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 Corr.us 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 Corr.us 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

corr.us

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