Tools & Wizards About Us
growize.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

growize.com

Grow Store, Indoor Gardening Supplies, Hydroponic Gardening | Lakewood, CO

Page Load Speed

1.1 sec in total

First Response

86 ms

Resources Loaded

474 ms

Page Rendered

531 ms

growize.com screenshot

About Website

Click here to check amazing Grow Ize content. Otherwise, check out these important facts you probably never knew about growize.com

GroWize is your local grow store in Lakewood, CO! We sell hydroponic gardening supplies & accessories. Visit us for all your indoor gardening needs!

Visit growize.com

Key Findings

We analyzed Growize.com page load time and found that the first response time was 86 ms and then it took 1 sec 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

growize.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value800 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.392

26/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

growize.com

86 ms

jquery-ui.min.css

10 ms

css

40 ms

theme.css

20 ms

cms_theme_custom_css.php

37 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 59% of them (24 requests) were addressed to the original Growize.com, 15% (6 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (186 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

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

Content Size

4.7 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 32.7 kB

  • Original 41.5 kB
  • After minification 38.0 kB
  • After compression 8.8 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 32.7 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 85.5 kB

  • Original 4.4 MB
  • After minification 4.4 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. Grow Ize images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 227 B

  • Original 162.8 kB
  • After minification 162.8 kB
  • After compression 162.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

-13%

Potential reduce by 7.0 kB

  • Original 53.7 kB
  • After minification 53.7 kB
  • After compression 46.8 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. Growize.com needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (52%)

Requests Now

33

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

growize.com

growize.com

86 ms

jquery-ui.min.css

jquery-ui.min.css

10 ms

css

css

40 ms

theme.css

theme.css

20 ms

cms_theme_custom_css.php

cms_theme_custom_css.php

37 ms

scripts.min.js

scripts.min.js

15 ms

external-tracking.min.js

external-tracking.min.js

9 ms

cms_custom_css.php

cms_custom_css.php

15 ms

js

js

183 ms

js

js

186 ms

underscore.min.js

underscore.min.js

14 ms

theme-plugins-min.js

theme-plugins-min.js

35 ms

theme-min.js

theme-min.js

35 ms

beacon-lazy-load.min.js

beacon-lazy-load.min.js

36 ms

theme-menu-horizontal-v1.min.js

theme-menu-horizontal-v1.min.js

35 ms

scripts.min.js

scripts.min.js

38 ms

css

css

21 ms

loading.gif

loading.gif

96 ms

ga.js

ga.js

88 ms

no-bkg-img.gif

no-bkg-img.gif

9 ms

GroWize-Logo-1-white.jpg

GroWize-Logo-1-white.jpg

118 ms

lazy-load-placeholder.png

lazy-load-placeholder.png

9 ms

dl-21.jpg

dl-21.jpg

77 ms

GroWize-Logo-1-white-1.jpg

GroWize-Logo-1-white-1.jpg

115 ms

dl-11-new-1-7e4.jpg

dl-11-new-1-7e4.jpg

56 ms

rain-feat.png

rain-feat.png

56 ms

flower-feat.png

flower-feat.png

55 ms

nutrient-feat.png

nutrient-feat.png

119 ms

contact-feat.png

contact-feat.png

117 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

57 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

63 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

76 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

86 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

85 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

86 ms

tsi-cms.ttf

tsi-cms.ttf

59 ms

sdk.js

sdk.js

58 ms

__utm.gif

__utm.gif

32 ms

__utm.gif

__utm.gif

8 ms

sdk.js

sdk.js

20 ms

92 ms

Accessibility Review

growize.com accessibility score

56

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

growize.com best practices score

83

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

SEO Factors

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

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

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

growize.com

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