Website review, no card needed

heritagemedical.com logo

heritagemedical.com website review

Visit site (opens in a new tab)Reviewed 27 October 202631 issues · 83 checks

This review found 31 issues worth fixing on heritagemedical.com, 9 of them high impact, across 83 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
1.8 s1.6 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 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.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
98 ms90 msMay 9Oct 2496 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202694 ms
May 16, 202694 ms
May 23, 202695 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202697 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 202694 ms
Jul 18, 202693 ms
Jul 25, 202692 ms
Aug 1, 202691 ms
Aug 8, 202693 ms
Aug 15, 202692 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202692 ms
Sep 12, 202696 ms
Sep 19, 202695 ms
Sep 26, 202694 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202696 ms
Oct 24, 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 heritagemedical.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. heritagemedical.com at 1.2 s1.2 s
  2. heritagemedical.com at 2.5 s2.5 s
  3. heritagemedical.com at 3.7 s3.7 s
  4. heritagemedical.com at 4.9 s4.9 s
  5. heritagemedical.com at 6.2 s6.2 s
  6. heritagemedical.com at 7.4 s7.4 s
  7. heritagemedical.com at 8.6 s8.6 s
  8. heritagemedical.com at 9.9 s9.9 s

Speed

6 to fix56
  • Reduce unused JavaScript

    2.1 s · 380 KiB

    About 380 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.

  • Mobile performance score: 56

    56/100

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

  • Render-blocking requests

    850 ms

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

  • Legacy JavaScript

    600 ms · 71 KiB

    Polyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 36 KiB

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

  • Google Tag Manager adds 202 ms

    202 ms

    Google Tag Manager costs a phone 202 ms of main-thread work and 317 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and typeform.com and others), adding 434 KiB and 268 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 56. 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.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 62 ms

    62 ms

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

Core Web Vitals

5 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 text “Comprehensive, Compassionate, Customized. Forward-thinking,…”. Most of its time is resource load duration (7.9 s).

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Time to Interactive: 12.4 s

    12.4 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • 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

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s 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.8 s

    1.8 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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.1 s

    1.1 s

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

  • Real-user TTFB: 634 ms

    634 ms

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

  • Cumulative Layout Shift: 0.053

    0.053

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

  • Total Blocking Time: 89 ms

    89 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.53 g

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

4 checks passed
  • Page weight: 1.9 MB in 50 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 50 requests on a phone: scripts 1.0 MB (13), other files 544 KiB (21) and images 218 KiB (11). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9292
  • Hidden but focusable

    36 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (8 elements)

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

7 to fixGoogle 9165
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (27 characters)

    Your title is only 27 characters: “Heritage Medical Associates”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 42 links with vague text

    42 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (739 characters)

    Your meta description is 739 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No robots.txt

    There is no robots.txt at heritagemedical.com/robots.txt, the first file search crawlers ask for.

  • 117 internal links, 7 external

    The homepage links to 117 pages on heritagemedical.com and 7 external pages.

2 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.heritagemedical.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://www.heritagemedical.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 4 pages share 2 titles

    / and https://www.heritagemedical.com/specialties all use the title “Heritage Medical Associates”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.heritagemedical.com/specialties, https://www.heritagemedical.com/patient-info/medical-records-release, https://www.heritagemedical.com/topic/patient-education and https://www.heritagemedical.com/topic/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.heritagemedical.com/providers, https://www.heritagemedical.com/patient-info/rights-responsibilities and https://www.heritagemedical.com/careers use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.heritagemedical.com/locations has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 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 an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 10093
  • 12 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 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 913 words of copy

    The homepage carries about 913 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request Appointment” and “LEARN MORE”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Request Appointment”, “Learn More” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

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

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

  • 7 other companies contacted

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

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 heritagemedical.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
Gatsby
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on heritagemedical.com, including 11 speed issues, 7 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