Website review, no card needed
familycarenetwork.com website review
Visit site (opens in a new tab)Reviewed 29 October 202630 issues · 86 checks
This review found 30 issues worth fixing on familycarenetwork.com, 14 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 81 ms |
| May 16, 2026 | 83 ms |
| May 23, 2026 | 84 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 84 ms |
| Jun 13, 2026 | 82 ms |
| Jun 20, 2026 | 80 ms |
| Jun 27, 2026 | 80 ms |
| Jul 4, 2026 | 80 ms |
| Jul 11, 2026 | 81 ms |
| Jul 18, 2026 | 82 ms |
| Jul 25, 2026 | 84 ms |
| Aug 1, 2026 | 85 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 85 ms |
| Sep 19, 2026 | 84 ms |
| Sep 26, 2026 | 84 ms |
| Oct 3, 2026 | 84 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 85 ms |
| Oct 24, 2026 | 86 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.7 s · 893 KiBAbout 893 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
1.1 s26 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 1.9 MB and 1.5 s of main-thread time.
YouTube adds 712 ms
712 msYouTube costs a phone 712 ms of main-thread work and 980 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 684 ms
684 msGoogle CDN costs a phone 684 ms of main-thread work and 734 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.
Font display
750 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).
Reduce unused CSS
300 ms · 106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
350 ms · 55 KiB5 images could be 55 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 362 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
6 KiB6 files are served with short cache lifetimes, so returning visitors download them again (6 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: 67 ms
67 msYour server sent the HTML in 67 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.5 s
12.5 sYour largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “…”.
Time to Interactive: 19.8 s
19.8 sThe page becomes fully interactive after 19.8 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.203
0.203The layout shifts by 0.203 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 81 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 85 ms
85 msReal visitors wait 85 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 727 ms
727 msReal visitors wait 727 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.0 MB in 98 requests
4.0 MBYour homepage downloads 4.0 MB in 98 requests on a phone: scripts 1.8 MB (33), images 1.4 MB (14) and other files 350 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (70 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.1 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 137.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (220 characters)
Your meta description is 220 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
127 internal links, 8 external
The homepage links to 127 pages on familycarenetwork.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Healthcare for the whole family”.
Title: 62 characters
Your title is a healthy 62 characters: “Family Care Network | Clinics & Urgent Care | Skagit & Whatcom”.
Canonical URL set
The canonical URL is https://www.familycarenetwork.com/.
Structured data in place
Structured data found: MedicalBusiness, MedicalOrganization, SiteNavigationElement and WebSite.
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://www.familycarenetwork.com/sitemap_index.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,420 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.familycarenetwork.com/llms.txt (4 KiB, 35 links), a plain-text guide to the site for AI tools.
Other pages
1 page slow to respond
https://www.familycarenetwork.com/clinics/sports-medicine took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 found) and read each the way a search engine does.
7 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.
Every page has an H1
Each page we checked has a main headline.
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
6 small tap targets
6 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestor…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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: “more than 100,000 patients”. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
About 607 words of copy
The homepage carries about 607 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “After Hours Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Matomo and Cloudflare Web Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
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.
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 familycarenetwork.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
- Matomo
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on familycarenetwork.com, including 17 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.