Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

growables.org

Growables Home Page

Page Load Speed

1.4 sec in total

First Response

129 ms

Resources Loaded

1.1 sec

Page Rendered

185 ms

growables.org screenshot

About Website

Visit growables.org now to see the best up-to-date Growables content for Spain and also check out these interesting facts you probably never knew about growables.org

how to,tropical tree,grow in florida,growables,grow florida edibles,fruit,

Visit growables.org

Key Findings

We analyzed Growables.org page load time and found that the first response time was 129 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

growables.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

growables.org

129 ms

growables.org

266 ms

grodropdownmenu.css

197 ms

grotext.css

195 ms

grodiv.css

197 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that all of those requests were addressed to Growables.org and no external sources were called. The less responsive or slowest element that took the longest time to load (502 ms) belongs to the original domain Growables.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.1 kB (9%)

Content Size

312.6 kB

After Optimization

284.5 kB

In fact, the total size of Growables.org main page is 312.6 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. 15% of websites need less resources to load. Images take 288.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 13.0 kB

  • Original 16.5 kB
  • After minification 16.5 kB
  • After compression 3.5 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 13.0 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 11.5 kB

  • Original 288.6 kB
  • After minification 277.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. Growables images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 3.3 kB

  • Original 6.0 kB
  • After minification 6.0 kB
  • After compression 2.7 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.3 kB or 54% of the original size.

CSS Optimization

-27%

Potential reduce by 433 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.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. Growables.org needs all CSS files to be minified and compressed as it can save up to 433 B or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

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

Accessibility Review

growables.org accessibility score

95

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

growables.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

growables.org SEO score

77

Search Engine Optimization Advices

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