Website review, no card needed

healthgrades.com logo

healthgrades.com website review

Visit site (opens in a new tab)Reviewed 11 October 202625 issues · 65 checks

This review found 25 issues worth fixing on healthgrades.com, 6 of them high impact, across 65 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.7 s1.4 sApr 18Oct 32.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.6 s
Apr 25, 20261.6 s
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20262.1 s
Sep 19, 20262.3 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
97 ms86 msApr 18Oct 396 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202692 ms
Apr 25, 202690 ms
May 2, 202689 ms
May 9, 202689 ms
May 16, 202689 ms
May 23, 202689 ms
May 30, 202690 ms
Jun 6, 202690 ms
Jun 13, 202690 ms
Jun 20, 202689 ms
Jun 27, 202689 ms
Jul 4, 202689 ms
Jul 11, 202688 ms
Jul 18, 202688 ms
Jul 25, 202688 ms
Aug 1, 202688 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202688 ms
Sep 12, 202691 ms
Sep 19, 202694 ms
Sep 26, 202696 ms
Oct 3, 202696 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 healthgrades.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix58
  • Reduce unused JavaScript

    2.1 s · 363 KiB

    About 363 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Use efficient cache lifetimes

    750 ms · 289 KiB

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    400 ms

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

  • awswaf.com adds 148 ms

    148 ms

    awswaf.com costs a phone 148 ms of main-thread work and 310 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (awswaf.com, rvohealth.com and Optanon and others), adding 681 KiB and 324 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Improve image delivery

    77 KiB

    5 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 58. 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.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 980 ms of it running JavaScript. That is comfortably low.

  • Server response: 48 ms

    48 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 12.3 s

    12.3 s

    Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Healthcare professionals found on Healthgrades”.

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 12.3 s

    12.3 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Largest content (LCP) got 59% slower for real visitors

    +59%

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

8 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.1 s

    1.1 s

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

  • Real-user INP: 121 ms

    121 ms

    Real visitors wait 121 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.0 s

    1.0 s

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

  • Real-user TTFB: 504 ms

    504 ms

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

  • Total Blocking Time: 111 ms

    111 ms

    Scripts block the page for only 111 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.52 g

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

1 checks passed
  • Page weight: 1.8 MB in 107 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 107 requests on a phone: scripts 915 KiB (30), HTML 476 KiB (3) and images 162 KiB (14). That is a lean page.

Accessibility

3 to fixGoogle 9794
  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 22 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Healthgrades | Find a Doctor - Doctor Reviews - Online Doctor Appointments”.

  • 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 124 internal links, 60 external

    The homepage links to 124 pages on healthgrades.com and 60 external pages.

5 checks passed
  • Meta description: 105 characters

    Your meta description is 105 characters: “Healthgrades is the leading online resource for comprehensive information about physicians and hospitals.”.

  • One H1 headline

    Your main headline reads: “Feel better about finding healthcare”.

  • Canonical URL set

    The canonical URL is https://www.healthgrades.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.healthgrades.com/sitemapindex.xml.

AI search readiness

1 to fix83
  • 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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • llms.txt published

    The site publishes https://www.healthgrades.com/llms.txt (3 KiB, 28 links), a plain-text guide to the site for AI tools.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 7789
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 46 words

    The homepage has only about 46 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn More about Healthgrades”, “Account Sign Up / Log In” and “Contact Us”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

Privacy and tracking

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 healthgrades.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
Next.js
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on healthgrades.com, including 11 speed issues, 3 SEO issues and 5 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