Website review, no card needed

soultenders.com logo

soultenders.com website review

Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 86 checks

This review found 38 issues worth fixing on soultenders.com, 17 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
4.2 s3.4 sApr 25Oct 103.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.0 s
May 2, 20264.1 s
May 9, 20264.0 s
May 16, 20263.8 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20264.1 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.6 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.8 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.7 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
99 ms67 msApr 25Oct 1087 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202671 ms
May 2, 202671 ms
May 9, 202671 ms
May 16, 202672 ms
May 23, 202676 ms
May 30, 202676 ms
Jun 6, 202676 ms
Jun 13, 202677 ms
Jun 20, 202676 ms
Jun 27, 202676 ms
Jul 4, 202676 ms
Jul 11, 202671 ms
Jul 18, 202678 ms
Jul 25, 202673 ms
Aug 1, 202695 ms
Aug 8, 202693 ms
Aug 15, 202687 ms
Aug 22, 202686 ms
Aug 29, 202673 ms
Sep 5, 202675 ms
Sep 12, 202673 ms
Sep 19, 202676 ms
Sep 26, 202680 ms
Oct 3, 202687 ms
Oct 10, 202687 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 soultenders.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. soultenders.com at 0.7 s0.7 s
  2. soultenders.com at 1.4 s1.4 s
  3. soultenders.com at 2.0 s2.0 s
  4. soultenders.com at 2.7 s2.7 s
  5. soultenders.com at 3.4 s3.4 s
  6. soultenders.com at 4.0 s4.0 s
  7. soultenders.com at 4.7 s4.7 s
  8. soultenders.com at 5.4 s5.4 s

Speed

9 to fix54
  • Render-blocking requests

    3.5 s

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

  • Use efficient cache lifetimes

    2.2 s · 516 KiB

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

  • Reduce unused JavaScript

    1.2 s · 245 KiB

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

  • Mobile performance score: 54

    54/100

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

  • Reduce unused CSS

    850 ms · 122 KiB

    About 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 850 ms faster on a phone.

  • Improve image delivery

    450 ms · 72 KiB

    3 images could be 72 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 3 long tasks on the main thread

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

  • Google Maps adds 203 ms

    203 ms

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

  • 1,949 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Maps, freshworks.com and cdn-cookieyes.com and others), adding 905 KiB and 410 ms of main-thread time.

  • Minify CSS

    250 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Minify JavaScript

    100 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 86 but mobile only 54. 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.5 s

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

  • Server response: 107 ms

    107 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.4 s

    5.4 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Real-user TTFB: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • Total Blocking Time: 229 ms

    229 ms

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

3 checks passed
  • Real-user INP: 88 ms

    88 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.023

    0.023

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

Images and page weight

100
  • 1 image in older formats

    1 image (128 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.5 g of CO₂ per visit

    0.49 g

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

3 checks passed
  • Page weight: 1.7 MB in 141 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 141 requests on a phone: scripts 826 KiB (62), images 371 KiB (19) and fonts 299 KiB (7). That is a lean page.

  • 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

9 to fixGoogle 7388
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

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

  • 8 images without alt text

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

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

  • 15 form fields without a label

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

  • 5 links without text

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 8588
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Management Services for Licensed Mental Health Therapists | Soultenders”.

  • One H1 headline

    Your <h1> is empty.

  • 52 internal links, 5 external

    The homepage links to 52 pages on soultenders.com and 5 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Soultenders has 20+ years of experience providing best in class management services for mental health providers that of…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, 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.soultenders.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://www.soultenders.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 (323 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://www.soultenders.com/therapists, https://www.soultenders.com/frequently-asked-questions, https://www.soultenders.com/locations, https://www.soultenders.com/contact-us, https://www.soultenders.com/patient-blog and https://www.soultenders.com/for-therapist and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.soultenders.com/contact-us and https://www.soultenders.com/business-inquiries have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.soultenders.com/therapists/garni-sohrabian took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 29 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

2 to fixGoogle 9687
  • 27 small tap targets

    27 of 41 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 “ApbctGatheringData is not a constructor”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 347 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Patient Contact Us Form” and “Join Our Provider Network”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Patient Contact Us Form”, “Join Our Provider Network” and “Contact Us”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 8 cookies set on arrival

    8

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

  • 8 other companies contacted

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

2 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

  • 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 soultenders.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
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on soultenders.com, including 20 speed issues, 2 SEO issues and 2 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