Website review, no card needed
valleyhospice.org website review
Visit site (opens in a new tab)Reviewed 24 October 202643 issues · 82 checks
This review found 43 issues worth fixing on valleyhospice.org, 16 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
70CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Use efficient cache lifetimes
9.2 s · 3.3 MB48 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).
Reduce unused JavaScript
5.8 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.
Render-blocking requests
6.5 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.5 s.
Improve image delivery
2.4 s · 1.7 MB12 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Minify JavaScript
1.4 s · 210 KiB210 KiB could be saved by minifying JavaScript.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 38). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 40 KiBAbout 40 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.
Minify CSS
300 ms · 10 KiB10 KiB could be saved by minifying CSS.
Google CDN adds 91 ms
91 msGoogle CDN costs a phone 91 ms of main-thread work and 351 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Twitter and others), adding 767 KiB and 311 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.
Document request latency
16 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 357 ms of it running JavaScript. That is comfortably low.
Server response: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.3 s
14.3 sYour largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 7.4 s
7.4 sThe first text or image appears after 7.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 22.2 s
22.2 sThe page becomes fully interactive after 22.2 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.063
0.063The layout barely moves while loading (CLS 0.063, good is under 0.1).
Total Blocking Time: 50 ms
50 msScripts block the page for only 50 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.5 MB in 94 requests
4.5 MBYour homepage downloads 4.5 MB in 94 requests on a phone: images 2.1 MB (18), scripts 2.0 MB (47) and HTML 149 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
sn0plwebsitebanner_new.jpg weighs 605 KiB. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (1.9 MB) 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.
6 images below the first screen load straight away
6 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Valley Hospice”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 H1 headlines
There are 9 <h1> headlines (“Home Care”, “Patient Comfort” and “Your Team”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.valleyhospice.org/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at valleyhospice.org/robots.txt, the first file search crawlers ask for.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
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.
29 internal links, 3 external
The homepage links to 29 pages on valleyhospice.org and 3 external pages.
2 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Valley Hospice ensures access to care for those living with a life-limiting illness through our commitment to Caring, L…”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
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.valleyhospice.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (334 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a meta description
https://www.valleyhospice.org/what-is-hospice, https://www.valleyhospice.org/our-services, https://www.valleyhospice.org/care-centers, https://www.valleyhospice.org/volunteers, https://www.valleyhospice.org/ways-to-give and https://www.valleyhospice.org/palliative-care and 9 others use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://www.valleyhospice.org/volunteers took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
17 small tap targets
17 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'msie')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 331 words of copy
The homepage carries about 331 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
5 calls to action
The homepage has 5 calls to action, for example “Contact” and “Learn More”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
13 other companies contacted
Loading the homepage contacts 13 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 valleyhospice.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on valleyhospice.org, including 15 speed issues, 8 SEO issues and 1 conversion gap. 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.