Tools & Wizards About Us
wegrow.company screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% 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

  • 93

    SEO

    Google-friendlier than
    83% of websites

wegrow.company

Scaling Business | WeGrow - Scaling business as a service | Amsterdam

Page Load Speed

1.6 sec in total

First Response

284 ms

Resources Loaded

1.3 sec

Page Rendered

59 ms

wegrow.company screenshot

About Website

Visit wegrow.company now to see the best up-to-date We Grow content and also check out these interesting facts you probably never knew about wegrow.company

weGrow is scaling business as a service. We are an international growth hub helping tech startups & scale-ups to achieve fast & sustainable international growth within Europe.

Visit wegrow.company

Key Findings

We analyzed Wegrow.company page load time and found that the first response time was 284 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 30% of websites can load faster.

Performance Metrics

wegrow.company performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

www.wegrow.company

284 ms

minified.js

31 ms

focus-within-polyfill.js

66 ms

polyfill.min.js

68 ms

thunderbolt-commons.e7839053.bundle.min.js

60 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wegrow.company, 35% (15 requests) were made to Static.wixstatic.com and 28% (12 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (734 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 502.6 kB (52%)

Content Size

975.7 kB

After Optimization

473.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wegrow.company main page is 975.7 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. 45% of websites need less resources to load. HTML takes 558.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 444.2 kB

  • Original 558.8 kB
  • After minification 557.0 kB
  • After compression 114.6 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 444.2 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 10.3 kB

  • Original 112.7 kB
  • After minification 102.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. We Grow images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 304.3 kB
  • After minification 304.3 kB
  • After compression 256.1 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 48.1 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Grow. 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

www.wegrow.company

www.wegrow.company

284 ms

minified.js

minified.js

31 ms

focus-within-polyfill.js

focus-within-polyfill.js

66 ms

polyfill.min.js

polyfill.min.js

68 ms

thunderbolt-commons.e7839053.bundle.min.js

thunderbolt-commons.e7839053.bundle.min.js

60 ms

main.760485a2.bundle.min.js

main.760485a2.bundle.min.js

101 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

59 ms

lodash.min.js

lodash.min.js

102 ms

react.production.min.js

react.production.min.js

94 ms

react-dom.production.min.js

react-dom.production.min.js

102 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

100 ms

0f2011_530cdeee8f2342fd8646467c5420dc65~mv2.png

0f2011_530cdeee8f2342fd8646467c5420dc65~mv2.png

239 ms

bundle.min.js

bundle.min.js

56 ms

wG.png

wG.png

174 ms

Screenshot%202023-07-05%20at%2012_10_20.png

Screenshot%202023-07-05%20at%2012_10_20.png

206 ms

Screenshot%202023-07-05%20at%2012_10_28.png

Screenshot%202023-07-05%20at%2012_10_28.png

216 ms

Screenshot%202023-07-15%20at%2019_51_37.png

Screenshot%202023-07-15%20at%2019_51_37.png

172 ms

1ca4f1_1bbd31d2596e4de7919c745ab5ef3eab~mv2.png

1ca4f1_1bbd31d2596e4de7919c745ab5ef3eab~mv2.png

224 ms

1ca4f1_3becacd46f5e465298a85c64e6e82b75~mv2.png

1ca4f1_3becacd46f5e465298a85c64e6e82b75~mv2.png

385 ms

1ca4f1_0aba58644c284517ad7ea98aa36d6c45~mv2.png

1ca4f1_0aba58644c284517ad7ea98aa36d6c45~mv2.png

343 ms

1ca4f1_605270772573437bad3b03d3343e014c~mv2.png

1ca4f1_605270772573437bad3b03d3343e014c~mv2.png

370 ms

1ca4f1_ec9a01fe27924289bb8eafb710b8891b~mv2.png

1ca4f1_ec9a01fe27924289bb8eafb710b8891b~mv2.png

365 ms

1ca4f1_5b366c00e6b94a70a5555b5634b2d653~mv2.png

1ca4f1_5b366c00e6b94a70a5555b5634b2d653~mv2.png

405 ms

1ca4f1_04dfd0c058054fb5b559c05b3bbdb3c9~mv2.png

1ca4f1_04dfd0c058054fb5b559c05b3bbdb3c9~mv2.png

365 ms

1ca4f1_1fac44bb48714130bbfa4f29ede4a0e2~mv2.png

1ca4f1_1fac44bb48714130bbfa4f29ede4a0e2~mv2.png

482 ms

1ca4f1_abac05abaa284bf6953b038105f472ed~mv2.png

1ca4f1_abac05abaa284bf6953b038105f472ed~mv2.png

734 ms

109 ms

114 ms

108 ms

110 ms

111 ms

108 ms

135 ms

145 ms

139 ms

137 ms

136 ms

134 ms

file.woff

file.woff

339 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

24 ms

deprecation-style.v5.css

deprecation-style.v5.css

10 ms

right-arrow.svg

right-arrow.svg

10 ms

Accessibility Review

wegrow.company accessibility score

97

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

Links do not have a discernible name

Best Practices

wegrow.company 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

Page has valid source maps

SEO Factors

wegrow.company SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Wegrow.company 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 Wegrow.company 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

wegrow.company

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