Website review, no card needed

woundcentrics.com logo

woundcentrics.com website review

Visit site (opens in a new tab)Reviewed 21 October 202641 issues · 83 checks

This review found 41 issues worth fixing on woundcentrics.com, 17 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
2.5 s1.7 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.1 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
88 ms59 msMay 2Sep 1970 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202666 ms
May 9, 202663 ms
May 16, 202670 ms
May 23, 202678 ms
May 30, 202685 ms
Jun 6, 202680 ms
Jun 13, 202672 ms
Jun 20, 202671 ms
Jun 27, 202667 ms
Jul 4, 202668 ms
Jul 11, 202670 ms
Jul 18, 202666 ms
Jul 25, 202673 ms
Aug 1, 202680 ms
Aug 8, 202679 ms
Aug 15, 202680 ms
Aug 22, 202679 ms
Aug 29, 202673 ms
Sep 5, 202662 ms
Sep 12, 202662 ms
Sep 19, 202670 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 woundcentrics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. woundcentrics.com at 0.8 s0.8 s
  2. woundcentrics.com at 1.5 s1.5 s
  3. woundcentrics.com at 2.3 s2.3 s
  4. woundcentrics.com at 3.0 s3.0 s
  5. woundcentrics.com at 3.8 s3.8 s
  6. woundcentrics.com at 4.5 s4.5 s
  7. woundcentrics.com at 5.3 s5.3 s
  8. woundcentrics.com at 6.0 s6.0 s

Speed

15 to fix36
  • Reduce unused JavaScript

    8.3 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.3 s faster on a phone.

  • Improve image delivery

    4.3 s · 869 KiB

    4 images could be 869 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.

  • Reduce unused CSS

    1.4 s · 213 KiB

    About 213 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.4 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Squarespace, Google CDN and Google Maps and others), adding 4.5 MB and 1.9 s of main-thread time.

  • Use efficient cache lifetimes

    800 ms · 220 KiB

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

  • Squarespace adds 784 ms

    784 ms

    Squarespace costs a phone 784 ms of main-thread work and 1.1 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.

  • Google CDN adds 649 ms

    649 ms

    Google CDN costs a phone 649 ms of main-thread work and 1.1 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.

  • Legacy JavaScript

    500 ms · 148 KiB

    Polyfills for old browsers add 148 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 331 ms. During a long task the page ignores taps.

  • Google Maps adds 195 ms

    195 ms

    Google Maps costs a phone 195 ms of main-thread work and 413 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.

  • sqspcdn.com adds 112 ms

    112 ms

    sqspcdn.com costs a phone 112 ms of main-thread work and 472 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.

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.3 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.

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

1 checks passed
  • Server response: 76 ms

    76 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 28.0 s

    28.0 s

    Your largest element takes 28.0 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: 28.9 s

    28.9 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 860 ms

    860 ms

    Scripts block taps and scrolling for 860 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

5 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.8 s

    1.8 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 5.1 MB in 149 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 149 requests on a phone: scripts 2.7 MB (88), images 1.3 MB (21) and other files 485 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

    3 images further down the page (293 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8891
  • Links must have discernible text (6 elements)

    Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • 6 H1 headlines

    There are 6 <h1> headlines (“Smarter Wound Care starts with Better Strategy”, “| Dr. Marcus Gitterle will present at the Angiody…” and “| Chelsea Thompson will present Tissue Salvage Be…”). One clear main headline is easier for people and search engines.

  • Meta description is long (178 characters)

    Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/69de86ff4863124dc3a…”.

  • 32 internal links, 22 external

    The homepage links to 32 pages on woundcentrics.com and 22 external pages.

5 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “WoundCentrics | Enhance Wound Care Now — Get Started”.

  • Canonical URL set

    The canonical URL is https://www.woundcentrics.com/.

  • 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.woundcentrics.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.woundcentrics.com/llms.txt (2 KiB, 5 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.woundcentrics.com/executive-leadership-1 and https://www.woundcentrics.com/executive-leadership all use the title “Executive Leadership in Wound & Vascular Care | WoundCentrics — Wound…”. 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.woundcentrics.com/executive-leadership-1 and https://www.woundcentrics.com/executive-leadership use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.woundcentrics.com/wound-care-programs, https://www.woundcentrics.com/contact, https://www.woundcentrics.com/consulting, https://www.woundcentrics.com/clinical-research, https://www.woundcentrics.com/woundcentric-clinic-locations and https://www.woundcentrics.com/mission-values have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 635 words of copy

    The homepage carries about 635 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Start here to explore a better approach” and “Sign Up”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks and 35 customer or partner logos.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 woundcentrics.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
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on woundcentrics.com, including 21 speed issues, 3 SEO issues and 5 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