Tools & Wizards About Us
greenex.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

greenex.com

Home - Greenex

Page Load Speed

3.2 sec in total

First Response

314 ms

Resources Loaded

2.9 sec

Page Rendered

55 ms

greenex.com screenshot

About Website

Welcome to greenex.com homepage info - get ready to check Greenex best content right away, or after learning these important things about greenex.com

Worldwide production and distribution of Seeds, Cuttings, Liners/Young Plants, Half-Finished and Pre-Finished Plants for commercial growers.

Visit greenex.com

Key Findings

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

Performance Metrics

greenex.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

greenex.com

314 ms

greenex.com

414 ms

www.greenex.com

562 ms

uc.js

39 ms

bootstrap-icons.css

34 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 72% of them (26 requests) were addressed to the original Greenex.com, 11% (4 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Policy.app.cookieinformation.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Greenex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.1 kB (2%)

Content Size

3.0 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greenex.com main page is 3.0 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. 40% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 15.8 kB

  • Original 19.6 kB
  • After minification 15.7 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.6 MB
  • After minification 2.6 MB

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. Greenex images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 27.2 kB

  • Original 346.4 kB
  • After minification 346.4 kB
  • After compression 319.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. This website has mostly compressed JavaScripts.

CSS Optimization

-21%

Potential reduce by 12.0 kB

  • Original 58.5 kB
  • After minification 58.5 kB
  • After compression 46.5 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. Greenex.com needs all CSS files to be minified and compressed as it can save up to 12.0 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (62%)

Requests Now

29

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greenex.com

greenex.com

314 ms

greenex.com

greenex.com

414 ms

www.greenex.com

www.greenex.com

562 ms

uc.js

uc.js

39 ms

bootstrap-icons.css

bootstrap-icons.css

34 ms

bootstrap-grid.css

bootstrap-grid.css

100 ms

bootstrap.css

bootstrap.css

202 ms

animate.css

animate.css

289 ms

site.css

site.css

382 ms

js

js

86 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

448 ms

lazysizes.min.js

lazysizes.min.js

290 ms

jquery.validate.min.js

jquery.validate.min.js

291 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

298 ms

bootstrap.bundle.js

bootstrap.bundle.js

484 ms

pdf.min.js

pdf.min.js

684 ms

filesaver.min.js

filesaver.min.js

447 ms

wow.min.js

wow.min.js

449 ms

main.js

main.js

477 ms

lightbox.js

lightbox.js

480 ms

webfont.js

webfont.js

41 ms

lightbox.min.js

lightbox.min.js

46 ms

greenex-logo.png

greenex-logo.png

107 ms

foliage-hero-optimized.png

foliage-hero-optimized.png

1185 ms

koppe-20210429_202-optimized.jpg

koppe-20210429_202-optimized.jpg

464 ms

hero-home-flowering.jpg

hero-home-flowering.jpg

373 ms

kp-holland-rosalina-don-justino-optimized.jpg

kp-holland-rosalina-don-justino-optimized.jpg

385 ms

css

css

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

19 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

27 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

32 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

32 ms

foliage-hero-optimized.png

foliage-hero-optimized.png

389 ms

koppe-20210429_202-optimized.jpg

koppe-20210429_202-optimized.jpg

388 ms

hero-home-flowering.jpg

hero-home-flowering.jpg

191 ms

kp-holland-rosalina-don-justino-optimized.jpg

kp-holland-rosalina-don-justino-optimized.jpg

192 ms

Accessibility Review

greenex.com accessibility score

94

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-*] attributes do not match their roles

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

greenex.com 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 Greenex.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 Greenex.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

greenex.com

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