23.1 sec in total
2.2 sec
20.4 sec
478 ms
Click here to check amazing Healthbuds content for India. Otherwise, check out these important facts you probably never knew about healthbuds.in
Healthbuds - Partnering Your Well Being
Visit healthbuds.inWe analyzed Healthbuds.in page load time and found that the first response time was 2.2 sec and then it took 20.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
healthbuds.in performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value13.1 s
0/100
25%
Value24.2 s
0/100
10%
Value8,610 ms
0/100
30%
Value0.911
3/100
15%
Value31.6 s
0/100
10%
2194 ms
99 ms
109 ms
96 ms
96 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 83% of them (123 requests) were addressed to the original Healthbuds.in, 11% (16 requests) were made to Health.healthbuds.in and 1% (2 requests) were made to Seal.websecurity.norton.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Healthbuds.in.
Page size can be reduced by 387.2 kB (36%)
1.1 MB
676.7 kB
In fact, the total size of Healthbuds.in main page is 1.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. 45% of websites need less resources to load. Images take 587.1 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.6 kB or 79% of the original size.
Potential reduce by 51.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. Healthbuds images are well optimized though.
Potential reduce by 59.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 59.9 kB or 49% of the original size.
Potential reduce by 246.5 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. Healthbuds.in needs all CSS files to be minified and compressed as it can save up to 246.5 kB or 78% of the original size.
Number of requests can be reduced by 107 (73%)
147
40
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Healthbuds. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.
healthbuds.in
2194 ms
opentip.css
99 ms
calendar-blue.css
109 ms
default.css
96 ms
alphacube.css
96 ms
styles.css
118 ms
widgets.css
102 ms
style.css
1094 ms
amshopby.css
104 ms
fc.css
109 ms
itemslider.css
1094 ms
generic-nav.css
129 ms
brands.css
1090 ms
ultra-slideshow.css
160 ms
accordion.css
1102 ms
menu.css
1156 ms
menu-accordion.css
244 ms
menu-dropdown.css
265 ms
menu-sidebar.css
313 ms
additional.css
327 ms
bookmark.css
1338 ms
style.css
2075 ms
amazon.css
2113 ms
mirasvit_searchindex.css
2055 ms
social-share.css
2700 ms
form.css
1163 ms
results.css
1213 ms
stars.css
1469 ms
file-upload.css
1351 ms
srka.review.stars.css
1362 ms
styles-infortis.css
1368 ms
generic-cck.css
2706 ms
dropdown.css
3751 ms
itemgrid.css
2056 ms
tabs.css
2065 ms
icons.css
2083 ms
css
96 ms
icons-font.css
3635 ms
icons-theme.css
2011 ms
icons-social.css
2025 ms
common.css
2036 ms
override-components.css
3623 ms
override-theme.css
3614 ms
grid12.css
3623 ms
design_default.css
2594 ms
grid_default.css
2574 ms
getseal
185 ms
layout_default.css
2522 ms
override-config.css
4464 ms
custom.css
3716 ms
tooltip.css
4422 ms
prototype.js
4681 ms
ccard.js
3678 ms
validation.js
3686 ms
builder.js
3884 ms
effects.js
4628 ms
dragdrop.js
3596 ms
controls.js
3603 ms
slider.js
4565 ms
js.js
3445 ms
form.js
4425 ms
translate.js
4405 ms
cookies.js
4614 ms
jquery-1.7.2.min.js
4766 ms
jquery-noconflict.js
4657 ms
jquery.owlcarousel.min.js
4690 ms
jquery.easing.min.js
4723 ms
jquery.accordion.min.js
4682 ms
jquery.cookie.js
4896 ms
bookmark.js
5118 ms
jquery.min.js
4604 ms
underscore.js
5589 ms
backbone.js
4626 ms
form.js
5625 ms
autocomplete.js
5070 ms
logic.js
5068 ms
opentip-native-excanvas.min.js
4274 ms
multistep.js
5241 ms
stars.js
4469 ms
calendar.js
4739 ms
calendar-setup.js
3991 ms
window.js
3994 ms
tiny_mce.js
5526 ms
no-conflict.js
5042 ms
jquery.ui.widget.js
4037 ms
jquery.iframe-transport.js
4050 ms
jquery.fileupload.js
4253 ms
srka.review.stars.min.js
4278 ms
modernizr.custom.min.js
4662 ms
custom.js
4966 ms
matchMedia.js
4038 ms
matchMedia.addListener.js
5036 ms
enquire.js
4272 ms
jquery.tabs.min.js
4274 ms
imagesloaded.js
4500 ms
jquery.auto-text-rotating.js
4513 ms
app.js
3533 ms
jquery.js
3554 ms
main.js
4350 ms
ga.js
70 ms
tree.png
523 ms
logo-healthbuds-mobile.png
979 ms
logo.png
1011 ms
logoimg.png
1021 ms
icon.png
745 ms
1401346942Socialshare_Image.png
993 ms
1401346970Socialshare_Image.png
1015 ms
1401347001Socialshare_Image.png
978 ms
1401347065Socialshare_Image.png
1011 ms
24-hours.png
520 ms
phone.png
520 ms
stethoscope.png
542 ms
stars.png
544 ms
img4.png
803 ms
img5.png
784 ms
mobile-phone.png
1287 ms
google-play-store.png
1036 ms
life-notes.png
1041 ms
facebooklogo.png
805 ms
twiterlogo.png
1033 ms
gplogo.png
1067 ms
gtm.js
183 ms
link-separator.png
1961 ms
upper-bg.jpg
1325 ms
2hig-tnMw8lXZsjwuh-9ow.ttf
97 ms
dr-background.jpg
1489 ms
app-download-bg.jpg
1498 ms
__utm.gif
47 ms
show
3340 ms
15.png
2883 ms
bullet.png
1870 ms
getseal
119 ms
fc_add_item.jpg
1836 ms
fc_close_icon.png
1804 ms
medica-hospital.jpg
2765 ms
woodlands-hospitals.jpg
2798 ms
apollo-clinic.jpg
2801 ms
vasan-eye-care.jpg
2812 ms
ajax-loader.gif
3746 ms
analytics.js
22 ms
collect
5 ms
collect
111 ms
microlap.jpg
1788 ms
healthbuds-logo.png
1333 ms
opc-ajax-loader.gif
1026 ms
hb-apps-store.png
1123 ms
ruby-hospital.jpg
1014 ms
print.css
1460 ms
mercy-hospital.jpg
1035 ms
healthbuds.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
button, link, and menuitem elements do not have accessible names.
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
healthbuds.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
healthbuds.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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healthbuds.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), while the claimed language is English. Our system also found out that Healthbuds.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.
healthbuds.in
Open Graph description is not detected on the main page of Healthbuds. 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: