Website review, no card needed

wncchs.org logo

wncchs.org website review

Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 83 checks

This review found 39 issues worth fixing on wncchs.org, 20 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
3.4 s2.1 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
124 ms92 msMay 2Oct 17115 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202696 ms
May 16, 202696 ms
May 23, 2026100 ms
May 30, 202698 ms
Jun 6, 2026102 ms
Jun 13, 2026106 ms
Jun 20, 2026106 ms
Jun 27, 2026111 ms
Jul 4, 2026111 ms
Jul 11, 2026109 ms
Jul 18, 2026107 ms
Jul 25, 2026108 ms
Aug 1, 2026107 ms
Aug 8, 2026105 ms
Aug 15, 2026111 ms
Aug 22, 2026114 ms
Aug 29, 2026113 ms
Sep 5, 2026120 ms
Sep 12, 2026120 ms
Sep 19, 2026114 ms
Sep 26, 2026116 ms
Oct 3, 2026109 ms
Oct 10, 2026108 ms
Oct 17, 2026115 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 wncchs.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wncchs.org at 2.2 s2.2 s
  2. wncchs.org at 4.4 s4.4 s
  3. wncchs.org at 6.7 s6.7 s
  4. wncchs.org at 8.9 s8.9 s
  5. wncchs.org at 11.1 s11.1 s
  6. wncchs.org at 13.3 s13.3 s
  7. wncchs.org at 15.5 s15.5 s
  8. wncchs.org at 17.8 s17.8 s

Speed

14 to fix30
  • Reduce unused JavaScript

    3.0 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Improve image delivery

    2.1 s · 1.2 MB

    11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Google Tag Manager adds 3.2 s

    3.2 s

    Google Tag Manager costs a phone 3.2 s of main-thread work and 503 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Squarespace adds 2.8 s

    2.8 s

    Squarespace costs a phone 2.8 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 21.2 s

    A phone's processor spends 21.2 s on main-thread work while loading, 9.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Render-blocking requests

    1.6 s

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

  • Google CDN adds 1.0 s

    1.0 s

    Google CDN costs a phone 1.0 s of main-thread work and 801 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30 (desktop: 49). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Squarespace and Google CDN and others), adding 3.0 MB and 7.9 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 2.1 s. During a long task the page ignores taps.

  • Reduce unused CSS

    610 ms · 200 KiB

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

  • Other Google APIs/SDKs adds 427 ms

    427 ms

    Other Google APIs/SDKs costs a phone 427 ms of main-thread work and 150 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.

  • Legacy JavaScript

    300 ms · 120 KiB

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

  • StackAdapt adds 270 ms

    270 ms

    StackAdapt costs a phone 270 ms of main-thread work and 11 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.

  • Use efficient cache lifetimes

    36 KiB

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

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

1 checks passed
  • Server response: 78 ms

    78 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DSC_1006.jpg”. Most of its time is resource load delay (6.1 s).

  • Total Blocking Time: 7.8 s

    7.8 s

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

  • Time to Interactive: 29.3 s

    29.3 s

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

  • Speed Index: 14.3 s

    14.3 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

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

    +28%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.2 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) got 16% slower for real visitors

    +16%

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

5 checks passed
  • Real-user INP: 112 ms

    112 ms

    Real visitors wait 112 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.5 s

    1.5 s

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

  • Real-user TTFB: 613 ms

    613 ms

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

  • Cumulative Layout Shift: 0.012

    0.012

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

Images and page weight

2 to fix55
  • Page weight: 6.0 MB in 140 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 140 requests on a phone: scripts 2.7 MB (76), images 2.4 MB (17) and other files 494 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    TV+Screen+Templates+(11+x+8.5+in)+(8.5+x+11+in).png weighs 1.0 MB. On a phone connection a single image that size takes seconds.

  • 4 images below the first screen load straight away

    4 images further down the page (246 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.70 g

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

2 checks passed
  • 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

4 to fixGoogle 9795
  • 2 text elements with low contrast

    2 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 (2 elements)

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

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8575
  • No meta description

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

  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/65c50ea082a5e34b825…”.

  • 3 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 184 internal links, 4 external

    The homepage links to 184 pages on wncchs.org and 4 external pages.

4 checks passed
  • Title: 48 characters

    Your title is a healthy 48 characters: “Western North Carolina Community Health Services”.

  • Canonical URL set

    The canonical URL is https://www.wncchs.org/.

  • 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.wncchs.org/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.wncchs.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.

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.wncchs.org/pricing-payment, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a meta description

    https://www.wncchs.org/about, https://www.wncchs.org/leadership, https://www.wncchs.org/impact, https://www.wncchs.org/partners, https://www.wncchs.org/contact and https://www.wncchs.org/blog and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.wncchs.org/about, https://www.wncchs.org/leadership, https://www.wncchs.org/impact, https://www.wncchs.org/providers, https://www.wncchs.org/appointment and https://www.wncchs.org/mychart and 4 others 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 56 found) and read each the way a search engine does.

4 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 471 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Us: (828) 285-0622”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact”, “Request an Appointment” and “Pricing & Payment”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 trust badge and “more than 13,000 patients”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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.

  • 10 cookies set on arrival

    10

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 wncchs.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
Squarespace
Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on wncchs.org, including 23 speed issues and 4 SEO issues. 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