Tools & Wizards About Us
collectivegrowers.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

collectivegrowers.com

Collective Growers – Locally Owned Licensed Cannabis Retailer

Page Load Speed

3.7 sec in total

First Response

885 ms

Resources Loaded

2.4 sec

Page Rendered

384 ms

collectivegrowers.com screenshot

About Website

Click here to check amazing Collective Growers content for Canada. Otherwise, check out these important facts you probably never knew about collectivegrowers.com

Visit collectivegrowers.com

Key Findings

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

Performance Metrics

collectivegrowers.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

collectivegrowers.com

885 ms

js

126 ms

gtm.js

165 ms

wp-emoji-release.min.js

22 ms

style.min.css

30 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 69% of them (34 requests) were addressed to the original Collectivegrowers.com, 22% (11 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (885 ms) belongs to the original domain Collectivegrowers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.1 kB (3%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Collectivegrowers.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 59.4 kB

  • Original 73.4 kB
  • After minification 69.8 kB
  • After compression 14.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. 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 59.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 4.8 kB

  • Original 1.7 MB
  • After minification 1.7 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. Collective Growers images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 254 B

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

CSS Optimization

-4%

Potential reduce by 5.6 kB

  • Original 145.8 kB
  • After minification 145.8 kB
  • After compression 140.2 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. Collectivegrowers.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (66%)

Requests Now

35

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Collective Growers. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

collectivegrowers.com

collectivegrowers.com

885 ms

js

js

126 ms

gtm.js

gtm.js

165 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

22 ms

style.min.css

style.min.css

30 ms

classic-themes.min.css

classic-themes.min.css

37 ms

styles.css

styles.css

35 ms

style.css

style.css

42 ms

fontawesome.min.css

fontawesome.min.css

34 ms

js_composer.min.css

js_composer.min.css

259 ms

8e84cb2815176706a70cb43c916e7dae

8e84cb2815176706a70cb43c916e7dae

81 ms

css

css

120 ms

ionicons.min.css

ionicons.min.css

269 ms

index.js

index.js

73 ms

index.js

index.js

73 ms

jquery.min.js

jquery.min.js

73 ms

js_composer_front.min.js

js_composer_front.min.js

73 ms

elfsight-age-verification.js

elfsight-age-verification.js

625 ms

jquery-migrate.min.js

jquery-migrate.min.js

76 ms

imagesloaded.min.js

imagesloaded.min.js

301 ms

masonry.min.js

masonry.min.js

346 ms

jquery.masonry.min.js

jquery.masonry.min.js

75 ms

jquery.clb-slider.min.js

jquery.clb-slider.min.js

77 ms

jquery.mega-menu.min.js

jquery.mega-menu.min.js

77 ms

jquery.tilt.min.js

jquery.tilt.min.js

346 ms

aos.min.js

aos.min.js

343 ms

main.min.js

main.min.js

296 ms

CG_Logo_Black_Header.png

CG_Logo_Black_Header.png

297 ms

greencannabis_logo.png

greencannabis_logo.png

299 ms

hemson_logo.png

hemson_logo.png

299 ms

laundryday_logo.png

laundryday_logo.png

298 ms

pippipe_logo.png

pippipe_logo.png

300 ms

ongrok_logo.png

ongrok_logo.png

301 ms

shutterstock_1978625702.jpg

shutterstock_1978625702.jpg

339 ms

10-new-Canadian-infused-drinks-1024x640.jpg

10-new-Canadian-infused-drinks-1024x640.jpg

509 ms

shutterstock_410872996.jpg

shutterstock_410872996.jpg

96 ms

EJRVQgYoZZY2vCFuvAFWzro.ttf

EJRVQgYoZZY2vCFuvAFWzro.ttf

71 ms

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf

71 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf

116 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf

143 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf

145 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf

145 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf

146 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf

145 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf

143 ms

EJRTQgYoZZY2vCFuvAFT_r21dw.ttf

EJRTQgYoZZY2vCFuvAFT_r21dw.ttf

146 ms

EJRQQgYoZZY2vCFuvAFT9gaQZynfpQ.ttf

EJRQQgYoZZY2vCFuvAFT9gaQZynfpQ.ttf

147 ms

fa-brands-400.woff

fa-brands-400.woff

116 ms

ionicons.woff

ionicons.woff

163 ms

Accessibility Review

collectivegrowers.com accessibility score

76

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

Links do not have a discernible name

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

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

collectivegrowers.com 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

collectivegrowers.com SEO score

86

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

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

collectivegrowers.com

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