Website review, no card needed
animassurgical.com website review
Visit site (opens in a new tab)Reviewed 22 October 202637 issues · 86 checks
This review found 37 issues worth fixing on animassurgical.com, 14 of them high impact, across 86 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.8 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 82 ms |
| May 9, 2026 | 88 ms |
| May 16, 2026 | 80 ms |
| May 23, 2026 | 76 ms |
| May 30, 2026 | 73 ms |
| Jun 6, 2026 | 69 ms |
| Jun 13, 2026 | 69 ms |
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 69 ms |
| Jul 4, 2026 | 69 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 68 ms |
| Aug 29, 2026 | 69 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 68 ms |
| Sep 19, 2026 | 69 ms |
| Sep 26, 2026 | 70 ms |
| Oct 3, 2026 | 70 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 73 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
12.0 s · 3.2 MB12 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.0 s faster on a phone.
Render-blocking requests
3.1 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Use efficient cache lifetimes
900 ms · 155 KiB3 files are served with short cache lifetimes, so returning visitors download them again (155 KiB).
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 49). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
850 ms · 131 KiBAbout 131 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 850 ms faster on a phone.
Reduce unused CSS
750 ms · 91 KiBAbout 91 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.
Legacy JavaScript
150 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 8 KiB8 KiB could be saved by minifying CSS.
6 third-party services on the page
6 third-party services load with your homepage (userway.org, ihealthspot.com and FontAwesome CDN and others), adding 377 KiB and 78 ms of main-thread time.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 195 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Largest Contentful Paint: 44.6 s
44.6 sYour largest element takes 44.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Animas Surgical Hospital”.
Time to Interactive: 44.6 s
44.6 sThe page becomes fully interactive after 44.6 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 906 ms
906 msReal visitors wait 906 ms for your server to start answering (75th percentile). Good is under 800 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 72 ms
72 msReal visitors wait 72 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.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 82 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.3 MB in 74 requests
9.3 MBYour homepage downloads 9.3 MB in 74 requests on a phone: images 8.8 MB (22), scripts 302 KiB (22) and stylesheets 161 KiB (23). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.4 MB1 image is downloaded at several times the size a phone draws it, for example Main-Page-Durango.png at 2,000 px wide, shown at 390 px. Resized copies would save about 1.4 MB.
14 images in older formats
14 images (8.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.
10 images below the first screen load straight away
10 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.65 g of CO₂e: 317.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.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 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 (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Animas Surgical Hospital | Physician-Owned Hospital in Durango, CO”.
Meta description is long (279 characters)
Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.
81 internal links, 1 external
The homepage links to 81 pages on animassurgical.com and 1 external page.
6 checks passed
One H1 headline
Your main headline reads: “Advanced Care for Durango & the Four Corners”.
Canonical URL set
The canonical URL is https://www.animassurgical.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage 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.animassurgical.com/sitemap_index.xml.
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.animassurgical.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 (382 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.animassurgical.com/about and https://www.animassurgical.com/new-nurse-residency all use the title “About Us | Animas Surgical Hospital | Durango, CO”. 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.animassurgical.com/patients-visitors/patient-portal has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.animassurgical.com/about and https://www.animassurgical.com/new-nurse-residency use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.animassurgical.com/patients-visitors/patient-portal has 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 41 found) and read each the way a search engine does.
4 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.0.6/css/all.css' from origin 'https://www.animassu…”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
13 of 13 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.
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: a star rating. 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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 256 words of copy
The homepage carries about 256 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Pricing” and “Contact Us”.
Analytics in place
Analytics detected: Matomo.
Direct contact links
Visitors can reach you directly: 3 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
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 animassurgical.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on animassurgical.com, including 15 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.