Tools & Wizards About Us
himalayanheal.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

himalayanheal.com

Himalayan Heal Ayurveda MD Expert panel » Himalayan Heal

Page Load Speed

3.2 sec in total

First Response

117 ms

Resources Loaded

2.5 sec

Page Rendered

569 ms

himalayanheal.com screenshot

About Website

Click here to check amazing Himalayan Heal content. Otherwise, check out these important facts you probably never knew about himalayanheal.com

Step into our GMP-certified manufacturing facility in the peaceful Sansarpur Terrace, Himachal Pradesh, where time-honored practices meet modern methods. Led by our MD specialists, we offer tailored A...

Visit himalayanheal.com

Key Findings

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

Performance Metrics

himalayanheal.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value32.5 s

0/100

10%

TBT (Total Blocking Time)

Value46,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value94.0 s

0/100

10%

Network Requests Diagram

himalayanheal.com

117 ms

2hex7.css

165 ms

2ijan.css

133 ms

post-20739.css

130 ms

2ijan.css

150 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 53% of them (42 requests) were addressed to the original Himalayanheal.com, 15% (12 requests) were made to Embed.tawk.to and 6% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (623 ms) belongs to the original domain Himalayanheal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (40%)

Content Size

4.7 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Himalayanheal.com main page is 4.7 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. 85% 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 1.6 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 240.9 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 1.6 MB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 141.5 kB

  • Original 1.9 MB
  • After minification 1.7 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. Himalayan Heal images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 141.2 kB

  • Original 915.0 kB
  • After minification 915.0 kB
  • After compression 773.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 141.2 kB or 15% of the original size.

CSS Optimization

-1%

Potential reduce by 1.2 kB

  • Original 112.1 kB
  • After minification 112.1 kB
  • After compression 110.9 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. Himalayanheal.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (83%)

Requests Now

75

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

himalayanheal.com

himalayanheal.com

117 ms

2hex7.css

2hex7.css

165 ms

2ijan.css

2ijan.css

133 ms

post-20739.css

post-20739.css

130 ms

2ijan.css

2ijan.css

150 ms

post-16572.css

post-16572.css

56 ms

css

css

72 ms

2hex8.js

2hex8.js

84 ms

2ijan.js

2ijan.js

82 ms

2hex8.js

2hex8.js

99 ms

2hex8.js

2hex8.js

102 ms

2hex8.js

2hex8.js

113 ms

90 ms

2hex8.js

2hex8.js

119 ms

js

js

102 ms

domain_74252025_8321_4614_82b8_46c447627d33.js

domain_74252025_8321_4614_82b8_46c447627d33.js

378 ms

adsbygoogle.js

adsbygoogle.js

370 ms

email-decode.min.js

email-decode.min.js

60 ms

2hex7.css

2hex7.css

323 ms

2ijan.css

2ijan.css

87 ms

js

js

88 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

100 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

387 ms

wp-polyfill.min.js

wp-polyfill.min.js

101 ms

hooks.min.js

hooks.min.js

386 ms

i18n.min.js

i18n.min.js

100 ms

main.js

main.js

101 ms

mpp-frontend.js

mpp-frontend.js

311 ms

sourcebuster.min.js

sourcebuster.min.js

312 ms

order-attribution.min.js

order-attribution.min.js

311 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

312 ms

imagesloaded.min.js

imagesloaded.min.js

384 ms

a403f542a6a693a78452f7fb653e380a.min.js

a403f542a6a693a78452f7fb653e380a.min.js

314 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

314 ms

webpack.runtime.min.js

webpack.runtime.min.js

315 ms

frontend-modules.min.js

frontend-modules.min.js

316 ms

frontend.min.js

frontend.min.js

317 ms

waypoints.min.js

waypoints.min.js

383 ms

core.min.js

core.min.js

382 ms

frontend.min.js

frontend.min.js

382 ms

elements-handlers.min.js

elements-handlers.min.js

384 ms

scc-c2.min.js

scc-c2.min.js

4 ms

tti.min.js

tti.min.js

4 ms

gtm.js

gtm.js

235 ms

fbevents.js

fbevents.js

234 ms

js

js

116 ms

analytics.js

analytics.js

109 ms

awb-icons.woff

awb-icons.woff

182 ms

eicons.woff

eicons.woff

203 ms

show_ads_impl.js

show_ads_impl.js

368 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

161 ms

client.js

client.js

162 ms

sdk.js

sdk.js

94 ms

destination

destination

115 ms

collect

collect

25 ms

collect

collect

292 ms

default

default

266 ms

sdk.js

sdk.js

164 ms

logo-2-1.png

logo-2-1.png

256 ms

Untitled-design-7.png

Untitled-design-7.png

236 ms

Untitled-design-8.png

Untitled-design-8.png

623 ms

ga-audiences

ga-audiences

294 ms

ads

ads

92 ms

265 ms

ITP-3-212x300.png

ITP-3-212x300.png

117 ms

1-212x300.png

1-212x300.png

117 ms

sodar

sodar

97 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

205 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

100 ms

twk-event-polyfill.js

twk-event-polyfill.js

203 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

98 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

100 ms

twk-main.js

twk-main.js

28 ms

twk-vendor.js

twk-vendor.js

43 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

62 ms

twk-chunk-common.js

twk-chunk-common.js

98 ms

twk-runtime.js

twk-runtime.js

101 ms

twk-app.js

twk-app.js

99 ms

141 ms

sodar2.js

sodar2.js

93 ms

Accessibility Review

himalayanheal.com accessibility score

85

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

himalayanheal.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

himalayanheal.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Himalayanheal.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 Himalayanheal.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

himalayanheal.com

Open Graph data is detected on the main page of Himalayan Heal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: