2.1 sec in total
248 ms
1.3 sec
567 ms
Click here to check amazing Holista content for India. Otherwise, check out these important facts you probably never knew about holista.in
Discover premium coconut-based food ingredients & preparatory products crafted with care & quality. Experience the goodness of coconut in every offering from Holista.
Visit holista.inWe analyzed Holista.in page load time and found that the first response time was 248 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
holista.in performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.7 s
1/100
25%
Value12.9 s
2/100
10%
Value1,580 ms
13/100
30%
Value0
100/100
15%
Value19.3 s
2/100
10%
248 ms
116 ms
58 ms
92 ms
65 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 75% of them (75 requests) were addressed to the original Holista.in, 12% (12 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (440 ms) belongs to the original domain Holista.in.
Page size can be reduced by 859.0 kB (21%)
4.1 MB
3.3 MB
In fact, the total size of Holista.in main page is 4.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. Only a small number of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 138.1 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 138.1 kB or 85% of the original size.
Potential reduce by 87.8 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. Holista images are well optimized though.
Potential reduce by 86.9 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 86.9 kB or 15% of the original size.
Potential reduce by 546.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. Holista.in needs all CSS files to be minified and compressed as it can save up to 546.2 kB or 68% of the original size.
Number of requests can be reduced by 54 (64%)
84
30
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Holista. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
holista.in
248 ms
holista.in
116 ms
w405.css
58 ms
w405.css
92 ms
post-7.css
65 ms
w405.css
101 ms
post-2.css
80 ms
w405.css
82 ms
css
31 ms
w405.css
111 ms
w46b.css
141 ms
css
50 ms
w405.js
120 ms
w405.js
110 ms
js
71 ms
post-2271.css
94 ms
post-2393.css
94 ms
post-2407.css
97 ms
post-36.css
102 ms
post-75.css
108 ms
post-154.css
373 ms
post-120.css
375 ms
post-229.css
374 ms
w405.css
376 ms
main.min.js
398 ms
hooks.min.js
396 ms
i18n.min.js
396 ms
index.js
418 ms
index.js
417 ms
core.min.js
396 ms
pum-site-scripts.js
397 ms
jquery-mousewheel.min.js
396 ms
custom-scrollbar.min.js
398 ms
post-type.min.js
398 ms
api.js
71 ms
wp-polyfill.min.js
400 ms
index.js
440 ms
frontend-common.min.js
401 ms
the7-slider.min.js
401 ms
the7-tabs-widget.min.js
402 ms
jquery-numerator.min.js
402 ms
the7-simple-posts.min.js
403 ms
webpack-pro.runtime.min.js
373 ms
webpack.runtime.min.js
370 ms
frontend-modules.min.js
352 ms
css
29 ms
frontend.min.js
352 ms
waypoints.min.js
336 ms
frontend.min.js
325 ms
elements-handlers.min.js
325 ms
jquery-sticky.min.js
316 ms
sticky-effects.min.js
315 ms
logo-small-white.png
138 ms
the7-chevron-down.svg
138 ms
the7-chevron-side.svg
139 ms
pm.png
140 ms
home-image1.jpg
140 ms
home-image2.jpg
64 ms
home-image3.jpg
45 ms
home-image5-1.png
45 ms
home-image6-1.png
42 ms
home-image7-1.png
193 ms
quality-image1.png
41 ms
quality-image2.png
40 ms
quality-logo6.png
163 ms
quality-image4.png
163 ms
quality-image5.png
163 ms
partners-logo1.png
162 ms
partners-logo2.png
161 ms
partners-logo3-1.png
190 ms
partners-logo4.png
187 ms
home-form-image.jpg
269 ms
home-image10.png
265 ms
home-image11.webp
266 ms
quote.png
264 ms
footer-bg.png
266 ms
anuga-banner-6.webp
263 ms
world-food-banner-1.webp
266 ms
AYCSpXb_Z9EORv1M5QTjEzMEteaAxIc.ttf
114 ms
BrisaAlternates.ttf
257 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5Xs1Ug.ttf
113 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4Gfy5Xs1Ug.ttf
147 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1Ug.ttf
174 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5Xs1Ug.ttf
173 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G5ClXs1Ug.ttf
174 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1Ug.ttf
172 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClXs1Ug.ttf
172 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXs1Ug.ttf
171 ms
icomoon-the7-font.ttf
256 ms
recaptcha__en.js
154 ms
anchor
103 ms
styles__ltr.css
4 ms
recaptcha__en.js
10 ms
TTBJrrNQwau1PDJ6QUYcAMwMD78zyE29ToB9MLfHXyQ.js
30 ms
webworker.js
29 ms
logo_48.png
21 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
68 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
69 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
68 ms
recaptcha__en.js
72 ms
holista.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-*] attributes do not match their roles
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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
holista.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
holista.in SEO score
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 Holista.in 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 Holista.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.
holista.in
Open Graph data is detected on the main page of Holista. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: