Tools & Wizards About Us
growing.com screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

growing.com

Growing dot com - Hosting Neuroscience, Photography and other sites since 1995

Page Load Speed

1.9 sec in total

First Response

407 ms

Resources Loaded

1.3 sec

Page Rendered

242 ms

growing.com screenshot

About Website

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

Growing dot com - Hosting Neuroscience, Photography and other sites since 1995. Most recently the official websites for theta-alpha-gamma synchrony neurofeedback (TAG Sync) and Live Complexity Trainin...

Visit growing.com

Key Findings

We analyzed Growing.com page load time and found that the first response time was 407 ms and then it took 1.5 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

growing.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

82/100

10%

Network Requests Diagram

growing.com

407 ms

xr_main.css

153 ms

custom_styles.css

161 ms

xr_text.css

152 ms

roe.js

305 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 96% of them (44 requests) were addressed to the original Growing.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (501 ms) belongs to the original domain Growing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.3 kB (40%)

Content Size

261.9 kB

After Optimization

157.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Growing.com main page is 261.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 133.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 15.6 kB

  • Original 18.8 kB
  • After minification 18.6 kB
  • After compression 3.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 15.6 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 14.4 kB

  • Original 133.4 kB
  • After minification 119.0 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. Obviously, Growing needs image optimization as it can save up to 14.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 45.6 kB

  • Original 77.3 kB
  • After minification 76.6 kB
  • After compression 31.7 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 45.6 kB or 59% of the original size.

CSS Optimization

-89%

Potential reduce by 28.7 kB

  • Original 32.4 kB
  • After minification 26.5 kB
  • After compression 3.6 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. Growing.com needs all CSS files to be minified and compressed as it can save up to 28.7 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (9%)

Requests Now

45

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

growing.com

growing.com

407 ms

xr_main.css

xr_main.css

153 ms

custom_styles.css

custom_styles.css

161 ms

xr_text.css

xr_text.css

152 ms

roe.js

roe.js

305 ms

replaceMobileFonts.js

replaceMobileFonts.js

161 ms

xr_all.css

xr_all.css

218 ms

ani.css

ani.css

299 ms

ga.js

ga.js

57 ms

207.png

207.png

120 ms

222.png

222.png

123 ms

208.png

208.png

122 ms

223.png

223.png

122 ms

209.png

209.png

122 ms

224.png

224.png

119 ms

437.png

437.png

171 ms

450.png

450.png

171 ms

438.png

438.png

173 ms

309.png

309.png

169 ms

439.jpg

439.jpg

169 ms

440.png

440.png

168 ms

452.png

452.png

235 ms

297.png

297.png

234 ms

442.png

442.png

234 ms

453.png

453.png

237 ms

443.png

443.png

238 ms

495.png

495.png

242 ms

505.png

505.png

304 ms

496.png

496.png

300 ms

506.png

506.png

304 ms

497.jpg

497.jpg

308 ms

456.png

456.png

305 ms

465.png

465.png

310 ms

457.png

457.png

365 ms

466.png

466.png

367 ms

458.png

458.png

369 ms

517.png

517.png

376 ms

460.png

460.png

376 ms

469.png

469.png

377 ms

461.png

461.png

429 ms

470.png

470.png

432 ms

323.png

323.png

436 ms

513.png

513.png

444 ms

520.png

520.png

443 ms

514.jpg

514.jpg

501 ms

__utm.gif

__utm.gif

14 ms

Accessibility Review

growing.com accessibility score

100

Accessibility Issues

Best Practices

growing.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

growing.com SEO score

86

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

growing.com

Open Graph description is not detected on the main page of Growing. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: