4.2 sec in total
207 ms
3.3 sec
655 ms
Click here to check amazing Herbal Ride content. Otherwise, check out these important facts you probably never knew about herbalride.com
Visit herbalride.comWe analyzed Herbalride.com page load time and found that the first response time was 207 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
herbalride.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value6.8 s
7/100
25%
Value7.9 s
22/100
10%
Value2,690 ms
3/100
30%
Value0.211
59/100
15%
Value19.5 s
2/100
10%
207 ms
330 ms
58 ms
113 ms
166 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 84% of them (114 requests) were addressed to the original Herbalride.com, 11% (15 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (549 ms) belongs to the original domain Herbalride.com.
Page size can be reduced by 109.3 kB (5%)
2.1 MB
1.9 MB
In fact, the total size of Herbalride.com main page is 2.1 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. 80% 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 102.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 102.6 kB or 84% of the original size.
Potential reduce by 3.6 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. Herbal Ride images are well optimized though.
Potential reduce by 2.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 1.2 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. Herbalride.com has all CSS files already compressed.
Number of requests can be reduced by 88 (79%)
112
24
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Herbal Ride. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
herbalride.com
207 ms
www.herbalride.com
330 ms
frontend-lite.min.css
58 ms
post-385.css
113 ms
post-809.css
166 ms
styles.css
167 ms
style.min.css
223 ms
style.css
170 ms
woo-mini-cart.min.css
168 ms
all.min.css
172 ms
simple-line-icons.min.css
218 ms
css
35 ms
css
45 ms
ekiticons.css
233 ms
elementor-icons.min.css
238 ms
swiper.min.css
239 ms
post-387.css
240 ms
post-2.css
271 ms
woocommerce.min.css
278 ms
woo-star-font.min.css
275 ms
hover-style.min.css
276 ms
woo-quick-view.min.css
284 ms
widget-styles.css
341 ms
responsive.css
325 ms
widgets.css
329 ms
style.min.css
333 ms
css
42 ms
fontawesome.min.css
334 ms
solid.min.css
333 ms
brands.min.css
378 ms
jquery.min.js
439 ms
jquery-migrate.min.js
393 ms
jquery.blockUI.min.js
392 ms
add-to-cart.min.js
392 ms
js.cookie.min.js
393 ms
woocommerce.min.js
431 ms
underscore.min.js
453 ms
wp-util.min.js
459 ms
add-to-cart-variation.min.js
467 ms
jquery.flexslider.min.js
468 ms
css
31 ms
api.js
52 ms
api.js
70 ms
widget-icon-list.min.css
481 ms
style-1345.css
549 ms
forminator-icons.min.css
502 ms
forminator-utilities.min.css
446 ms
forminator-form-default.base.min.css
447 ms
intlTelInput.min.css
439 ms
buttons.min.css
446 ms
animations.min.css
507 ms
cart-fragments.min.js
490 ms
index.js
477 ms
index.js
472 ms
sourcebuster.min.js
467 ms
order-attribution.min.js
469 ms
imagesloaded.min.js
506 ms
theme.min.js
475 ms
drop-down-mobile-menu.min.js
467 ms
drop-down-search.min.js
467 ms
magnific-popup.min.js
469 ms
ow-lightbox.min.js
459 ms
flickity.pkgd.min.js
443 ms
ow-slider.min.js
444 ms
scroll-effect.min.js
444 ms
scroll-top.min.js
427 ms
select.min.js
439 ms
woo-custom-features.min.js
425 ms
frontend-script.js
427 ms
widget-scripts.js
436 ms
wp-polyfill-inert.min.js
427 ms
regenerator-runtime.min.js
456 ms
wp-polyfill.min.js
524 ms
index.js
389 ms
woo-hover-style.min.js
419 ms
woo-quick-view.min.js
448 ms
woo-mini-cart.min.js
447 ms
social.js
448 ms
jquery.validate.min.js
437 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
133 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
160 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
163 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
162 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
163 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
162 ms
forminator-form.min.js
366 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
48 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
52 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
52 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
56 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
56 ms
front.multi.min.js
360 ms
intlTelInput.min.js
361 ms
cleave.min.js
363 ms
cleave-phone.i18n.js
448 ms
webpack.runtime.min.js
360 ms
frontend-modules.min.js
375 ms
waypoints.min.js
297 ms
core.min.js
297 ms
frontend.min.js
307 ms
animate-circle.min.js
308 ms
elementor.js
335 ms
fa-solid-900.woff
411 ms
fa-solid-900.ttf
484 ms
fa-regular-400.ttf
407 ms
eicons.woff
457 ms
fa-brands-400.woff
421 ms
fa-brands-400.ttf
486 ms
elementskit.woff
534 ms
herbal-logo.png
407 ms
logo-1.png
441 ms
slider-3.jpg
542 ms
slider-2.jpg
525 ms
slider-1.jpg
530 ms
ayurvedic-treatment-and-herbs.png
490 ms
online-ayurvedic-store-ayurvedic-medicine-online.png
464 ms
natural-health-care-products.png
508 ms
money-back.png
517 ms
recaptcha__en.js
27 ms
ayurvedic-medicine-for-bone-density_1.jpg
492 ms
ayurvedic-medcine-for-menopause_1.jpg
494 ms
d.jpg
494 ms
ayurvedic-medicine-for-muscle-health-and-healthy-joints_1.jpg
457 ms
ayurvedic-medicine-for-mens-health_1.jpg
467 ms
ayurvedic-medicine-for-pancreas-health_1.jpg
476 ms
ayurvedic-herbs-ayurvedic-treatment.jpg
439 ms
ccc.png
440 ms
ayurvedic-doctor.jpg
462 ms
ayurvedic-doctor-ayurvedic-physician.jpg
461 ms
health-care-natural-products.jpg
469 ms
organic-ayurvedic-products.jpg
532 ms
background-5.jpg
483 ms
herbalride.com 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
Links do not have a discernible name
herbalride.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
herbalride.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Herbalride.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 Herbalride.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.
herbalride.com
Open Graph description is not detected on the main page of Herbal Ride. 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: