Website review, no card needed

casamba.net logo

casamba.net website review

Visit site (opens in a new tab)Reviewed 25 October 202630 issues · 84 checks

This review found 30 issues worth fixing on casamba.net, 7 of them high impact, across 84 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.4 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
May 9, 20263.0 s
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.1 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.0 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.0 s
Sep 5, 20262.8 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
132 ms105 msMay 2Oct 17119 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026111 ms
May 9, 2026108 ms
May 16, 2026108 ms
May 23, 2026112 ms
May 30, 2026120 ms
Jun 6, 2026124 ms
Jun 13, 2026128 ms
Jun 20, 2026128 ms
Jun 27, 2026128 ms
Jul 4, 2026127 ms
Jul 11, 2026126 ms
Jul 18, 2026128 ms
Jul 25, 2026128 ms
Aug 1, 2026125 ms
Aug 8, 2026127 ms
Aug 15, 2026125 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026128 ms
Sep 12, 2026127 ms
Sep 19, 2026125 ms
Sep 26, 2026120 ms
Oct 3, 2026120 ms
Oct 10, 2026120 ms
Oct 17, 2026119 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

Full-page screenshot of casamba.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. casamba.net at 0.4 s0.4 s
  2. casamba.net at 0.8 s0.8 s
  3. casamba.net at 1.1 s1.1 s
  4. casamba.net at 1.5 s1.5 s
  5. casamba.net at 1.9 s1.9 s
  6. casamba.net at 2.3 s2.3 s
  7. casamba.net at 2.6 s2.6 s
  8. casamba.net at 3.0 s3.0 s

Speed

8 to fix62
  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 88 KiB

    About 88 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 123 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (123 KiB).

  • Improve image delivery

    300 ms · 42 KiB

    1 image could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and cloudflare.com and others), adding 1.0 MB and 212 ms of main-thread time.

  • 2,056 HTML elements

    The page has 2,056 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Google Tag Manager adds 116 ms

    116 ms

    Google Tag Manager costs a phone 116 ms of main-thread work and 373 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.

  • site.com adds 12 ms

    12 ms

    site.com costs a phone 12 ms of main-thread work and 606 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.

  • Render-blocking requests

    150 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    45 KiB

    About 45 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 424 ms of it running JavaScript. That is comfortably low.

  • Server response: 57 ms

    57 ms

    Your server sent the HTML in 57 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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: 13.4 s

    13.4 s

    Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero image with software mockups”.

  • Time to Interactive: 13.5 s

    13.5 s

    The page becomes fully interactive after 13.5 s. Good is under 3.8 s.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.0 s

    6.0 s

    Visually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 111 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user INP: 114 ms

    114 ms

    Real visitors wait 114 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 40 ms

    40 ms

    Scripts block the page for only 40 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 84 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 84 requests on a phone: scripts 1.1 MB (51), other files 636 KiB (11) and images 488 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9596
  • 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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 32 links without text

    32 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, ImageObject and Organization) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • 97 internal links, 31 external

    The homepage links to 97 pages on casamba.net and 31 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Extend care beyond the clinic with Limber, Net Health remote therapeutic monitoring software that engages patients and …”.

  • One H1 headline

    Your main headline reads: “Grow Your Rehab Therapy Practice with Seamless Hybrid Care Tools​”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Limber: Remote Therapeutic Monitoring | Net Health”.

  • Canonical URL set

    The canonical URL is https://www.nethealth.com/limber/.

  • 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.nethealth.com/sitemap_index.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,165 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.nethealth.com/llms.txt (4 KiB, 27 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.nethealth.com/wound-care-solutions and https://www.nethealth.com/wound-care-software-solutions all use the title “Wound Care Software & EHR Solutions | Net Health”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.nethealth.com/wound-care-solutions and https://www.nethealth.com/wound-care-software-solutions use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.nethealth.com/wound-care-solutions, whose canonical is https://www.nethealth.com/wound-care-software-solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 2 small tap targets

    2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (8 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 501 words of copy

    The homepage carries about 501 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a Demo”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Request a Demo”, “Learn More About Limber” and “Download the Free Checklist”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 casamba.net, 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 Analytics | Google Tag Manager | Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on casamba.net, including 16 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25