4.8 sec in total
438 ms
3.2 sec
1.1 sec
Visit rico.in now to see the best up-to-date Rico content for India and also check out these interesting facts you probably never knew about rico.in
Rico is a world-class & most trusted Home & Kitchen Appliances brand. Rico was the first company to introduce mixer grinders in India
Visit rico.inWe analyzed Rico.in page load time and found that the first response time was 438 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rico.in performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value7.4 s
4/100
25%
Value10.8 s
6/100
10%
Value9,380 ms
0/100
30%
Value0.885
3/100
15%
Value32.5 s
0/100
10%
438 ms
185 ms
47 ms
127 ms
45 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 60% of them (47 requests) were addressed to the original Rico.in, 9% (7 requests) were made to Youtube.com and 8% (6 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source App.engati.com.
Page size can be reduced by 349.2 kB (17%)
2.0 MB
1.7 MB
In fact, the total size of Rico.in main page is 2.0 MB. 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 a small number of websites need less resources to load. Javascripts take 760.1 kB which makes up the majority of the site volume.
Potential reduce by 338.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. 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 338.7 kB or 71% of the original size.
Potential reduce by 419 B
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. Rico images are well optimized though.
Potential reduce by 10.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 83 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. Rico.in has all CSS files already compressed.
Number of requests can be reduced by 26 (39%)
67
41
The browser has sent 67 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 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.rico.in
438 ms
js
185 ms
theme.scss.css
47 ms
jquery.min.js
127 ms
vendor.min.js
45 ms
stores.js
40 ms
nerdy_form_widget.js
139 ms
adsbygoogle.js
293 ms
js
180 ms
shopify-perf-kit-unstable.min.js
120 ms
option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js
139 ms
wow.min.js
143 ms
theme.min.js
139 ms
script-loader.js
144 ms
trekkie.storefront.72278931d43be9cf54de64f928f82f2eef1fa047.min.js
126 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
124 ms
shopify-boomerang-1.0.0.min.js
124 ms
8xfvtxcB1dI
339 ms
4Jk6GmSLLhc
430 ms
bjXvgwjMalk
479 ms
Logo_160x.jpg
303 ms
HP2207_Website_Banner_Dec22.jpg
308 ms
HP2207_Website_Mobile_Banner_Dec22.jpg
307 ms
Website_Banner_Juicer_JE1401_March23_67c6b366-77e7-444e-8741-db7adecc42a8.jpg
307 ms
Website_Mobile_Banner_Juicer_JE1401_March23_b2954b69-761e-4ee8-980b-1dedd31657ed.jpg
307 ms
spacer.png
303 ms
1_798ba02f-97d7-49ac-9095-993301a54733_50x.jpg
792 ms
Slide1_50x.jpg
788 ms
1_34c3bc3a-cdd6-46a7-baab-bbfb7db668e8_50x.jpg
394 ms
01_09b7f42b-cb96-4b64-b3a1-72cdc1acd20a_50x.jpg
362 ms
1_c84e99d4-9875-4292-8569-f36e4b39d686_50x.jpg
372 ms
HP2207InfographicsNov221_50x.jpg
395 ms
1_Without_Watts_50x.jpg
656 ms
1_ad59444d-a09a-4903-988d-49b10dcdeddc_50x.jpg
657 ms
Slide1_9369d73b-a5e9-4b06-849b-4e7c81bb23e0_50x.jpg
656 ms
240357_1_50x.jpg
945 ms
12_50x.png
786 ms
1_db470225-0203-4381-ad3c-4d851fb968f5_50x.jpg
788 ms
MG1907_50x.jpg
945 ms
Kitchen_Appliances_1fff2440-01ce-4e6e-a3b9-3491f4056e02_50x.jpg
788 ms
Heating_Appliances_3d34613b-ed38-4e73-9c82-dc0556fe765a_50x.jpg
946 ms
Home_Appliances_50x.jpg
790 ms
New_Launch_50x.jpg
790 ms
Juicer_Mid_Banner_20-4-2022_50x.jpg
944 ms
Spare_Parts_50x.jpg
945 ms
Spare_Parts_Mobile_50x.jpg
943 ms
montserrat_n4.cfce41a967758ce5a9b7d48daeb5b028fd977a9b.woff
1006 ms
montserrat_n3.f481a31eaff8b48749cc413f5c6990b1db3c9103.woff
989 ms
widget_18_08_2022.min.css
259 ms
icons.min.css
261 ms
pikaday_12_04_2021.min.css
295 ms
montserrat_n6.2c97c1a692c63ad09ab0635cb73b1939c5f417c0.woff
958 ms
montserrat_n7.78b0223375c94b39ce1af7e09a0225f2bb3d05f7.woff
954 ms
rico-india
337 ms
adorn-icons.woff
826 ms
roboto_n7.1babbb6a27f91b14216bafa40bf222e08f6999f4.woff
825 ms
roboto_n4.a512c7b68cd7f12c72e1a5fd58e7f7315c552e93.woff
920 ms
roboto_n3.fa321b1ddee0338f7cf3bfb01c364bbc1b6a419a.woff
920 ms
www.rico.in
1300 ms
show_ads_impl.js
680 ms
www-player.css
97 ms
www-embed-player.js
120 ms
base.js
166 ms
ad_status.js
521 ms
jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js
470 ms
embed.js
250 ms
id
157 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
225 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
227 ms
zrt_lookup.html
109 ms
ads
84 ms
widget.js
1391 ms
Create
299 ms
Create
304 ms
Create
392 ms
GenerateIT
145 ms
GenerateIT
136 ms
GenerateIT
17 ms
rico.in accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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.
rico.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
rico.in 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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rico.in 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 Rico.in 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.in
Open Graph data is detected on the main page of Rico. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: