Website review, no card needed

proclaimhealth.com logo

proclaimhealth.com website review

Visit site (opens in a new tab)Reviewed 13 November 202626 issues · 73 checks

This review found 26 issues worth fixing on proclaimhealth.com, 7 of them high impact, across 73 checks. The most urgent: render-blocking requests. 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.2 s789 msMay 23Aug 8888 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026994 ms
May 30, 20261.0 s
Jun 6, 2026899 ms
Jun 13, 2026831 ms
Jun 20, 2026886 ms
Jun 27, 2026988 ms
Jul 4, 20261.0 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 2026980 ms
Aug 8, 2026888 ms
Real-visitor tap response (INP)75th percentile, phones
107 ms89 msMay 23Jul 1898 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 2026105 ms
Jun 20, 2026104 ms
Jun 27, 202696 ms
Jul 4, 202691 ms
Jul 18, 202698 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 proclaimhealth.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. proclaimhealth.com at 0.6 s0.6 s
  2. proclaimhealth.com at 1.2 s1.2 s
  3. proclaimhealth.com at 1.7 s1.7 s
  4. proclaimhealth.com at 2.3 s2.3 s
  5. proclaimhealth.com at 2.9 s2.9 s
  6. proclaimhealth.com at 3.5 s3.5 s
  7. proclaimhealth.com at 4.1 s4.1 s
  8. proclaimhealth.com at 4.7 s4.7 s

Speed

6 to fix60
  • Render-blocking requests

    4.7 s

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

  • Reduce unused JavaScript

    2.4 s · 422 KiB

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

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (website-files.com, Google CDN and cloudfront.net and others), adding 1.4 MB and 424 ms of main-thread time.

  • website-files.com adds 293 ms

    293 ms

    website-files.com costs a phone 293 ms of main-thread work and 934 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.

  • Google CDN adds 98 ms

    98 ms

    Google CDN costs a phone 98 ms of main-thread work and 359 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

    150 ms · 44 KiB

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

  • 4 long tasks on the main thread

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

  • Improve image delivery

    70 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Connect With Us! BETTER OVERALL HEALTH. LOWER COSTS. STRONG…”.

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Time to Interactive: 8.3 s

    8.3 s

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

  • 8 images without width and height

    8 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-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -6%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 98 ms

    98 ms

    Scripts block the page for only 98 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

1 to fix97
  • An image on the first screen is lazy-loaded

    6a306fec752dfc0129d9cfdf_Hero%20Shape%20One-p-500.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.4 g of CO₂ per visit

    0.44 g

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

3 checks passed
  • Page weight: 1.6 MB in 37 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 37 requests on a phone: scripts 832 KiB (9), images 544 KiB (12) and fonts 154 KiB (10). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

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

    All page content should be contained by landmarks: 7 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.

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

5 to fixGoogle 10078
  • Title is short (22 characters)

    Your title is only 22 characters: “Home | Proclaim Health”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://proclaimhealth.com/sitemap.xml, so Google discovers your pages only by following links.

  • 16 internal links, 11 external

    The homepage links to 16 pages on proclaimhealth.com and 11 external pages.

3 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Leading oral systemic platform connecting oral health to outcomes. $3 ROI per $1 invested, 41% cost reduction. AI-power…”.

  • One H1 headline

    Your main headline reads: “Proclaim's closed loop home care: data matched by outcomes”.

  • robots.txt in place

    robots.txt is in place.

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://proclaimhealth.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 (299 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 linked pages hidden from search

    https://proclaimhealth.com/home-care-protocol and https://proclaimhealth.com/resources are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://proclaimhealth.com/shopaddons, https://proclaimhealth.com/terms-of-sale and https://proclaimhealth.com/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages with very little text

    https://proclaimhealth.com/shopaddons and https://proclaimhealth.com/contact have 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.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    8 pages of 9 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    5 of 5 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 283 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop Add Ons” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 proclaimhealth.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics
Hosting
Webflow

Company

Headquarters
San Jose

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on proclaimhealth.com, including 11 speed issues, 5 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