2.9 sec in total
93 ms
2 sec
723 ms
Click here to check amazing Rich content for Vietnam. Otherwise, check out these important facts you probably never knew about rich.com
Rich's inspires possibilities with high quality, wholesale food products and ingredients that can be found in commercial kitchens in all corners of the globe. Serving foodservice, in-store bakery...
Visit rich.comWe analyzed Rich.com page load time and found that the first response time was 93 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
rich.com performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value26.7 s
0/100
25%
Value8.8 s
15/100
10%
Value820 ms
35/100
30%
Value0.037
100/100
15%
Value18.9 s
3/100
10%
93 ms
28 ms
17 ms
50 ms
47 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rich.com, 2% (3 requests) were made to Fastly-cloud.typenetwork.com and 1% (1 request) were made to Cloud.typenetwork.com. The less responsive or slowest element that took the longest time to load (965 ms) relates to the external source Richs.com.
Page size can be reduced by 116.8 kB (3%)
3.7 MB
3.6 MB
In fact, the total size of Rich.com main page is 3.7 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. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 114.3 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 114.3 kB or 84% of the original size.
Potential reduce by 0 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. Rich images are well optimized though.
Potential reduce by 0 B
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 2.5 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. Rich.com needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 90% of the original size.
Number of requests can be reduced by 95 (67%)
141
46
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rich. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 56 to 1 for CSS and as a result speed up the page load time.
www.richs.com
93 ms
fontface.css
28 ms
style.min.css
17 ms
classic-themes.min.css
50 ms
ivory-search.min.css
47 ms
main.css
55 ms
blog_custom.css
34 ms
header-blog.css
88 ms
title-text1-blog.css
101 ms
main-blog.css
52 ms
single-blog.css
92 ms
encabezado-blog.css
89 ms
banner-n.css
90 ms
video-n.css
100 ms
galeria-n.css
98 ms
slider-n.css
97 ms
slidertwo-n.css
100 ms
sliderthree-n.css
96 ms
sliderfour-n.css
112 ms
sliderfive-n.css
111 ms
sliderseven-n.css
108 ms
highlights-n.css
114 ms
text-video-n.css
115 ms
banner2-p.css
116 ms
banner3.css
127 ms
banner4-p.css
127 ms
banner5-p.css
130 ms
banner6-p.css
135 ms
banner7-p.css
133 ms
banner-p.css
133 ms
cards2-p.css
142 ms
collage2-p.css
146 ms
collage-p.css
144 ms
contact-p.css
148 ms
contact-forms-p.css
146 ms
contact-richs-p.css
159 ms
distribuidores-p.css
159 ms
optimize.js
80 ms
forms2.min.js
130 ms
mapa-p.css
156 ms
marketo-form1-p.css
158 ms
simple-banner2-p.css
138 ms
simple-banner-p.css
127 ms
slider-p.css
134 ms
tarjetas-p.css
142 ms
text-image1-p.css
98 ms
text-image2-n.css
111 ms
menu-n.css
109 ms
cards3-n.css
103 ms
collage3-n.css
105 ms
slidersix-n.css
106 ms
banner8-n.css
118 ms
text-with-button-n.css
114 ms
data-banner-n.css
115 ms
banner9-n.css
119 ms
bannerour-n.css
115 ms
see-all-destinations2.css
110 ms
mega_menu_2.css
137 ms
popupE.css
117 ms
jquery.min.js
116 ms
jquery-migrate.min.js
121 ms
main.js
262 ms
slider2.js
110 ms
hero-height.js
115 ms
btn-player.js
201 ms
slider-one.js
195 ms
slider-two.js
191 ms
slider-seven.js
195 ms
circles_six.js
189 ms
slider-six.js
187 ms
circles.js
228 ms
slider-three.js
185 ms
galeria-n.js
225 ms
slider-five.js
214 ms
highlights-n.js
214 ms
sliderfour-n.js
213 ms
data-banner-n.js
212 ms
cards3-n.js
212 ms
simple-banner2-p.js
206 ms
popupE.js
204 ms
ivory-search.min.js
202 ms
mobile_menu_scroll.js
188 ms
mega_menu.js
223 ms
geobotton_controller.js
221 ms
gtm.js
151 ms
footer-logo.png
92 ms
richs-logo.svg
92 ms
red-arrow-img.png
592 ms
white-arrow-icon.png
561 ms
bettercreme.png
621 ms
whip-topping.png
559 ms
on-top.png
563 ms
IceHot-Logo-.png
592 ms
Our-Specialty-BAKE-HOUSE-Logo-R.png
559 ms
Our-Specialty_treat-shop_tagline.png
584 ms
Gold-Label-logo-color-01.png
726 ms
versatie.png
728 ms
tres-riches.png
738 ms
Large-Prowhip_Logo_Color-Color-Pillow.jpg
614 ms
USC_Web-SeaPak_Logo_2023_PMS.jpeg
614 ms
FarmRich-Logo-DesktopMobile.png
644 ms
MicrosoftTeams-image-17.png
632 ms
Christie-Cookie-Logo-DesktopMobile.png
632 ms
Medium-SeaPak_Moreys_Logo_Color_WhtBkgrnd.jpeg
649 ms
Freal-Logo-DesktopMobile.png
646 ms
JD_Logo.jpg
664 ms
byrons-logo-2.png
628 ms
icon-close.png
792 ms
long-arrow-icon.svg
648 ms
proximo.png
797 ms
long-red-%20arrow-icon.svg
673 ms
chevron-icon.svg
691 ms
proximo-red.png
887 ms
hero-img-1.png
700 ms
red-arrow-icon.svg
706 ms
red-right-arrow.svg
709 ms
possibilities-card.png
892 ms
37321-_PE_Product-Beauty-Desktop.jpeg
720 ms
fa-solid-900.woff
903 ms
1c78_vdef_baa6e6f83f_5151.woff
442 ms
1c70_vdef_baa6e6f83f_5153.woff
442 ms
1c75_vdef_baa6e6f83f_5155.woff
441 ms
fa-regular-400.woff
916 ms
AlrightSans-Black.ttf
770 ms
pizza-img.jpg
780 ms
Soft-Whip-Tile-1.png
965 ms
bynder-embed.js
96 ms
AlrightSans-Medium.ttf
326 ms
AlrightSans-Regular.ttf
351 ms
39F65B_0_0.woff
640 ms
cf-visitor
390 ms
region
691 ms
1-9537-Desktop-1.jpg
411 ms
159 ms
23548_Product-Beauty_Styled-2-Desktop.jpeg
404 ms
Richs-Brand-video-desktop-scaled.jpeg
404 ms
monuments.svg
413 ms
Category-home-tile-culinary-solutions.jpg
436 ms
Category-home-tile-pizza.jpg
421 ms
Category-home-tile-Beverage.jpg
422 ms
Category-home-tile-desserts-cheesecake.jpg
412 ms
Category-home-tile-Bakery.jpg
407 ms
Category-home-tile-cake-icings-sweet-starters.jpg
407 ms
footer-bg.jpg
390 ms
footer-card.png
570 ms
redd-arrow-icon.svg
369 ms
facebook-icon.png
540 ms
instagram-icon.png
524 ms
linkedin-icon.png
537 ms
x-icon.png
662 ms
global-markets-img-1.jpg
518 ms
global-markets-usa.jpg
20 ms
global-markets-img-1.jpg
17 ms
rich.com 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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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 IDs are not unique
rich.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
rich.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Rich.com 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 Rich.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.
rich.com
Open Graph description is not detected on the main page of Rich. 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: