Tools & Wizards About Us

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

growerline.com

Growerline: grow shop a Pomezia (Roma) per coltivare indoor e outdoor

Page Load Speed

7 sec in total

First Response

312 ms

Resources Loaded

6.2 sec

Page Rendered

484 ms

About Website

Click here to check amazing Growerline content for Italy. Otherwise, check out these important facts you probably never knew about growerline.com

Growerline è il tuo grow shop di fiducia a Pomezia (Roma) dal 2007. Solo i migliori prodotti per coltivare indoor, idroponica, e grow box delle migliori marche, ogni mese offerte grower!

Visit growerline.com

Key Findings

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

Performance Metrics

growerline.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

growerline.com

312 ms

1651 ms

uc.js

44 ms

woocommerce-gift-system.css

336 ms

front.min.css

314 ms

Our browser made a total of 141 requests to load all elements on the main page. We found that 97% of them (137 requests) were addressed to the original Growerline.com, 1% (1 request) were made to Consent.cookiebot.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Growerline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 548.0 kB (22%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-83%

Potential reduce by 392.7 kB

  • Original 474.1 kB
  • After minification 460.4 kB
  • After compression 81.4 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 392.7 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 67.5 kB

  • Original 1.9 MB
  • After minification 1.8 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. Growerline images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 87.9 kB

  • Original 113.2 kB
  • After minification 113.2 kB
  • After compression 25.3 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 87.9 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

136

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

growerline.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

growerline.com SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Growerline.com can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it does not match the claimed English language. Our system also found out that Growerline.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 Growerline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: