Tools & Wizards About Us
growingio.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

growingio.com

GrowingIO 官网｜全域全场景智能易用的分析云

Page Load Speed

3.8 sec in total

First Response

670 ms

Resources Loaded

3.1 sec

Page Rendered

80 ms

growingio.com screenshot

About Website

Click here to check amazing GrowingIO content for China. Otherwise, check out these important facts you probably never knew about growingio.com

GrowingIO分析云是基于用户行为的新一代数据分析产品，提供全球领先的数据采集和分析技术。企业无需在网站或app中埋点，即可获取并分析全面、实时的用户行为数据，以优化产品体验，实现精益化运营，用数据驱动用户和营收的增长。

Visit growingio.com

Key Findings

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

growingio.com performance score

0

Network Requests Diagram

growingio.com

670 ms

www.growingio.com

1764 ms

fd9d1056-6ec2d37f48aef60e.js

430 ms

8069-86d7873a217197f5.js

847 ms

main-app-81efa7dd90030e04.js

639 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Growingio.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Growingio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.6 kB (51%)

Content Size

309.9 kB

After Optimization

151.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Growingio.com main page is 309.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. Only 10% of websites need less resources to load. HTML takes 160.2 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 110.2 kB

  • Original 160.2 kB
  • After minification 160.2 kB
  • After compression 50.0 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 110.2 kB or 69% of the original size.

Image Optimization

-6%

Potential reduce by 3.8 kB

  • Original 66.2 kB
  • After minification 62.3 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. GrowingIO images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 44.6 kB

  • Original 83.6 kB
  • After minification 83.6 kB
  • After compression 39.0 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 44.6 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (88%)

Requests Now

8

After Optimization

1

  • JavaScript

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

Network Requests Diagram

growingio.com

growingio.com

670 ms

www.growingio.com

www.growingio.com

1764 ms

fd9d1056-6ec2d37f48aef60e.js

fd9d1056-6ec2d37f48aef60e.js

430 ms

8069-86d7873a217197f5.js

8069-86d7873a217197f5.js

847 ms

main-app-81efa7dd90030e04.js

main-app-81efa7dd90030e04.js

639 ms

5250-091cb5b21dba6b19.js

5250-091cb5b21dba6b19.js

675 ms

1749-6d57c93313692557.js

1749-6d57c93313692557.js

676 ms

global-error-b9e9138ca36bb37e.js

global-error-b9e9138ca36bb37e.js

639 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

646 ms

webpack-a5b8447f94603e9c.js

webpack-a5b8447f94603e9c.js

855 ms

SEO Factors

growingio.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Growingio.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Growingio.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

growingio.com

Open Graph description is not detected on the main page of GrowingIO. 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: