Tools & Wizards About Us
healcard.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

healcard.com

Healcard: India's Top Clinic & Hospital Management Software

Page Load Speed

10.8 sec in total

First Response

413 ms

Resources Loaded

9.5 sec

Page Rendered

823 ms

healcard.com screenshot

About Website

Click here to check amazing Healcard content. Otherwise, check out these important facts you probably never knew about healcard.com

Discover Healcard's AI-powered EMR & HIMS. Book online appointments, manage records, and enhance patient care all in one secure platform.

Visit healcard.com

Key Findings

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

Performance Metrics

healcard.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

healcard.com

413 ms

www.healcard.com

2511 ms

7935751.js

95 ms

gtm.js

78 ms

banner.js

45 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 28% of them (18 requests) were addressed to the original Healcard.com, 50% (32 requests) were made to Cdn.healcard.com and 11% (7 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Healcard.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (68%)

Content Size

1.7 MB

After Optimization

558.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Healcard.com main page is 1.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. 55% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 985.2 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 184.0 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 985.2 kB or 84% of the original size.

Image Optimization

-35%

Potential reduce by 175.2 kB

  • Original 507.6 kB
  • After minification 332.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. Obviously, Healcard needs image optimization as it can save up to 175.2 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 7.2 kB

  • Original 49.6 kB
  • After minification 49.6 kB
  • After compression 42.4 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 7.2 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (45%)

Requests Now

60

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

healcard.com

healcard.com

413 ms

www.healcard.com

www.healcard.com

2511 ms

7935751.js

7935751.js

95 ms

gtm.js

gtm.js

78 ms

banner.js

banner.js

45 ms

fb.js

fb.js

46 ms

collectedforms.js

collectedforms.js

44 ms

conversations-embed.js

conversations-embed.js

52 ms

7935751.js

7935751.js

54 ms

lightgallery.css

lightgallery.css

28 ms

lg-zoom.css

lg-zoom.css

37 ms

lg-thumbnail.css

lg-thumbnail.css

48 ms

lg-video.css

lg-video.css

49 ms

lg-autoplay.css

lg-autoplay.css

45 ms

lg-rotate.css

lg-rotate.css

57 ms

lg-fullscreen.css

lg-fullscreen.css

45 ms

1568193280187.png

1568193280187.png

86 ms

runtime.81da8165dfef94d4.js

runtime.81da8165dfef94d4.js

242 ms

polyfills.fb424d3afb37231a.js

polyfills.fb424d3afb37231a.js

433 ms

scripts.52aa9237eb9ccab5.js

scripts.52aa9237eb9ccab5.js

1391 ms

main.9e80fc5197f85f04.js

main.9e80fc5197f85f04.js

1955 ms

1568193301333.png

1568193301333.png

64 ms

1587291144766.svg

1587291144766.svg

65 ms

1587291199372.svg

1587291199372.svg

66 ms

1580107135402.svg

1580107135402.svg

67 ms

1580107535303.svg

1580107535303.svg

69 ms

1571459912481.svg

1571459912481.svg

72 ms

1571464895850.svg

1571464895850.svg

68 ms

1580125014656.svg

1580125014656.svg

70 ms

1592209926929.svg

1592209926929.svg

73 ms

1592210049244.svg

1592210049244.svg

73 ms

1592209936529.svg

1592209936529.svg

77 ms

1571464812518.svg

1571464812518.svg

74 ms

1571464873174.svg

1571464873174.svg

75 ms

1580189488114.png

1580189488114.png

79 ms

1580187684484.svg

1580187684484.svg

78 ms

1580120024133.svg

1580120024133.svg

80 ms

1580204748601.png

1580204748601.png

81 ms

1580817656614.png

1580817656614.png

82 ms

1581571509898.png

1581571509898.png

98 ms

1581059184637.png

1581059184637.png

81 ms

1591349186937.png

1591349186937.png

83 ms

1580208242854.svg

1580208242854.svg

82 ms

1580208279186.svg

1580208279186.svg

84 ms

1580208269810.svg

1580208269810.svg

85 ms

1580208260258.svg

1580208260258.svg

86 ms

1580207110464.png

1580207110464.png

107 ms

1711604362239.svg

1711604362239.svg

93 ms

1711604345329.svg

1711604345329.svg

89 ms

1580209570255.svg

1580209570255.svg

97 ms

1580209609630.svg

1580209609630.svg

99 ms

1581682043587.png

1581682043587.png

107 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

2361 ms

fa-brands-400.woff

fa-brands-400.woff

2418 ms

MaterialIcons-Regular.ttf

MaterialIcons-Regular.ttf

1774 ms

fa-brands-400.ttf

fa-brands-400.ttf

1760 ms

material-icons.css

material-icons.css

322 ms

fa-brands-400.svg

fa-brands-400.svg

1015 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

193 ms

css.css

css.css

192 ms

all.css

all.css

206 ms

styles.css

styles.css

192 ms

fa-brands-400.woff

fa-brands-400.woff

382 ms

styles.1af070a8a0ff6af2.css

styles.1af070a8a0ff6af2.css

403 ms

Accessibility Review

healcard.com accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

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

Missing source maps for large first-party JavaScript

SEO Factors

healcard.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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

healcard.com

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