Tools & Wizards About Us
heartbeat.ai screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

heartbeat.ai

Heartbeat AI - Search 11M+ Healthcare & Medical Professionals

Page Load Speed

2.3 sec in total

First Response

173 ms

Resources Loaded

1.7 sec

Page Rendered

452 ms

heartbeat.ai screenshot

About Website

Click here to check amazing Heartbeat content. Otherwise, check out these important facts you probably never knew about heartbeat.ai

Heartbeat AI lets you quickly find Healthcare & Medical Professionals’ direct contact info: email addresses, direct telephone, and cell / mobile phone numbers. Perfect for Staffing, Recruiting, or Sal...

Visit heartbeat.ai

Key Findings

We analyzed Heartbeat.ai page load time and found that the first response time was 173 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

heartbeat.ai performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

heartbeat.ai

173 ms

heartbeat.ai

454 ms

gtm.js

91 ms

landings.min.css

40 ms

jquery.min.js

47 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 76% of them (38 requests) were addressed to the original Heartbeat.ai, 6% (3 requests) were made to Googletagmanager.com and 6% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (454 ms) belongs to the original domain Heartbeat.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.9 kB (9%)

Content Size

761.5 kB

After Optimization

693.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heartbeat.ai main page is 761.5 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. 55% of websites need less resources to load. Images take 624.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 58.8 kB

  • Original 71.4 kB
  • After minification 56.3 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 15.1 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.8 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 5.9 kB

  • Original 624.5 kB
  • After minification 618.7 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. Heartbeat images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 3.2 kB

  • Original 55.8 kB
  • After minification 55.8 kB
  • After compression 52.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 9.8 kB
  • After minification 9.8 kB
  • After compression 9.8 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. Heartbeat.ai has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heartbeat.ai

heartbeat.ai

173 ms

heartbeat.ai

heartbeat.ai

454 ms

gtm.js

gtm.js

91 ms

landings.min.css

landings.min.css

40 ms

jquery.min.js

jquery.min.js

47 ms

js

js

126 ms

all.css

all.css

81 ms

grid.min.css

grid.min.css

72 ms

healthcare.js

healthcare.js

78 ms

widget.js

widget.js

106 ms

landings.js

landings.js

133 ms

gtm.js

gtm.js

59 ms

hand-o-up.svg

hand-o-up.svg

76 ms

logo_healthcare.svg

logo_healthcare.svg

132 ms

dignity_health.svg

dignity_health.svg

172 ms

aspen_dental.svg

aspen_dental.svg

130 ms

chen_med.svg

chen_med.svg

168 ms

vault.svg

vault.svg

167 ms

village_md.svg

village_md.svg

170 ms

main-landing.png

main-landing.png

340 ms

main-landing-mobile.png

main-landing-mobile.png

212 ms

coral-tick.png

coral-tick.png

236 ms

hc-feature-1.jpg

hc-feature-1.jpg

305 ms

hc-feature-1-mobile.jpeg

hc-feature-1-mobile.jpeg

303 ms

speciality_1.png

speciality_1.png

291 ms

speciality_1-mobile.png

speciality_1-mobile.png

282 ms

heartbeat-finding-results.png

heartbeat-finding-results.png

341 ms

heartbeat-finding-results-mobile.png

heartbeat-finding-results-mobile.png

336 ms

strategist-avatar.png

strategist-avatar.png

336 ms

village-MD.svg

village-MD.svg

333 ms

heart-white.svg

heart-white.svg

337 ms

mailCircleSVG.svg

mailCircleSVG.svg

367 ms

twitterCircleSVG.svg

twitterCircleSVG.svg

379 ms

linkedINCircleSVG.svg

linkedINCircleSVG.svg

381 ms

facebookCircleSVG.svg

facebookCircleSVG.svg

379 ms

instagramCircleSVG.svg

instagramCircleSVG.svg

382 ms

national_association_large.svg

national_association_large.svg

402 ms

logo_healthcare_footer.svg

logo_healthcare_footer.svg

399 ms

sweetalert.min.js

sweetalert.min.js

26 ms

fa-solid-900.woff

fa-solid-900.woff

19 ms

fa-regular-400.woff

fa-regular-400.woff

22 ms

popups.css

popups.css

36 ms

style.min.css

style.min.css

52 ms

footer.css

footer.css

53 ms

MuseoSansCyrl_2.otf

MuseoSansCyrl_2.otf

50 ms

MuseoSansCyrl_1.otf

MuseoSansCyrl_1.otf

50 ms

MuseoSansCyrl_0.otf

MuseoSansCyrl_0.otf

45 ms

service-comparison-include.css

service-comparison-include.css

28 ms

widget.js

widget.js

38 ms

insight.min.js

insight.min.js

33 ms

Accessibility Review

heartbeat.ai accessibility score

88

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.

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

Form elements do not have associated labels

Best Practices

heartbeat.ai 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

High

Page has valid source maps

SEO Factors

heartbeat.ai SEO score

93

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

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 Heartbeat.ai 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 Heartbeat.ai 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

heartbeat.ai

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