64.9 sec in total
3 sec
61.4 sec
448 ms
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.comWe analyzed Growingio.com page load time and found that the first response time was 3 sec and then it took 61.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
growingio.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value9.0 s
1/100
25%
Value13.0 s
2/100
10%
Value170 ms
93/100
30%
Value0
100/100
15%
Value10.0 s
27/100
10%
3027 ms
2850 ms
15548 ms
19999 ms
12214 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 85% of them (39 requests) were addressed to the original Growingio.com, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Growingio.com.
Page size can be reduced by 60.2 kB (36%)
165.5 kB
105.4 kB
In fact, the total size of Growingio.com main page is 165.5 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. 25% of websites need less resources to load. Javascripts take 83.6 kB which makes up the majority of the site volume.
Potential reduce by 11.7 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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.7 kB or 74% of the original size.
Potential reduce by 3.8 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.
Potential reduce by 44.6 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.
Number of requests can be reduced by 7 (18%)
40
33
The browser has sent 40 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.
growingio.com
3027 ms
growingio.com
2850 ms
www.growingio.com
15548 ms
61633099e88eb821dbf99ffaf0378a7b-jquery-1.11.3.min.js
19999 ms
ca726471ce1f9ce047d33ab9e6f3d785-bootstrap.js
12214 ms
008f852533481b69828876ed93332411-jquery.easing.min.js
1355 ms
a03d233ff2cba8f7d460c9b9699d4021-home.js
1360 ms
2493ffbb288ad3bbcf22b1cbcffbc245-retina.min.js
1772 ms
ca30257e7ce2f6c1cd6a60ec53450268-site.css
20002 ms
762436d85ab1dfc6f5a6d29bc872846b-index.js
2101 ms
vds-gate.js
3576 ms
analytics.js
113 ms
hm.js
907 ms
feature-collection.png
351 ms
feature-analyze.png
378 ms
user-segmentation.png
362 ms
user-retention.png
378 ms
tag-management.png
1406 ms
realtime-analyze.png
16913 ms
conversion-funnel.png
1499 ms
cohort-retention.png
3152 ms
channel-analyze.png
19974 ms
liepin.png
1882 ms
liepin-logo-sm.png
5015 ms
huanxin.png
5055 ms
easemob-logo-sm.png
2665 ms
xiaoshouyi.png
3615 ms
xiaoshouyi-logo-sm.png
4006 ms
youzan-logo.png
4050 ms
beisen-logo.png
4449 ms
xiaoshouyi-logo.png
8866 ms
ucloud-logo.png
4896 ms
douban-logo.png
5329 ms
liepin-logo.png
10530 ms
36kr-logo.png
6124 ms
highpin-logo.png
5703 ms
easemob-logo.png
6054 ms
fangcloud-logo.png
7665 ms
logo_other.png
16416 ms
ico_zhihu.png
8106 ms
ico_sina.png
9680 ms
erweima.jpg
13037 ms
collect
12 ms
hm.gif
226 ms
pv
4097 ms
action
3745 ms
growingio.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
growingio.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
growingio.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
ZH
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 it matches the claimed language. 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.
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: