Website review, no card needed

hvcmd.com logo

hvcmd.com website review

Visit site (opens in a new tab)Reviewed 18 October 202638 issues · 90 checks

This review found 38 issues worth fixing on hvcmd.com, 14 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.6 sApr 25Oct 101.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.9 s
May 2, 20261.9 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
96 ms79 msApr 25Oct 1094 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202690 ms
May 2, 202687 ms
May 9, 202683 ms
May 16, 202684 ms
May 23, 202681 ms
May 30, 202682 ms
Jun 6, 202687 ms
Jun 13, 202685 ms
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202684 ms
Jul 11, 202686 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202688 ms
Aug 15, 202689 ms
Aug 22, 202692 ms
Aug 29, 202693 ms
Sep 5, 202690 ms
Sep 12, 202691 ms
Sep 19, 202688 ms
Sep 26, 202693 ms
Oct 3, 202694 ms
Oct 10, 202694 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of hvcmd.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hvcmd.com at 0.4 s0.4 s
  2. hvcmd.com at 0.8 s0.8 s
  3. hvcmd.com at 1.1 s1.1 s
  4. hvcmd.com at 1.5 s1.5 s
  5. hvcmd.com at 1.9 s1.9 s
  6. hvcmd.com at 2.3 s2.3 s
  7. hvcmd.com at 2.6 s2.6 s
  8. hvcmd.com at 3.0 s3.0 s

Speed

13 to fix34
  • Reduce unused JavaScript

    4.8 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.

  • Render-blocking requests

    1.8 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34 (desktop: 90). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.5 s

    A phone's processor spends 5.5 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,006 HTML elements

    The page has 3,006 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and jotfor.ms and others), adding 3.4 MB and 2.2 s of main-thread time.

  • Improve image delivery

    600 ms · 1.6 MB

    10 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    500 ms · 434 KiB

    102 files are served with short cache lifetimes, so returning visitors download them again (434 KiB).

  • Google CDN adds 749 ms

    749 ms

    Google CDN costs a phone 749 ms of main-thread work and 1.5 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 756 ms

    756 ms

    Google Tag Manager costs a phone 756 ms of main-thread work and 679 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    660 ms · 124 KiB

    About 124 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 660 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 369 ms. During a long task the page ignores taps.

  • jotfor.ms adds 235 ms

    235 ms

    jotfor.ms costs a phone 235 ms of main-thread work and 769 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Minify JavaScript

    150 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Phones get a much slower page than desktops

    Desktop scores 90 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • First Contentful Paint: 14.4 s

    14.4 s

    The first text or image appears after 14.4 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 22.8 s

    22.8 s

    Your largest element takes 22.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Heart and Vascular Care, we believe healthcare should be…”.

  • Time to Interactive: 30.6 s

    30.6 s

    The page becomes fully interactive after 30.6 s. Good is under 3.8 s.

  • Speed Index: 14.4 s

    14.4 s

    Visually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 912 ms

    912 ms

    Scripts block taps and scrolling for 912 ms in total while the page loads. Good is under 200 ms.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 90 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 97 ms

    97 ms

    Real visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 361 ms

    361 ms

    Real visitors wait 361 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 7.9 MB in 203 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 203 requests on a phone: images 3.1 MB (85), scripts 2.8 MB (44) and other files 855 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image far larger than shown

    14 KiB

    1 image is downloaded at several times the size a phone draws it, for example Castle Connolly2026png.png at 390 px wide, shown at 121 px. Resized copies would save about 14 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (111 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 267.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8892
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7789
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 135 internal links, 11 external

    The homepage links to 135 pages on hvcmd.com and 11 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Get advanced cardiovascular care at Heart and Vascular Care in Atlanta. Leading-edge treatments, dedicated emergency se…”.

  • One H1 headline

    Your main headline reads: “Your Home for Heart Care”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Cardiology and Vascular Care | Heart and Vascular Care Atlanta”.

  • Canonical URL set

    The canonical URL is https://hvcmd.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://hvcmd.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://hvcmd.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,291 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://hvcmd.com/locations has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 100 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

    3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,589 words of copy

    The homepage carries about 1,589 words of visible text.

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Schedule Appointment” and “Schedule Appointment Now”.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • 29 other companies contacted

    Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hvcmd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on hvcmd.com, including 19 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25