Website review, no card needed

prinehealth.com logo

prinehealth.com website review

Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 85 checks

This review found 32 issues worth fixing on prinehealth.com, 4 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.0 s1.1 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.4 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.2 s
Aug 22, 20262.0 s
Aug 29, 20261.8 s
Sep 5, 20261.6 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.8 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
132 ms73 msMay 2Oct 17109 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202681 ms
May 9, 202685 ms
May 16, 202689 ms
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202693 ms
Jun 27, 202687 ms
Jul 4, 202683 ms
Jul 11, 202680 ms
Jul 18, 202684 ms
Jul 25, 202683 ms
Aug 1, 202684 ms
Aug 8, 202698 ms
Aug 15, 2026125 ms
Aug 22, 2026112 ms
Aug 29, 2026105 ms
Sep 5, 202691 ms
Sep 12, 202685 ms
Sep 19, 202687 ms
Sep 26, 202694 ms
Oct 3, 2026103 ms
Oct 10, 2026106 ms
Oct 17, 2026109 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 prinehealth.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix59
  • Reduce unused JavaScript

    900 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Use efficient cache lifetimes

    650 ms · 805 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, jotfor.ms and jotform.com and others), adding 3.0 MB and 966 ms of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • Google Tag Manager adds 610 ms

    610 ms

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

    450 ms · 123 KiB

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

  • jotfor.ms adds 237 ms

    237 ms

    jotfor.ms costs a phone 237 ms of main-thread work and 1.9 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.

  • Improve image delivery

    371 KiB

    1 image could be 371 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1,571 HTML elements

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    16 KiB

    16 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    10 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 179 ms

    179 ms

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

Core Web Vitals

9 to fix100
  • Fails Core Web Vitals for real visitors

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

  • Time to Interactive: 23.2 s

    23.2 s

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

  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PRINE Health Multidisciplinary Health Experts Empowering He…”.

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 899 ms

    899 ms

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Total Blocking Time: 415 ms

    415 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

1 to fix85
  • Page weight: 3.9 MB in 107 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 107 requests on a phone: scripts 1.9 MB (45), fonts 998 KiB (11) and images 650 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.11 g

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

3 checks passed
  • 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 9294
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 80 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9295
  • No social preview image

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

  • 10 links with vague text

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

  • 101 internal links, 23 external

    The homepage links to 101 pages on prinehealth.com and 23 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “PRINE Health specializes in chronic kidney disease, combining Nephrologists, Primary Care, and specialists for comprehe…”.

  • One H1 headline

    Your main headline reads: “PRINE Health”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Expert Care for Chronic Kidney Disease at PRINE Health”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, CommunityHealth, ImageObject, Organization and Person.

  • 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://prinehealth.com/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://prinehealth.com/llms.txt (111 KiB, 457 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 2 pages without an H1

    https://prinehealth.com/specialty/podiatry and https://prinehealth.com/specialty/infusion have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://prinehealth.com/specialty/podiatry 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.

  • 1 page slow to respond

    https://prinehealth.com/nutrition took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 44 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

1 to fixGoogle 10093
  • 5 small tap targets

    5 of 16 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

3 to fix85
  • 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.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (1 required). Every extra field lowers completion.

  • No map or directions link

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

  • About 600 words of copy

    The homepage carries about 600 words of visible text.

7 checks passed
  • Clear next step on the first screen

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

  • 25 calls to action

    The homepage has 25 calls to action, for example “Contact Us”, “Request an Appointment” and “Join Us”.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and Cloudflare Web Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 1 of them by other companies (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.

  • 19 other companies contacted

    Loading the homepage contacts 19 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 prinehealth.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on prinehealth.com, including 18 speed issues, 2 SEO issues and 3 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