Tools & Wizards About Us
healingradius.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

healingradius.com

HealingRadius :: Page Not Found

Page Load Speed

1 sec in total

First Response

32 ms

Resources Loaded

907 ms

Page Rendered

80 ms

healingradius.com screenshot

About Website

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

Visit healingradius.com

Key Findings

We analyzed Healingradius.com page load time and found that the first response time was 32 ms and then it took 987 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

healingradius.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

healingradius.com

32 ms

www.healingradius.com

10 ms

www.healingradius.com

45 ms

gtm.js

109 ms

css

96 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 62% of them (40 requests) were addressed to the original Healingradius.com, 12% (8 requests) were made to Fonts.gstatic.com and 9% (6 requests) were made to D7i0gxyscl483.cloudfront.net. The less responsive or slowest element that took the longest time to load (276 ms) relates to the external source Cjs.ptengine.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.7 kB (36%)

Content Size

272.0 kB

After Optimization

174.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Healingradius.com main page is 272.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 189.7 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.9 kB

  • Original 6.3 kB
  • After minification 6.1 kB
  • After compression 2.5 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 3.9 kB or 61% of the original size.

Image Optimization

-25%

Potential reduce by 47.1 kB

  • Original 189.7 kB
  • After minification 142.6 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. Obviously, Healing Radius needs image optimization as it can save up to 47.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 45.5 kB

  • Original 67.6 kB
  • After minification 67.6 kB
  • After compression 22.1 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 45.5 kB or 67% of the original size.

CSS Optimization

-15%

Potential reduce by 1.3 kB

  • Original 8.3 kB
  • After minification 8.3 kB
  • After compression 7.1 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. Healingradius.com needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (56%)

Requests Now

43

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

healingradius.com

healingradius.com

32 ms

www.healingradius.com

www.healingradius.com

10 ms

www.healingradius.com

www.healingradius.com

45 ms

gtm.js

gtm.js

109 ms

css

css

96 ms

css

css

101 ms

css

css

125 ms

font-awesome.min.css

font-awesome.min.css

30 ms

css

css

63 ms

modernizr

modernizr

60 ms

css

css

61 ms

jquery

jquery

90 ms

jqueryui

jqueryui

92 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

91 ms

jqueryval

jqueryval

89 ms

bootstrap

bootstrap

91 ms

timepickerjs

timepickerjs

102 ms

jQuery.noBrowserSupport.js

jQuery.noBrowserSupport.js

55 ms

commoncss

commoncss

92 ms

healingradiusjs

healingradiusjs

91 ms

alphanumericjs

alphanumericjs

93 ms

commonjs

commonjs

97 ms

appinitjs

appinitjs

92 ms

carouseljs

carouseljs

95 ms

loader.js

loader.js

63 ms

logo.png

logo.png

11 ms

keyIcon.png

keyIcon.png

88 ms

userIcon.png

userIcon.png

89 ms

slide3.jpg

slide3.jpg

84 ms

page-not-found.jpg

page-not-found.jpg

81 ms

dotted.png

dotted.png

83 ms

logoW.png

logoW.png

85 ms

App-store.png

App-store.png

85 ms

Google-play.png

Google-play.png

88 ms

logo.png

logo.png

87 ms

page-not-found.jpg

page-not-found.jpg

18 ms

dotted.png

dotted.png

18 ms

slide3.jpg

slide3.jpg

18 ms

logow.png

logow.png

19 ms

app-store.png

app-store.png

17 ms

keyicon.png

keyicon.png

17 ms

usericon.png

usericon.png

18 ms

google-play.png

google-play.png

16 ms

widgets.js

widgets.js

75 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

75 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

110 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

127 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

127 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

126 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

126 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

28 ms

up-arrow.png

up-arrow.png

62 ms

roboto-condensed-webfont.woff

roboto-condensed-webfont.woff

59 ms

pta_en.js

pta_en.js

97 ms

jQuery.noBrowserSupport.css

jQuery.noBrowserSupport.css

132 ms

logo.png

logo.png

55 ms

chromeIcon.png

chromeIcon.png

210 ms

firefoxIcon.png

firefoxIcon.png

144 ms

safariIcon.png

safariIcon.png

144 ms

ieIcon.png

ieIcon.png

114 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

42 ms

settings

settings

100 ms

255e926e.js

255e926e.js

276 ms

Accessibility Review

healingradius.com accessibility score

69

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

healingradius.com best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

healingradius.com SEO score

82

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healingradius.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Healingradius.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

healingradius.com

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