Tools & Wizards About Us
growwer.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

growwer.com

Growwer: Online reputation and link building tool to promote your business

Page Load Speed

5.3 sec in total

First Response

729 ms

Resources Loaded

3.6 sec

Page Rendered

980 ms

growwer.com screenshot

About Website

Visit growwer.com now to see the best up-to-date Growwer content for Pakistan and also check out these interesting facts you probably never knew about growwer.com

Discover Growwer, an automatic and free tool to promote your company in blogs and newspapers where your customers are waiting for you.

Visit growwer.com

Key Findings

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

Performance Metrics

growwer.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

growwer.com

729 ms

autoptimize_single_8f3b09e9f08e9d37b02df511c1eaa76f.css

9 ms

autoptimize_single_8772098d82c2322965b2ef03f90e7468.css

964 ms

jquery.min.js

457 ms

simple-banner.js

18 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 98% of them (40 requests) were addressed to the original Growwer.com, 2% (1 request) were made to I.ytimg.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Growwer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.3 kB (25%)

Content Size

924.9 kB

After Optimization

689.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 225.4 kB

  • Original 269.9 kB
  • After minification 269.3 kB
  • After compression 44.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 225.4 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 9.6 kB

  • Original 651.0 kB
  • After minification 641.4 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. Growwer images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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

-11%

Potential reduce by 361 B

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 3.0 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. Growwer.com needs all CSS files to be minified and compressed as it can save up to 361 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

growwer.com

growwer.com

729 ms

autoptimize_single_8f3b09e9f08e9d37b02df511c1eaa76f.css

autoptimize_single_8f3b09e9f08e9d37b02df511c1eaa76f.css

9 ms

autoptimize_single_8772098d82c2322965b2ef03f90e7468.css

autoptimize_single_8772098d82c2322965b2ef03f90e7468.css

964 ms

jquery.min.js

jquery.min.js

457 ms

simple-banner.js

simple-banner.js

18 ms

email-decode.min.js

email-decode.min.js

14 ms

wpa.js

wpa.js

362 ms

form.js

form.js

23 ms

menu.min.js

menu.min.js

21 ms

lazyload.min.js

lazyload.min.js

31 ms

shared.js

shared.js

30 ms

promo-banner.js

promo-banner.js

38 ms

cookies-notice.js

cookies-notice.js

40 ms

locale-switcher-modal.js

locale-switcher-modal.js

36 ms

chrome_icon-growwer-03-1.png

chrome_icon-growwer-03-1.png

431 ms

youtube.svg

youtube.svg

61 ms

hqdefault.jpg

hqdefault.jpg

106 ms

growwer-logo.png

growwer-logo.png

16 ms

portada-fondo-1.png

portada-fondo-1.png

343 ms

portada-fondo-2.png

portada-fondo-2.png

344 ms

portada-fondo-3.png

portada-fondo-3.png

14 ms

portada-fondo-4.png

portada-fondo-4.png

11 ms

amazon-growwer-1.png

amazon-growwer-1.png

352 ms

Heineken-growwer-1.png

Heineken-growwer-1.png

358 ms

binance-growwer-2.png

binance-growwer-2.png

379 ms

mercado-libre.png

mercado-libre.png

701 ms

edreams-growwer.png

edreams-growwer.png

689 ms

mbe-growwer.png

mbe-growwer.png

720 ms

growwers-annual-link-building-report-scaled.jpg

growwers-annual-link-building-report-scaled.jpg

364 ms

listado-medios-online.png

listado-medios-online.png

918 ms

section-1-1024x832.png

section-1-1024x832.png

1025 ms

esteve_castells-150x150-1.png

esteve_castells-150x150-1.png

827 ms

nacho_mascort-150x150-1.png

nacho_mascort-150x150-1.png

1117 ms

ivan_garcia-150x150-1.png

ivan_garcia-150x150-1.png

1057 ms

chrome_icon.png

chrome_icon.png

1070 ms

growwer-chrome-07.png

growwer-chrome-07.png

1470 ms

logo-vanguardia.svg

logo-vanguardia.svg

930 ms

logo-emprendedores.svg

logo-emprendedores.svg

1295 ms

logo-cloudflare.svg

logo-cloudflare.svg

1369 ms

section-3-1024x832.png

section-3-1024x832.png

1722 ms

Premio-internet-Growwer-english-1.png

Premio-internet-Growwer-english-1.png

1512 ms

Accessibility Review

growwer.com accessibility score

93

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

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

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

High

Image elements do not have [alt] attributes

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

growwer.com

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