Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

beinggardener.com

BeingGardener - Gardening Portal for Seeds and Material - Being Gardener | Gardening Portal

Page Load Speed

20.5 sec in total

First Response

2.6 sec

Resources Loaded

17.2 sec

Page Rendered

747 ms

beinggardener.com screenshot

About Website

Visit beinggardener.com now to see the best up-to-date Being Gardener content for India and also check out these interesting facts you probably never knew about beinggardener.com

BeingGardener - Gardening Portal for Seeds and Material . Buy Vegetable , Leafy Vegetable and flower , Fruit seeds online in beinggardener.com at reasonable prices . HDPE Grow Bags , neem Oil and Neem...

Visit beinggardener.com

Key Findings

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

Performance Metrics

beinggardener.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.284

42/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

beinggardener.com

2583 ms

www.beinggardener.com

1765 ms

jquery.js

771 ms

jquery.blockUI.min.js

573 ms

add-to-cart.min.js

585 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 46% of them (57 requests) were addressed to the original Beinggardener.com, 7% (9 requests) were made to Sync.crwdcntrl.net and 4% (5 requests) were made to Bcp.crwdcntrl.net. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Beinggardener.com.

Page Optimization Overview & Recommendations

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

Content Size

681.2 kB

After Optimization

500.5 kB

In fact, the total size of Beinggardener.com main page is 681.2 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. 55% of websites need less resources to load. Images take 436.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 163.7 kB

  • Original 190.0 kB
  • After minification 182.5 kB
  • After compression 26.2 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 163.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 436.1 kB
  • After minification 436.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. Being Gardener images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 17.0 kB

  • Original 55.1 kB
  • After minification 52.5 kB
  • After compression 38.2 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 17.0 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (66%)

Requests Now

102

After Optimization

35

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

Accessibility Review

beinggardener.com accessibility score

87

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

beinggardener.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

beinggardener.com SEO score

84

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Beinggardener.com 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 Beinggardener.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

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