12.5 sec in total
994 ms
10.8 sec
739 ms
Click here to check amazing Herbalheritage content. Otherwise, check out these important facts you probably never knew about herbalheritage.in
Visit herbalheritage.inWe analyzed Herbalheritage.in page load time and found that the first response time was 994 ms and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
herbalheritage.in performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value5.8 s
15/100
25%
Value10.0 s
9/100
10%
Value150 ms
95/100
30%
Value0.721
6/100
15%
Value19.5 s
2/100
10%
994 ms
1368 ms
915 ms
462 ms
685 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 66% of them (41 requests) were addressed to the original Herbalheritage.in, 21% (13 requests) were made to Embed.tawk.to and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.7 sec) belongs to the original domain Herbalheritage.in.
Page size can be reduced by 785.8 kB (10%)
8.1 MB
7.3 MB
In fact, the total size of Herbalheritage.in main page is 8.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. 50% of websites need less resources to load. Images take 7.5 MB which makes up the majority of the site volume.
Potential reduce by 21.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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.2 kB or 84% of the original size.
Potential reduce by 306.4 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. Herbalheritage images are well optimized though.
Potential reduce by 187.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 187.8 kB or 62% of the original size.
Potential reduce by 270.4 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. Herbalheritage.in needs all CSS files to be minified and compressed as it can save up to 270.4 kB or 84% of the original size.
Number of requests can be reduced by 36 (62%)
58
22
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Herbalheritage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
herbalheritage.in
994 ms
bootstrap.min.css
1368 ms
animate.css
915 ms
ddmenu.css
462 ms
common-styles.css
685 ms
common-responsive.css
459 ms
font-awesome.min.css
907 ms
lightgallery.css
1143 ms
owl.carousel.css
925 ms
owl.theme.css
1142 ms
bootstrap-touch-slider.css
1362 ms
date-picker.css
1823 ms
js
88 ms
jquery.js
2217 ms
bootstrap.min.js
2205 ms
ddmenu.js
1379 ms
wow.min.js
1596 ms
lazy-load.js
1599 ms
owl.carousel.js
2383 ms
common.js
2479 ms
lightgallery-all.min.js
2887 ms
bootstrap-touch-slider.js
2480 ms
dater-picker.js
3566 ms
css
35 ms
css
49 ms
analytics.js
653 ms
logo.png
1620 ms
appointmnt-icon.png
1114 ms
1369494912_2019-11-30_12-03-52.jpg
2072 ms
1424906755_2019-09-14_10-21-48.jpg
3778 ms
786961104_2019-09-14_10-22-40.jpg
2920 ms
bg-1.jpg
1903 ms
management-1.jpg
2284 ms
management-2.jpg
2284 ms
news-1.jpg
3195 ms
1798813895_2019-10-17_10-07-14.JPG
4786 ms
1193188067_2019-10-17_09-57-31.JPG
5244 ms
630814894_2019-10-17_09-56-52.JPG
4789 ms
2009850070_2019-10-17_09-53-34.JPG
5873 ms
9788_2019-08-31_11-06-38.jpg
5921 ms
655835927_2019-10-17_09-52-55.JPG
6271 ms
1232518157_2019-10-17_09-52-37.JPG
7736 ms
1108543556_2019-10-17_09-52-07.JPG
7741 ms
bg-3.jpg
6148 ms
2sDfZG1Wl4LcnbuKjk0j.ttf
191 ms
fontawesome-webfont.woff
6547 ms
EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf
185 ms
EJRVQgYoZZY2vCFuvAFWzro.ttf
185 ms
collect
25 ms
default
230 ms
twk-arr-find-polyfill.js
58 ms
twk-object-values-polyfill.js
69 ms
twk-event-polyfill.js
70 ms
twk-entries-polyfill.js
58 ms
twk-iterator-polyfill.js
69 ms
twk-promise-polyfill.js
190 ms
twk-main.js
137 ms
twk-vendor.js
165 ms
twk-chunk-vendors.js
211 ms
twk-chunk-common.js
225 ms
twk-runtime.js
130 ms
twk-app.js
187 ms
herbalheritage.in accessibility score
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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
herbalheritage.in 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
Page has valid source maps
herbalheritage.in 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
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Herbalheritage.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Herbalheritage.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.
herbalheritage.in
Open Graph description is not detected on the main page of Herbalheritage. 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: