6.3 sec in total
1.6 sec
4.3 sec
305 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 1.6 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rich.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value12.1 s
0/100
25%
Value10.3 s
8/100
10%
Value4,240 ms
1/100
30%
Value0.033
100/100
15%
Value18.5 s
3/100
10%
1613 ms
111 ms
19 ms
29 ms
118 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rich.com, 49% (65 requests) were made to Richs.com and 15% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Rich.com.
Page size can be reduced by 1.8 MB (41%)
4.3 MB
2.5 MB
In fact, the total size of Rich.com main page is 4.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 156.8 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 156.8 kB or 78% of the original size.
Potential reduce by 167.2 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. Rich images are well optimized though.
Potential reduce by 948.8 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 948.8 kB or 69% of the original size.
Potential reduce by 492.8 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 492.8 kB or 88% of the original size.
Number of requests can be reduced by 80 (62%)
129
49
The browser has sent 129 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 40 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
rich.com
1613 ms
www.richs.com
111 ms
wp-emoji-release.min.js
19 ms
layerslider.css
29 ms
css
118 ms
settings.css
19 ms
normalize.css
53 ms
rt-css-framework.css
75 ms
fontello.css
77 ms
jackbox.min.css
77 ms
style.css
52 ms
owl.carousel.css
79 ms
flexslider.css
81 ms
progression-player.css
84 ms
skin-minimal-light.css
80 ms
isotope.css
81 ms
colortip-1.0-jquery.css
82 ms
animate.css
93 ms
orange-style.css
96 ms
css
124 ms
css
131 ms
css
133 ms
css
124 ms
style.css
97 ms
greensock.js
104 ms
jquery.js
96 ms
jquery-migrate.min.js
101 ms
layerslider.kreaturamedia.jquery.js
101 ms
layerslider.transitions.js
102 ms
jquery.themepunch.tools.min.js
108 ms
jquery.themepunch.revolution.min.js
107 ms
modernizr.min.js
103 ms
tabs.js
102 ms
addthis_widget.js
114 ms
output.css
106 ms
soliloquy.css
104 ms
qppr_frontend_script.min.js
107 ms
jquery.easing.1.3.js
107 ms
jquery.tools.min.js
110 ms
waypoints.min.js
110 ms
mediaelement-and-player.min.js
111 ms
jackbox-packed.min.js
109 ms
colortip-1.0-jquery.js
110 ms
jquery.flexslider.js
107 ms
script.js
102 ms
wp-embed.min.js
100 ms
soliloquy-min.js
82 ms
vertical_fade.png
116 ms
analytics.js
122 ms
logo-website.png
91 ms
ROAR-Flint-940x400.jpg
93 ms
holder.gif
84 ms
WellnessFair2014-750x423.jpg
94 ms
ourfood1.jpg
87 ms
social-media-homepage.jpg
88 ms
footer_bg.png
88 ms
linkid.js
65 ms
slider-arrows-horizontal.png
27 ms
slider-arrows-vertical.png
28 ms
pause-play.png
29 ms
link_arrow.png
31 ms
values_tab.png
29 ms
link_arrow.png
31 ms
ourfood_tab.png
32 ms
socialmedia_tab.png
32 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
20 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
23 ms
fontello.woff
20 ms
collect
146 ms
collect
172 ms
likebox.php
555 ms
widgets.js
106 ms
richsfooter.jpg
103 ms
preloader.gif
16 ms
SweetMiddles-940x400.jpg
157 ms
300lo.json
55 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
85 ms
Trend2Table-940x400.jpg
90 ms
940x4001.jpg
90 ms
slider-dots.png
31 ms
left.png
28 ms
right.png
31 ms
sh.8e5f85691f9aaa082472a194.html
39 ms
syndication
105 ms
373151416656748544
156 ms
kyEKgjk51ZE.css
291 ms
xgj7bXhJNEH.css
359 ms
Czh0gDTFcBt.css
427 ms
N-k91nHCZS2.css
559 ms
ZeuPykSxSED.css
566 ms
q68gy-v_YMF.js
749 ms
FJmpeSpHpjS.js
766 ms
0wM5s1Khldu.js
491 ms
1bNoFZUdlYZ.js
495 ms
njO1TPvGzoR.js
565 ms
1QuX41zDRrx.js
576 ms
Oagsvfb4VWi.js
783 ms
LTv6ZK-5zxz.js
824 ms
1FCa-btixu2.js
782 ms
proxy.jpg
173 ms
proxy.jpg
191 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
23 ms
ep2Po1X7_normal.jpeg
157 ms
ef2624484c92cd5bf2caa2bab20a7a50_normal.jpeg
175 ms
QDyfm2-p_normal.jpg
218 ms
fQaRWqxo_normal.jpg
239 ms
uxdFiNVB_normal.jpg
258 ms
21tL-660_normal.jpg
265 ms
Cd6hVBdW4AAdYWv.jpg:small
267 ms
CdoycY0UYAEuW_H.jpg:small
271 ms
CdrHJ2tWAAA59An.jpg:small
270 ms
CdiZeS6UMAArZv0.jpg:small
265 ms
Cdl_WQ7W8AEuxr5.jpg:small
283 ms
CdmDz1oUkAAzTxI.jpg:small
311 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
48 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
43 ms
proxy.jpg
42 ms
proxy.jpg
33 ms
layers.e5ea973510bf60b3db41.js
19 ms
jot.html
5 ms
10502236_787547714610279_3712201402274398253_n.png
489 ms
safe_image.php
287 ms
safe_image.php
350 ms
safe_image.php
418 ms
390758_305323039499418_1373689420_n.jpg
547 ms
10540776_1114021425296238_7150251167809615161_n.jpg
615 ms
10398594_1114020188629695_4341010470962738224_n.jpg
747 ms
wL6VQj7Ab77.png
97 ms
s7jcwEQH7Sx.png
96 ms
QDwYpIaRyfG.png
99 ms
K00K-UgnsKu.png
97 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
70 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
No form fields have multiple labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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 data is detected on the main page of Rich. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: