Website review, no card needed

dvch.org logo

dvch.org website review

Visit site (opens in a new tab)Reviewed 2 November 202622 issues · 61 checks

This review found 22 issues worth fixing on dvch.org, 4 of them high impact, across 61 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
990 ms270 msMay 16Oct 31907 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026795 ms
May 23, 2026675 ms
May 30, 2026571 ms
Jun 6, 2026532 ms
Jun 13, 2026675 ms
Jun 20, 2026771 ms
Jun 27, 2026901 ms
Jul 4, 2026905 ms
Jul 11, 2026884 ms
Jul 18, 2026832 ms
Jul 25, 2026794 ms
Aug 1, 2026741 ms
Aug 8, 2026646 ms
Aug 15, 2026562 ms
Aug 22, 2026449 ms
Aug 29, 2026403 ms
Sep 5, 2026353 ms
Sep 12, 2026433 ms
Sep 19, 2026520 ms
Sep 26, 2026637 ms
Oct 3, 2026672 ms
Oct 10, 2026537 ms
Oct 17, 2026794 ms
Oct 24, 2026850 ms
Oct 31, 2026907 ms
Real-visitor tap response (INP)75th percentile, phones
101 ms76 msMay 16Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202684 ms
May 23, 202682 ms
May 30, 202684 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202691 ms
Jul 4, 202689 ms
Jul 11, 202691 ms
Jul 18, 202692 ms
Jul 25, 202687 ms
Aug 1, 202683 ms
Aug 8, 202682 ms
Aug 15, 202679 ms
Aug 22, 202680 ms
Aug 29, 202685 ms
Sep 5, 202685 ms
Sep 12, 202691 ms
Sep 19, 202693 ms
Sep 26, 202696 ms
Oct 3, 202698 ms
Oct 10, 202694 ms
Oct 17, 202696 ms
Oct 24, 202694 ms
Oct 31, 202688 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 dvch.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix73
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused CSS

    600 ms · 121 KiB

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

  • Improve image delivery

    300 ms · 81 KiB

    2 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    21 KiB

    About 21 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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: 0.6 s

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

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.5 s

    5.5 s

    Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “COMMUNITY FOCUSED HEALTH CARE Providing affordable, accessi…”.

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

    +20%

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Time to Interactive: 5.6 s

    5.6 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

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

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 84 ms to 88 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: 0.3 s

    0.3 s

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

  • Real-user INP: 75 ms

    75 ms

    Real visitors wait 75 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: 0.3 s

    0.3 s

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

  • Real-user TTFB: 85 ms

    85 ms

    Real visitors wait 85 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).

  • Total Blocking Time: 2 ms

    2 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.28 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 33.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,019 KiB in 97 requests

    1,019 KiB

    Your homepage downloads 1,019 KiB in 97 requests on a phone: images 395 KiB (19), scripts 225 KiB (66) and fonts 174 KiB (5). That is a lean page.

Accessibility

3 to fix84
  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • 6 text elements with low contrast

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

  • Links look like plain text

    4 links inside paragraphs rely on colour alone to stand out.

SEO

4 to fixGoogle 7777
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Delaware Valley Community Health – Community Focused Health Care For All”.

  • No structured data

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 55 internal links, 9 external

    The homepage links to 55 pages on dvch.org and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Community Focused Health Care”.

  • Canonical URL set

    The canonical URL is https://dvch.org/.

  • Open Graph tags complete

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

  • 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://dvch.org/wp-sitemap.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.

  • No llms.txt

    There is no https://dvch.org/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.

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://dvch.org/patient-portal, https://dvch.org/residency, https://dvch.org/about-us, https://dvch.org/history, https://dvch.org/support and https://dvch.org/contact-dvch and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://dvch.org/patient-portal and https://dvch.org/author/jbranco have 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 18 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.

  • 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

Google 100100
1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix70
  • Thin social proof

    Social proof on the homepage: 10 trust badges. 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.

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

    The homepage carries about 758 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “CONTACT DVCH”, “SCHEDULE AN APPOINTMENT” and “Contact DVCH”.

  • 2 short forms

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

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 dvch.org, 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
Hosting
Cloudflare

Company

Employees
323

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on dvch.org, including 9 speed issues, 4 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