2.6 sec in total
176 ms
2 sec
509 ms
Visit rico.com.br now to see the best up-to-date Rico content for Brazil and also check out these interesting facts you probably never knew about rico.com.br
Invista no Tesouro, CDB, LC, LCA, LCI, COE, CRI, CRA, Fundos, IPO, Futuros, Ações e Mini contratos. Confira os nossos investimentos e as vantagens Rico.
Visit rico.com.brWe analyzed Rico.com.br page load time and found that the first response time was 176 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
rico.com.br performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value9.5 s
0/100
25%
Value11.8 s
4/100
10%
Value7,190 ms
0/100
30%
Value0.037
100/100
15%
Value13.3 s
12/100
10%
176 ms
116 ms
112 ms
147 ms
147 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rico.com.br, 10% (8 requests) were made to Google.com and 7% (6 requests) were made to Rico.com.vc. The less responsive or slowest element that took the longest time to load (659 ms) relates to the external source Cdn.segment.com.
Page size can be reduced by 253.4 kB (54%)
469.7 kB
216.3 kB
In fact, the total size of Rico.com.br main page is 469.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. 70% of websites need less resources to load. Javascripts take 295.1 kB which makes up the majority of the site volume.
Potential reduce by 107.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 107.6 kB or 81% of the original size.
Potential reduce by 12.5 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, Rico needs image optimization as it can save up to 12.5 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 129.4 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 129.4 kB or 44% of the original size.
Potential reduce by 3.9 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. Rico.com.br needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 38% of the original size.
Number of requests can be reduced by 54 (79%)
68
14
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rico. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and as a result speed up the page load time.
www.rico.com.vc
176 ms
gtm.js
116 ms
51dbf511ad04fda3c040.css
112 ms
c98d3ec1bbb4bc50adc4.css
147 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
147 ms
webpack-b11ba5d94b7ccae9d584.js
112 ms
framework-895f067827ebe11ffe45.js
398 ms
main-62b8caa3ccc47893b147.js
315 ms
_app-9a0b62908b6544a86473.js
393 ms
779-700b79091175b1ef3ea0.js
394 ms
354-c96133fe16221366e7a7.js
314 ms
home-186c34863dfcecde7fca.js
313 ms
_buildManifest.js
395 ms
_ssgManifest.js
394 ms
superhero.png
99 ms
MnFRs3KgAC
52 ms
Gr%C3%A1ficoColado-3-e1659582269436.png
242 ms
MnFRs3KgAC
450 ms
optimize.js
221 ms
analytics.js
202 ms
conversion_async.js
381 ms
bat.js
374 ms
uwt.js
409 ms
tfa.js
403 ms
fbevents.js
401 ms
ktag.js
398 ms
embed.js
399 ms
kenshoo.js
398 ms
events.js
560 ms
analytics.min.js
659 ms
js
248 ms
activityi;src=9143205;type=rc_pages;cat=rico-0;ord=4494427717151;gtm=2wg9s0;auiddc=367081453.1664553251;u1=https%3A%2F%2Fwww.rico.com.vc%2F;u3=false;u4=undefined;u7=undefined;u20=undefined;u13=undefined;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
478 ms
activityi;src=9143205;type=rc_pages;cat=rico-001;ord=false--20220930;gtm=2wg9s0;auiddc=367081453.1664553251;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
484 ms
RicoSans-Bold.ttf
456 ms
optimize-dyn.js
183 ms
collect
344 ms
collect
135 ms
317 ms
405 ms
MnFRs3KgAC
240 ms
adsct
222 ms
adsct
221 ms
448392525363196
86 ms
json
149 ms
v1
105 ms
ga-audiences
67 ms
MnFRs3KgAC
164 ms
polyfill.min.js
49 ms
src=9143205;type=rc_pages;cat=rico-0;ord=4494427717151;gtm=2wg9s0;auiddc=367081453.1664553251;u1=https%3A%2F%2Fwww.rico.com.vc%2F;u3=false;u4=undefined;u7=undefined;u20=undefined;u13=undefined;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
29 ms
22 ms
cds-pips.js
16 ms
conversion.js
101 ms
pips.taboola.com
97 ms
src=9143205;type=rc_pages;cat=rico-001;ord=false--20220930;gtm=2wg9s0;auiddc=367081453.1664553251;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
59 ms
settings
6 ms
48 ms
870.bundle.323974846b6d45afb45e.js
22 ms
ajs-destination.bundle.35a8f6f19959bf2f455f.js
21 ms
22 ms
40 ms
schemaFilter.bundle.debb169c1abb431faaa6.js
7 ms
31 ms
6765cb3cf169443c119b.js
2 ms
86 ms
p
392 ms
20 ms
https:/
1 ms
MnFRs3KgAC
142 ms
61 ms
30 ms
generic1664295546709.js
49 ms
activityi;src=9143205;type=rc_pages;cat=rico-0;ord=8872815394402;gtm=2wg9s0;auiddc=367081453.1664553251;u1=https%3A%2F%2Fwww.rico.com.vc%2F;u3=819723042.1664553251;u4=undefined;u7=undefined;u20=undefined;u13=undefined;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
61 ms
activityi;src=9143205;type=rc_pages;cat=rico-001;ord=819723042.1664553251--20220930;gtm=2wg9s0;auiddc=367081453.1664553251;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
45 ms
17 ms
src=9143205;type=rc_pages;cat=rico-001;ord=819723042.1664553251--20220930;gtm=2wg9s0;auiddc=*;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
38 ms
24 ms
src=9143205;type=rc_pages;cat=rico-0;ord=8872815394402;gtm=2wg9s0;auiddc=*;u1=https%3A%2F%2Fwww.rico.com.vc%2F;u3=819723042.1664553251;u4=undefined;u7=undefined;u20=undefined;u13=undefined;~oref=https%3A%2F%2Fwww.rico.com.vc%2F
44 ms
42 ms
65 ms
46 ms
26 ms
rico.com.br accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
rico.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
rico.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rico.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Rico.com.br 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.
rico.com.br
Open Graph description is not detected on the main page of Rico. 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: