Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

Page Load Speed

1.2 sec in total

First Response

174 ms

Resources Loaded

884 ms

Page Rendered

155 ms

plantgrower.org screenshot

About Website

Welcome to plantgrower.org homepage info - get ready to check Plantgrower best content right away, or after learning these important things about plantgrower.org

Ornamental and food production outdoors, in greenhouses and in other controlled environments agriculture systems

Visit plantgrower.org

Key Findings

We analyzed Plantgrower.org page load time and found that the first response time was 174 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

plantgrower.org performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

plantgrower.org

174 ms

www.plantgrower.org

234 ms

sites.css

14 ms

fancybox.css

25 ms

social-icons.css

24 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 27% of them (11 requests) were addressed to the original Plantgrower.org, 68% (28 requests) were made to Cdn2.editmysite.com and 2% (1 request) were made to Static.zotabox.com. The less responsive or slowest element that took the longest time to load (235 ms) belongs to the original domain Plantgrower.org.

Page Optimization Overview & Recommendations

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

Content Size

646.4 kB

After Optimization

562.4 kB

In fact, the total size of Plantgrower.org main page is 646.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. 65% of websites need less resources to load. Javascripts take 471.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.1 kB

  • Original 83.4 kB
  • After minification 80.7 kB
  • After compression 15.3 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 68.1 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 110 B

  • Original 38.2 kB
  • After minification 38.1 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. Plantgrower images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 12.7 kB

  • Original 471.4 kB
  • After minification 469.6 kB
  • After compression 458.8 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

-6%

Potential reduce by 3.1 kB

  • Original 53.4 kB
  • After minification 52.4 kB
  • After compression 50.3 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. Plantgrower.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (76%)

Requests Now

29

After Optimization

7

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

Accessibility Review

plantgrower.org accessibility score

97

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.

Best Practices

plantgrower.org 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

plantgrower.org SEO score

85

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 Plantgrower.org 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 Plantgrower.org 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

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