Website review, no card needed
adirondackhealth.org website review
Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 84 checks
This review found 36 issues worth fixing on adirondackhealth.org, 9 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 943 ms |
| Jun 6, 2026 | 938 ms |
| Jun 13, 2026 | 895 ms |
| Jun 20, 2026 | 926 ms |
| Jun 27, 2026 | 899 ms |
| Jul 4, 2026 | 936 ms |
| Jul 11, 2026 | 983 ms |
| Jul 18, 2026 | 966 ms |
| Jul 25, 2026 | 974 ms |
| Aug 1, 2026 | 910 ms |
| Aug 8, 2026 | 905 ms |
| Aug 15, 2026 | 896 ms |
| Aug 22, 2026 | 918 ms |
| Aug 29, 2026 | 924 ms |
| Sep 5, 2026 | 942 ms |
| Sep 12, 2026 | 954 ms |
| Sep 19, 2026 | 954 ms |
| Sep 26, 2026 | 983 ms |
| Oct 3, 2026 | 965 ms |
| Oct 10, 2026 | 961 ms |
| Oct 17, 2026 | 952 ms |
| Oct 24, 2026 | 954 ms |
| Oct 31, 2026 | 949 ms |
| Nov 7, 2026 | 917 ms |
| Nov 14, 2026 | 858 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 61 ms |
| Jun 6, 2026 | 60 ms |
| Jun 13, 2026 | 61 ms |
| Jun 20, 2026 | 63 ms |
| Jun 27, 2026 | 63 ms |
| Jul 4, 2026 | 64 ms |
| Jul 11, 2026 | 66 ms |
| Jul 18, 2026 | 62 ms |
| Jul 25, 2026 | 60 ms |
| Aug 1, 2026 | 56 ms |
| Aug 8, 2026 | 56 ms |
| Aug 15, 2026 | 57 ms |
| Aug 22, 2026 | 60 ms |
| Aug 29, 2026 | 61 ms |
| Sep 5, 2026 | 62 ms |
| Sep 12, 2026 | 62 ms |
| Sep 19, 2026 | 62 ms |
| Sep 26, 2026 | 63 ms |
| Oct 3, 2026 | 61 ms |
| Oct 10, 2026 | 61 ms |
| Oct 17, 2026 | 62 ms |
| Oct 24, 2026 | 62 ms |
| Oct 31, 2026 | 63 ms |
| Nov 7, 2026 | 64 ms |
| Nov 14, 2026 | 63 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
Improve image delivery
3.3 s · 1.2 MB7 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Embedly and cloudfront.net and others), adding 9.2 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
YouTube adds 982 ms
982 msYouTube costs a phone 982 ms of main-thread work and 3.0 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.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
website-files.com adds 16 ms
16 mswebsite-files.com costs a phone 16 ms of main-thread work and 5.6 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 143 KiBAbout 143 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 123 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
2 KiB3 files are served with short cache lifetimes, so returning visitors download them again (2 KiB).
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 31.7 s
31.7 sThe page becomes fully interactive after 31.7 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 266 ms
266 msScripts block taps and scrolling for 266 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 61 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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 INP: 78 ms
78 msReal visitors wait 78 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 516 ms
516 msReal visitors wait 516 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.2 MB in 87 requests
9.2 MBYour homepage downloads 9.2 MB in 87 requests on a phone: images 5.4 MB (23), scripts 2.7 MB (25) and HTML 504 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (42 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.
1 image below the first screen load straight away
1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.61 g of CO₂e: 313.3 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
29 text elements with low contrast
29 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.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.adirondackhealth.org/sitemap.xml, so Google discovers your pages only by following links.
68 internal links, 7 external
The homepage links to 68 pages on adirondackhealth.org and 7 external pages.
4 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Adirondack Health offers a full range of medical, surgical, long-term and primary care services to residents and visito…”.
One H1 headline
Your main headline reads: “Paths to better health”.
Title: 53 characters
Your title is a healthy 53 characters: “Adirondack Health - Adirondack Medical Health Centers”.
robots.txt in place
robots.txt is in place.
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.adirondackhealth.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.
1 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.
Other pages
2 pages without a meta description
https://www.adirondackhealth.org/patients-and-visitors/support-and-education and https://www.adirondackhealth.org/pages/advance-directives have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.adirondackhealth.org/medical-records, https://www.adirondackhealth.org/about/about-us, https://www.adirondackhealth.org/services-conditions, https://www.adirondackhealth.org/docs/find-a-doctor, https://www.adirondackhealth.org/adirondack-medical-center-saranac-lake and https://www.adirondackhealth.org/location/lake-placid-health-and-medical-fitness-center and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 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.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
18 of 18 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.
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 147 words
The homepage has only about 147 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request Appointment”.
3 calls to action
The homepage has 3 calls to action, for example “Request Appointment” and “Contact Information”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
12 other companies contacted
Loading the homepage contacts 12 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 adirondackhealth.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
- Webflow
- Hosting
- Webflow
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Company
- Employees
- 870
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on adirondackhealth.org, including 13 speed issues, 4 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.