Website review, no card needed
handsofhopeny.com website review
Visit site (opens in a new tab)Reviewed 3 November 202612 issues · 72 checks
This review found 12 issues worth fixing on handsofhopeny.com, 0 of them high impact, across 72 checks. 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
95AClosest 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.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 114 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 143 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 116 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 107 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 124 ms |
| Oct 31, 2026 | 132 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
1,681 HTML elements
The page has 1,681 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (nxedge.io, zocdoc.com and Adobe TypeKit), adding 1.3 MB and 3 ms of main-thread time.
nxedge.io adds 3 ms
3 msnxedge.io costs a phone 3 ms of main-thread work and 1.2 MB 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.
Improve image delivery
31 KiB2 images could be 31 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
15 KiBAbout 15 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
5 KiB2 files are served with short cache lifetimes, so returning visitors download them again (5 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.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 57 ms of it running JavaScript. That is comfortably low.
Server response: 44 ms
44 msYour server sent the HTML in 44 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 114 ms to 132 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Discover Comprehensive Physical Therapy & Pain Management w…”.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.2 s
1.2 sThe page is fully interactive after 1.2 s.
Images and page weight
7 images below the first screen load straight away
7 images further down the page (162 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (30 KiB) is 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 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.4 MB in 82 requests
1.4 MBYour homepage downloads 1.4 MB in 82 requests on a phone: images 1.2 MB (75), fonts 121 KiB (4) and HTML 64 KiB (1). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
46 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: 46 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Discover Comprehensive Physical Therapy & Pain Ma…” and “Discover Comprehensive Physical Therapy & Pain Ma…”). One clear main headline is easier for people and search engines.
315 internal links, 45 external
The homepage links to 315 pages on handsofhopeny.com and 45 external pages.
7 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “Hands of Hope Physical Therapy in NY provides the best support for your journey to wellness. Come see us today!”.
Title: 55 characters
Your title is a healthy 55 characters: “Comprehensive Physical Therapy in NY - Hands of Hope PT”.
Canonical URL set
The canonical URL is https://handsofhopeny.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, MedicalBusiness, Organization and WebPage.
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://handsofhopeny.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://handsofhopeny.com/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 (1,896 words), so crawlers that don't run JavaScript still read it.
Other pages
5 linked pages hidden from search
https://handsofhopeny.com/location-category/brooklyn, https://handsofhopeny.com/location-category/queens, https://handsofhopeny.com/location-category/manhattan, https://handsofhopeny.com/location-category/bronx and https://handsofhopeny.com/location-category/staten-island are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
9 pages without a meta description
https://handsofhopeny.com/our-team, https://handsofhopeny.com/our-partners, https://handsofhopeny.com/our-award, https://handsofhopeny.com/brand-awareness, https://handsofhopeny.com/location-category/brooklyn and https://handsofhopeny.com/location-category/queens and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 133 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
33 distorted images
33 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
133 of 135 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 917 words of copy
The homepage carries about 917 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “REQUEST APPOINTMENT”.
22 calls to action
The homepage has 22 calls to action, for example “Contact”, “Request Appointment” and “Book ZocDoc”.
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 27 testimonial or review blocks, 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 20 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
3 other companies contacted
Loading the homepage contacts 3 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 handsofhopeny.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
- Google Tag Manager | Hotjar | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 12 issues on handsofhopeny.com, including 4 speed issues, 1 SEO issue 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.