Website review, no card needed
jameslwest.org website review
Visit site (opens in a new tab)Reviewed 20 October 202648 issues · 93 checks
This review found 48 issues worth fixing on jameslwest.org, 18 of them high impact, across 93 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 4.5 s |
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.3 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.3 s |
| Jul 18, 2026 | 5.4 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 5.1 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 125 ms |
| May 9, 2026 | 125 ms |
| May 16, 2026 | 125 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 126 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 111 ms |
| Sep 12, 2026 | 101 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 103 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
1.3 s
2.7 s
4.0 s
5.4 s
6.7 s
8.1 s
9.4 s
10.8 s
Speed
Render-blocking requests
3.1 s42 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 71). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
450 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (talkfurther.com, Google CDN and Cookiebot and others), adding 2.0 MB and 1.3 s of main-thread time.
Improve image delivery
850 ms · 657 KiB6 images could be 657 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
Reduce unused CSS
750 ms · 191 KiBAbout 191 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 682 KiB15 files are served with short cache lifetimes, so returning visitors download them again (682 KiB).
talkfurther.com adds 440 ms
440 mstalkfurther.com costs a phone 440 ms of main-thread work and 656 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 307 ms
307 msGoogle CDN costs a phone 307 ms of main-thread work and 736 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
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
2,448 HTML elements
The page has 2,448 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 194 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 34 KiB34 KiB could be saved by minifying JavaScript.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 327 ms
327 msYour server sent the HTML in 327 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.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.9 s
4.9 sReal visitors see the first content after 4.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 15.8 s
15.8 sYour largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The West Center North Texas’ Leading Center for Comprehensi…”.
Time to Interactive: 26.2 s
26.2 sThe page becomes fully interactive after 26.2 s. Good is under 3.8 s.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.3 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 322 ms
322 msScripts block taps and scrolling for 322 ms in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 125 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Images and page weight
Page weight: 7.7 MB in 190 requests
7.7 MBYour homepage downloads 7.7 MB in 190 requests on a phone: images 4.0 MB (36), scripts 2.6 MB (84) and other files 382 KiB (22). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (1.6 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.
15 images below the first screen load straight away
15 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
277 KiB1 image is downloaded at several times the size a phone draws it, for example 113320315372289_1538174381661137.jpg at 2,048 px wide, shown at 360 px. Resized copies would save about 277 KiB.
About 2.2 g of CO₂ per visit
2.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.19 g of CO₂e: 262.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (91 elements)
All page content should be contained by landmarks: 91 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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Orphan list items
Some list items are not inside a list.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Dementia, Alzheimer & Memory Care Services Fort Worth TX |James L. West”.
4 H1 headlines
There are 4 <h1> headlines (“North Texas’ Leading Center for Comprehensive Dem…”, “Senior Day Program Bridges Home and Residential C…” and “Personalized Expert Care in the Comfort of Your H…”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, LocalBusiness and Organization) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected end of JSON input)”.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
200 internal links, 67 external
The homepage links to 200 pages on jameslwest.org and 67 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “James L. West Center provides memory care & support to enhance the quality & dignity of each person’s life throughout t…”.
Canonical URL set
The canonical URL is https://www.jameslwest.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://www.jameslwest.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.jameslwest.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, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,976 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.jameslwest.org/panel declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.jameslwest.org/panel all use the title “Dementia, Alzheimer & Memory Care Services Fort Worth TX |James L. We…”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.jameslwest.org/resources/gallery has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.jameslwest.org/about/charitable-giving, https://www.jameslwest.org/contact-us, https://www.jameslwest.org/about, https://www.jameslwest.org/about/leadership, https://www.jameslwest.org/about/careers and https://www.jameslwest.org/resources/our-blog and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://www.jameslwest.org/about/charitable-giving, https://www.jameslwest.org/contact-us, https://www.jameslwest.org/about, https://www.jameslwest.org/about/leadership, https://www.jameslwest.org/resources/our-blog and https://www.jameslwest.org/resources/events-and-news and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,490 words of copy
The homepage carries about 1,490 words of visible text.
6 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Contact Us”, “Schedule a Visit” and “Learn more”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 jameslwest.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
- 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 48 issues on jameslwest.org, including 24 speed issues, 5 SEO issues and 2 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.