Tools & Wizards About Us
indigrow.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 0

    Best Practices

  • 83

    SEO

    Google-friendlier than
    46% of websites

indigrow.com

Indigrow | Growth through innovation

Page Load Speed

4.2 sec in total

First Response

821 ms

Resources Loaded

3.3 sec

Page Rendered

149 ms

indigrow.com screenshot

About Website

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

A group of companies striving to bring the latest technological advances to the turf and amenity, agriculture and horticulture and weed control industries.

Visit indigrow.com

Key Findings

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

Performance Metrics

indigrow.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,030 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

indigrow.com

821 ms

e41a00061d1e092d1021c928aff74a08.css

105 ms

e5e2c13a137eac29fc9daf79a27b3b7d.css

194 ms

1cd742e4d91b854b5c458123f85ed0cf.css

199 ms

content-module.css

205 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 94% of them (48 requests) were addressed to the original Indigrow.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Geoplugin.net. The less responsive or slowest element that took the longest time to load (986 ms) belongs to the original domain Indigrow.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.5 kB (52%)

Content Size

277.0 kB

After Optimization

132.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indigrow.com main page is 277.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 103.2 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 7.2 kB

  • Original 10.3 kB
  • After minification 9.8 kB
  • After compression 3.1 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 7.2 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 4.5 kB

  • Original 78.7 kB
  • After minification 74.2 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. Indigrow images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 61.1 kB

  • Original 103.2 kB
  • After minification 89.5 kB
  • After compression 42.0 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 61.1 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 71.7 kB

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

Requests Breakdown

Number of requests can be reduced by 36 (82%)

Requests Now

44

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indigrow.com

indigrow.com

821 ms

e41a00061d1e092d1021c928aff74a08.css

e41a00061d1e092d1021c928aff74a08.css

105 ms

e5e2c13a137eac29fc9daf79a27b3b7d.css

e5e2c13a137eac29fc9daf79a27b3b7d.css

194 ms

1cd742e4d91b854b5c458123f85ed0cf.css

1cd742e4d91b854b5c458123f85ed0cf.css

199 ms

content-module.css

content-module.css

205 ms

ctools.css

ctools.css

207 ms

date.css

date.css

207 ms

faceebox.css

faceebox.css

208 ms

filefield.css

filefield.css

290 ms

mollom.css

mollom.css

294 ms

panels.css

panels.css

306 ms

node.css

node.css

310 ms

defaults.css

defaults.css

310 ms

system.css

system.css

312 ms

system-menus.css

system-menus.css

385 ms

user.css

user.css

392 ms

fieldgroup.css

fieldgroup.css

406 ms

views.css

views.css

412 ms

flexible.css

flexible.css

413 ms

custom_search.css

custom_search.css

413 ms

style.css

style.css

484 ms

jquery.min.js

jquery.min.js

691 ms

drupal.js

drupal.js

507 ms

facebox.js

facebox.js

514 ms

googleanalytics.js

googleanalytics.js

502 ms

mollom.js

mollom.js

504 ms

panels.js

panels.js

567 ms

poormanscron.js

poormanscron.js

597 ms

custom_search.js

custom_search.js

605 ms

javascript.gp

javascript.gp

174 ms

cookieControl-5.1.min.js

cookieControl-5.1.min.js

986 ms

reset.css

reset.css

136 ms

spacer.gif

spacer.gif

106 ms

landing_02.jpg

landing_02.jpg

194 ms

landing_05.jpg

landing_05.jpg

319 ms

landing_07.jpg

landing_07.jpg

100 ms

landing_08.jpg

landing_08.jpg

106 ms

landing_09.jpg

landing_09.jpg

199 ms

2014-background_0.jpg

2014-background_0.jpg

841 ms

ga.js

ga.js

14 ms

closelabel.gif

closelabel.gif

580 ms

closelabel.gif

closelabel.gif

98 ms

loading.gif

loading.gif

555 ms

tl.png

tl.png

104 ms

b.png

b.png

99 ms

tr.png

tr.png

105 ms

bl.png

bl.png

194 ms

br.png

br.png

197 ms

__utm.gif

__utm.gif

13 ms

amenityover.png

amenityover.png

612 ms

aghortover.png

aghortover.png

597 ms

Accessibility Review

indigrow.com accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

SEO Factors

indigrow.com SEO score

83

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indigrow.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Indigrow.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

indigrow.com

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