Website review, no card needed
fhw.org website review
Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 86 checks
This review found 34 issues worth fixing on fhw.org, 11 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 83 ms |
| May 23, 2026 | 82 ms |
| May 30, 2026 | 80 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 85 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 91 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 91 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 92 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 92 ms |
| Sep 12, 2026 | 89 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 90 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 88 ms |
| Oct 31, 2026 | 87 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
Speed
Render-blocking requests
9.1 s92 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.1 s.
Reduce unused JavaScript
5.0 s · 967 KiBAbout 967 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
800 ms · 132 KiB2 images could be 132 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 570 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Accessibe Accessibility Overlay and sitescdn.net), adding 401 KiB and 185 ms of main-thread time.
Reduce unused CSS
150 ms · 46 KiBAbout 46 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
7 KiB1 file is served with short cache lifetimes, so returning visitors download them again (7 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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 685 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
First Contentful Paint: 7.9 s
7.9 sThe first text or image appears after 7.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.6 s
18.6 sYour largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Healthcare that feels like home. Schedule an Appointment Fi…”.
Time to Interactive: 18.6 s
18.6 sThe page becomes fully interactive after 18.6 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 604 ms
604 msScripts block taps and scrolling for 604 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
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
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 83 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 144 requests
3.0 MBYour homepage downloads 3.0 MB in 144 requests on a phone: scripts 1.8 MB (76), images 816 KiB (7) and fonts 263 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
115 KiB1 image is downloaded at several times the size a phone draws it, for example FHW-Primary-Logo-Full-Color-On-White.jpg at 1,014 px wide, shown at 103 px. Resized copies would save about 115 KiB.
About 0.8 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 101.7 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
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.
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 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
39 internal links, 9 external
The homepage links to 39 pages on fhw.org and 9 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “At Family Health West, we're here to help you flourish. We provide general care, an ER, and specialty clinics to care f…”.
One H1 headline
Your main headline reads: “Healthcare that feels like home.”.
Title: 42 characters
Your title is a healthy 42 characters: “Family Health West - Together, We Flourish”.
Canonical URL set
The canonical URL is https://fhw.org/.
Structured data in place
Structured data found: Article, FAQPage, Hospital, ImageObject and Organization.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://fhw.org/sitemap.xml.
AI search readiness
No llms.txt
There is no https://fhw.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.
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (300 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://fhw.org/mission-values is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://fhw.org/foundation and https://fhw.org/fhw-foundation all use the title “FHW Foundation | Family Health West”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://fhw.org/foundation and https://fhw.org/fhw-foundation use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://fhw.org/fhw-foundation, whose canonical is https://fhw.org/foundation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://fhw.org/mission-values has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://fhw.org/services and https://fhw.org/patient-resources 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.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
Every page has a meta description
All 14 pages that loaded have a meta description.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 198 words
The homepage has only about 198 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Schedule an Appointment”.
3 calls to action
The homepage has 3 calls to action, for example “Schedule an Appointment” and “How do I schedule an appointment?”.
Direct contact links
Visitors can reach you directly: 1 phone link 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.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 fhw.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
- React
- Hosting
- Cloudflare
Company
- Employees
- 596
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on fhw.org, including 15 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.