Tools & Wizards About Us
intelligro.co.nz screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

intelligro.co.nz

Bulk landscape gardening centre Christchurch, Selwyn, Rolleston

Page Load Speed

4.6 sec in total

First Response

348 ms

Resources Loaded

3.5 sec

Page Rendered

682 ms

intelligro.co.nz screenshot

About Website

Click here to check amazing Intelligro content for New Zealand. Otherwise, check out these important facts you probably never knew about intelligro.co.nz

For the highest quality landscape supplies in Christchurch and Rolleston including garden top soil, check out the range by Intelligro.

Visit intelligro.co.nz

Key Findings

We analyzed Intelligro.co.nz page load time and found that the first response time was 348 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

intelligro.co.nz performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value3,350 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

intelligro.co.nz

348 ms

gtm.js

93 ms

theme.css

63 ms

lazysizes.min.js

107 ms

vendor.js

50 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 32% of them (17 requests) were addressed to the original Intelligro.co.nz, 38% (20 requests) were made to Cdn.shopify.com and 6% (3 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.5 kB (27%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 394.1 kB

  • Original 466.0 kB
  • After minification 451.8 kB
  • After compression 71.9 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 394.1 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 3.3 kB

  • Original 317.6 kB
  • After minification 314.4 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. Intelligro images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 52.5 kB

  • Original 831.8 kB
  • After minification 831.8 kB
  • After compression 779.3 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

-1%

Potential reduce by 663 B

  • Original 83.4 kB
  • After minification 83.4 kB
  • After compression 82.7 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. Intelligro.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (79%)

Requests Now

52

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intelligro.co.nz

intelligro.co.nz

348 ms

gtm.js

gtm.js

93 ms

theme.css

theme.css

63 ms

lazysizes.min.js

lazysizes.min.js

107 ms

vendor.js

vendor.js

50 ms

theme.js

theme.js

58 ms

preloads.js

preloads.js

86 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

82 ms

storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js

storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js

83 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

104 ms

cfp_refactored36339.js

cfp_refactored36339.js

706 ms

jquery-uinew.min36339.css

jquery-uinew.min36339.css

511 ms

style.min.css

style.min.css

78 ms

apo-product-options_v1.min.css

apo-product-options_v1.min.css

103 ms

apo-product-options_v2.min.css

apo-product-options_v2.min.css

117 ms

apo-date.js

apo-date.js

126 ms

apo-file.min.js

apo-file.min.js

118 ms

cropper.min.js

cropper.min.js

120 ms

apoPhoneInput.min.js

apoPhoneInput.min.js

122 ms

utils.js

utils.js

129 ms

apo-color-picker.js

apo-color-picker.js

150 ms

cropper.css

cropper.css

134 ms

apoPhoneInput.css

apoPhoneInput.css

149 ms

apo-options.js

apo-options.js

156 ms

apo-style-collections.min.js

apo-style-collections.min.js

150 ms

apo-style-products.js

apo-style-products.js

153 ms

apo-product-options.js

apo-product-options.js

182 ms

apo-mini-cart.js

apo-mini-cart.js

157 ms

klaviyo.js

klaviyo.js

73 ms

storepickup_v1.js

storepickup_v1.js

197 ms

inbox-chat-loader.js

inbox-chat-loader.js

166 ms

analytics.js

analytics.js

70 ms

afterpay-1.x.js

afterpay-1.x.js

93 ms

shopify-afterpay-javascript.js

shopify-afterpay-javascript.js

85 ms

gtm.js

gtm.js

62 ms

storepickup_v1.css

storepickup_v1.css

19 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

88 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

89 ms

runtime.f0e7d4bf2a07ba450c3d.js

runtime.f0e7d4bf2a07ba450c3d.js

2 ms

sharedUtils.e8c90ec039ff40fd1c44.js

sharedUtils.e8c90ec039ff40fd1c44.js

13 ms

trekkie.storefront.a1ad2ab43a5932ff96084a0e2e69f51ba73ddbec.min.js

trekkie.storefront.a1ad2ab43a5932ff96084a0e2e69f51ba73ddbec.min.js

152 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

152 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

149 ms

logo-afterpay-black.png

logo-afterpay-black.png

143 ms

blank_1x1.gif

blank_1x1.gif

145 ms

soil-calculator.png

soil-calculator.png

146 ms

collect

collect

94 ms

afterpay_logo_small-c21f624e13e513b83e729c61fa161b4d75643a4e62d4dcd3df62e1c5d3ed7326.svg

afterpay_logo_small-c21f624e13e513b83e729c61fa161b4d75643a4e62d4dcd3df62e1c5d3ed7326.svg

122 ms

polyfill.min.js

polyfill.min.js

1116 ms

Intelligro-logo-0321-800_rev_180x.png

Intelligro-logo-0321-800_rev_180x.png

229 ms

Intelligro-logo-0321-800_180x.png

Intelligro-logo-0321-800_180x.png

279 ms

1AC15BC0-7DB0-4665-8E8F-976942FEA090.jpg

1AC15BC0-7DB0-4665-8E8F-976942FEA090.jpg

480 ms

Vegepod_KitchenGarden_Black_7e5d1b6a-9257-44d8-a7cc-fc55da42a15f.jpg

Vegepod_KitchenGarden_Black_7e5d1b6a-9257-44d8-a7cc-fc55da42a15f.jpg

62 ms

Accessibility Review

intelligro.co.nz accessibility score

92

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.

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

Links do not have a discernible name

Best Practices

intelligro.co.nz best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

intelligro.co.nz SEO score

86

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

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 Intelligro.co.nz 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 Intelligro.co.nz 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

intelligro.co.nz

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