Tools & Wizards About Us
herbaceacare.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

herbaceacare.com

Herbacea Care

Page Load Speed

17.4 sec in total

First Response

886 ms

Resources Loaded

15.5 sec

Page Rendered

1 sec

herbaceacare.com screenshot

About Website

Visit herbaceacare.com now to see the best up-to-date Herbacea Care content for India and also check out these interesting facts you probably never knew about herbaceacare.com

Visit herbaceacare.com

Key Findings

We analyzed Herbaceacare.com page load time and found that the first response time was 886 ms and then it took 16.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

herbaceacare.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

herbaceacare.com

886 ms

dripicons.min.css

593 ms

elegant-icons.min.css

601 ms

all.min.css

619 ms

ionicons.min.css

587 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 82% of them (106 requests) were addressed to the original Herbaceacare.com, 14% (18 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Herbaceacare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.8 kB (6%)

Content Size

4.6 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Herbaceacare.com main page is 4.6 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. 70% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 233.0 kB

  • Original 262.2 kB
  • After minification 242.2 kB
  • After compression 29.2 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 233.0 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 20.6 kB

  • Original 3.6 MB
  • After minification 3.6 MB

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. Herbacea Care images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.0 kB

  • Original 498.8 kB
  • After minification 498.8 kB
  • After compression 495.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 4.2 kB

  • Original 238.5 kB
  • After minification 238.0 kB
  • After compression 234.3 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. Herbaceacare.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 84 (79%)

Requests Now

107

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Herbacea Care. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

herbaceacare.com

herbaceacare.com

886 ms

dripicons.min.css

dripicons.min.css

593 ms

elegant-icons.min.css

elegant-icons.min.css

601 ms

all.min.css

all.min.css

619 ms

ionicons.min.css

ionicons.min.css

587 ms

linea-icons.min.css

linea-icons.min.css

645 ms

linear-icons.min.css

linear-icons.min.css

869 ms

icon

icon

35 ms

simple-line-icons.min.css

simple-line-icons.min.css

1176 ms

style.min.css

style.min.css

1191 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

1187 ms

wc-blocks-style.css

wc-blocks-style.css

1514 ms

styles.css

styles.css

1257 ms

ctf-styles.min.css

ctf-styles.min.css

1474 ms

login.css

login.css

1741 ms

swiper.min.css

swiper.min.css

1794 ms

grid.min.css

grid.min.css

1759 ms

helper-parts.min.css

helper-parts.min.css

1859 ms

main.min.css

main.min.css

2327 ms

select2.css

select2.css

2079 ms

core-dashboard.min.css

core-dashboard.min.css

2320 ms

perfect-scrollbar.css

perfect-scrollbar.css

2347 ms

main.min.css

main.min.css

2666 ms

sante-core.min.css

sante-core.min.css

2737 ms

sante-membership.min.css

sante-membership.min.css

2656 ms

design.css

design.css

2886 ms

magnific-popup.css

magnific-popup.css

2910 ms

css

css

30 ms

design.css

design.css

2942 ms

elementor.min.css

elementor.min.css

3211 ms

elementor-icons.min.css

elementor-icons.min.css

3243 ms

frontend-lite.min.css

frontend-lite.min.css

3341 ms

post-5.css

post-5.css

3451 ms

global.css

global.css

3492 ms

post-84.css

post-84.css

3525 ms

css

css

28 ms

jquery.min.js

jquery.min.js

4083 ms

jquery-migrate.min.js

jquery-migrate.min.js

3840 ms

email-decode.min.js

email-decode.min.js

3076 ms

css

css

13 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

3643 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

3461 ms

rs6.css

rs6.css

3478 ms

index.js

index.js

3597 ms

index.js

index.js

3880 ms

rbtools.min.js

rbtools.min.js

4435 ms

rs6.min.js

rs6.min.js

4337 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

3484 ms

js.cookie.min.js

js.cookie.min.js

3484 ms

woocommerce.min.js

woocommerce.min.js

3490 ms

cart-fragments.min.js

cart-fragments.min.js

3784 ms

core.min.js

core.min.js

3751 ms

main.min.js

main.min.js

3739 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

3519 ms

hoverIntent.min.js

hoverIntent.min.js

3868 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

3878 ms

modernizr.js

modernizr.js

3940 ms

tweenmax.min.js

tweenmax.min.js

4040 ms

main.min.js

main.min.js

3511 ms

sante-core.min.js

sante-core.min.js

3492 ms

tabs.min.js

tabs.min.js

3876 ms

sante-membership.min.js

sante-membership.min.js

3592 ms

jquery.waitforimages.js

jquery.waitforimages.js

3699 ms

jquery.appear.js

jquery.appear.js

3660 ms

swiper.min.js

swiper.min.js

3799 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

3790 ms

select2.full.min.js

select2.full.min.js

4149 ms

jquery.justifiedGallery.min.js

jquery.justifiedGallery.min.js

3616 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

3729 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

3648 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

4237 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

3842 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

3936 ms

vimeo.min.js

vimeo.min.js

4024 ms

webpack.runtime.min.js

webpack.runtime.min.js

3788 ms

frontend-modules.min.js

frontend-modules.min.js

3743 ms

waypoints.min.js

waypoints.min.js

3847 ms

frontend.min.js

frontend.min.js

3947 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

3942 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

3892 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

122 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

153 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

153 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

154 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

154 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

153 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

155 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

155 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

154 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

156 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

156 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

157 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

154 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

156 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

157 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

157 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

158 ms

font

font

157 ms

wp-polyfill.min.js

wp-polyfill.min.js

3987 ms

hooks.min.js

hooks.min.js

3575 ms

i18n.min.js

i18n.min.js

3830 ms

elementor.js

elementor.js

3903 ms

elementor.js

elementor.js

3679 ms

ElegantIcons.woff

ElegantIcons.woff

4212 ms

quentin-webfont.woff

quentin-webfont.woff

4771 ms

Linearicons-Free.woff

Linearicons-Free.woff

4446 ms

fa-solid-900.woff

fa-solid-900.woff

4654 ms

fa-regular-400.woff

fa-regular-400.woff

4249 ms

Herbacea-Care-Logo-1.png

Herbacea-Care-Logo-1.png

3367 ms

dummy.png

dummy.png

3631 ms

3.png

3.png

4946 ms

2.png

2.png

4901 ms

6.png

6.png

5151 ms

7.png

7.png

5009 ms

1.png

1.png

5113 ms

sdk.js

sdk.js

17 ms

5.png

5.png

5219 ms

sdk.js

sdk.js

5 ms

h1-banner-img-1.jpg

h1-banner-img-1.jpg

5802 ms

h1-banner-img-2.jpg

h1-banner-img-2.jpg

5827 ms

h1-banner-img-3.jpg

h1-banner-img-3.jpg

5448 ms

section-title-icon-1.png

section-title-icon-1.png

4459 ms

3-650x650.png

3-650x650.png

6027 ms

2-650x650.png

2-650x650.png

6045 ms

6-650x650.png

6-650x650.png

6125 ms

7-650x650.png

7-650x650.png

6434 ms

1-650x650.png

1-650x650.png

6550 ms

5-650x650.png

5-650x650.png

6511 ms

pexels-oliver-king-4061116.jpg

pexels-oliver-king-4061116.jpg

6423 ms

pexels-roger-brown-5664736-1-scaled.jpg

pexels-roger-brown-5664736-1-scaled.jpg

7130 ms

Accessibility Review

herbaceacare.com accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

herbaceacare.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

herbaceacare.com SEO score

70

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Herbaceacare.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 Herbaceacare.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.

Social Sharing Optimization

herbaceacare.com

Open Graph description is not detected on the main page of Herbacea Care. 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: