6.5 sec in total
528 ms
4.7 sec
1.2 sec
Visit grow.ly now to see the best up-to-date GROW content for Spain and also check out these interesting facts you probably never knew about grow.ly
Grow.ly es una plataforma de crowdlending autorizada por CNMV donde multitud de inversores prestan a pymes obteniendo mayor rentabilidad por sus ahorros.
Visit grow.lyWe analyzed Grow.ly page load time and found that the first response time was 528 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
grow.ly performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.3 s
21/100
25%
Value10.2 s
8/100
10%
Value4,310 ms
1/100
30%
Value0.256
48/100
15%
Value17.9 s
3/100
10%
528 ms
1401 ms
279 ms
173 ms
250 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 76% of them (52 requests) were addressed to the original Grow.ly, 6% (4 requests) were made to Static.olark.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Grow.ly.
Page size can be reduced by 107.0 kB (11%)
945.9 kB
838.9 kB
In fact, the total size of Grow.ly main page is 945.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. 60% of websites need less resources to load. Images take 804.2 kB which makes up the majority of the site volume.
Potential reduce by 34.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 9.4 kB, which is 22% 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 34.7 kB or 80% of the original size.
Potential reduce by 63.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. GROW images are well optimized though.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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. Grow.ly has all CSS files already compressed.
Number of requests can be reduced by 16 (26%)
62
46
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
grow.ly
528 ms
www.grow.ly
1401 ms
all.css
279 ms
css
173 ms
growly
250 ms
video-js.css
143 ms
font-awesome.min.css
183 ms
beginning
364 ms
video.js
189 ms
jquery.min.js
161 ms
validation
920 ms
end
1192 ms
ValidationMessages
640 ms
index.js
639 ms
__utm.gif
238 ms
sello70_75.gif
1238 ms
glyphicons-442-phone-alt.png
317 ms
growly-logo.png
317 ms
avatar-37.png
318 ms
img01.png
2085 ms
g-step1.png
399 ms
g-step2.png
535 ms
g-step3.png
665 ms
g-step4.png
525 ms
5a051700a98cdb881e252523df88caf8.png
565 ms
7f0857c3a6bac8bf8a2e9c7cfc5f9df1.png
637 ms
52e4799521a17264020fc97966859863.png
665 ms
a18907178e7f5d282aab11ecacf0acce.png
687 ms
b265e512e1d54e206fd1041d1e8f798b.png
1172 ms
682fa5a8ed7ea570dcdbf6863b9a59f0.png
1218 ms
5db755694e21da2e2bdc7352b5840fab.png
1217 ms
img02.png
1308 ms
overlay.png
1216 ms
c90614f1f42b5bf56bfd5d70348add25.png
1233 ms
c1c7b15c69a5d9a8004f216e6969e5e6.png
1306 ms
asnef_empresas.png
1307 ms
barrabes_sqr.png
1317 ms
AF-FINAN%C3%87AMENT.png
1318 ms
OT2015_medal_finalist_en.png
1433 ms
logo-icon-4.png
1433 ms
e-certificada.jpg
1436 ms
Banners_Acelera.jpg
1435 ms
sprite.png
1434 ms
loading4.gif
2119 ms
analytics.js
8 ms
fa-brands-400.woff
90 ms
glyphicons-regular.woff
1941 ms
collect
16 ms
loader0.js
361 ms
likelySubtags.json
1130 ms
currencyData.json
1146 ms
numberingSystems.json
1144 ms
ordinals.json
1168 ms
plurals.json
1198 ms
timeData.json
1212 ms
weekData.json
1201 ms
ca-gregorian.json
1211 ms
currencies.json
1232 ms
dateFields.json
1229 ms
numbers.json
1215 ms
timeZoneNames.json
1215 ms
units.json
1248 ms
ajax-loader.gif
1081 ms
slick.woff
1046 ms
app.js
38 ms
6074-189-10-5544.js
29 ms
c
67 ms
application2.js
127 ms
grow.ly 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 progressbar elements do not have accessible names.
[aria-*] attributes do not have valid values
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.
grow.ly 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
grow.ly SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grow.ly can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Grow.ly 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.
grow.ly
Open Graph description is not detected on the main page of GROW. 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: