Tools & Wizards About Us
gardencare.co.za screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

gardencare.co.za

Page Load Speed

3.6 sec in total

First Response

807 ms

Resources Loaded

2.6 sec

Page Rendered

200 ms

gardencare.co.za screenshot

About Website

Click here to check amazing Gardencare content. Otherwise, check out these important facts you probably never knew about gardencare.co.za

Visit gardencare.co.za

Key Findings

We analyzed Gardencare.co.za page load time and found that the first response time was 807 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 50% of websites can load faster.

Performance Metrics

gardencare.co.za performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

gardencare.co.za

807 ms

gardencare.css

247 ms

menu_data.js

497 ms

pagecolour.gif

272 ms

header.gif

491 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that all of those requests were addressed to Gardencare.co.za and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gardencare.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.2 kB (13%)

Content Size

182.4 kB

After Optimization

158.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gardencare.co.za main page is 182.4 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. Only 10% of websites need less resources to load. Images take 166.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 6.9 kB

  • Original 9.7 kB
  • After minification 8.9 kB
  • After compression 2.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 6.9 kB or 71% of the original size.

Image Optimization

-7%

Potential reduce by 12.4 kB

  • Original 166.4 kB
  • After minification 153.9 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. Gardencare images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 3.0 kB

  • Original 4.1 kB
  • After minification 3.5 kB
  • After compression 1.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.0 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 1.9 kB

  • Original 2.3 kB
  • After minification 1.9 kB
  • After compression 392 B

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. Gardencare.co.za needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gardencare. According to our analytics all requests are already optimized.

Network Requests Diagram

gardencare.co.za

gardencare.co.za

807 ms

gardencare.css

gardencare.css

247 ms

menu_data.js

menu_data.js

497 ms

pagecolour.gif

pagecolour.gif

272 ms

header.gif

header.gif

491 ms

introb1.jpg

introb1.jpg

509 ms

introb2.jpg

introb2.jpg

510 ms

introc1.jpg

introc1.jpg

509 ms

introc2.jpg

introc2.jpg

510 ms

introd1.jpg

introd1.jpg

511 ms

introd2.jpg

introd2.jpg

982 ms

introbookname.jpg

introbookname.jpg

751 ms

buybook.jpg

buybook.jpg

753 ms

introbook.jpg

introbook.jpg

1489 ms

index_clip_image001.gif

index_clip_image001.gif

772 ms

index_clip_image002.gif

index_clip_image002.gif

787 ms

index_clip_image002_0021.jpg

index_clip_image002_0021.jpg

1011 ms

links_clip_image002_0000.jpg

links_clip_image002_0000.jpg

996 ms

index_clip_image002_0018.jpg

index_clip_image002_0018.jpg

1027 ms

Accessibility Review

gardencare.co.za accessibility score

86

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

<frame> or <iframe> elements do not have a title

Best Practices

gardencare.co.za 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

SEO Factors

gardencare.co.za SEO score

100

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gardencare.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Gardencare.co.za main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

gardencare.co.za

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