Website review, no card needed

bowenhealth.org logo

bowenhealth.org website review

Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 76 checks

This review found 34 issues worth fixing on bowenhealth.org, 12 of them high impact, across 76 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
1.2 s1.0 sMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.0 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
94 ms78 msMay 9Oct 2485 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202682 ms
May 16, 202680 ms
May 23, 202680 ms
May 30, 202681 ms
Jun 6, 202681 ms
Jun 13, 202684 ms
Jun 20, 202686 ms
Jun 27, 202691 ms
Jul 4, 202692 ms
Jul 11, 202692 ms
Jul 18, 202691 ms
Jul 25, 202687 ms
Aug 1, 202688 ms
Aug 8, 202689 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202684 ms
Sep 5, 202684 ms
Sep 12, 202683 ms
Sep 19, 202682 ms
Sep 26, 202685 ms
Oct 3, 202685 ms
Oct 10, 202685 ms
Oct 17, 202686 ms
Oct 24, 202685 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 bowenhealth.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix28
  • Reduce unused JavaScript

    1.5 s · 591 KiB

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

  • Render-blocking requests

    1.8 s

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

  • Squarespace adds 1.1 s

    1.1 s

    Squarespace costs a phone 1.1 s of main-thread work and 962 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 4.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, weglot.com and Other Google APIs/SDKs and others), adding 1.5 MB and 1.7 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 119 KiB

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

  • Legacy JavaScript

    450 ms · 93 KiB

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

  • 12 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 139 KiB

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

  • 1,860 HTML elements

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

  • Improve image delivery

    150 ms · 247 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 91 but mobile only 28. 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 38 ms

    38 ms

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

Core Web Vitals

9 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: 11.8 s

    11.8 s

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

  • Time to Interactive: 15.0 s

    15.0 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 758 ms

    758 ms

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

  • Real-user CLS: 0.21

    0.21

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

  • Cumulative Layout Shift: 0.233

    0.233

    The layout shifts by 0.233 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 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

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 89 ms

    89 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 600 ms

    600 ms

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

Images and page weight

1 to fix67
  • Page weight: 2.2 MB in 103 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 103 requests on a phone: scripts 1.2 MB (47), images 470 KiB (25) and stylesheets 187 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.62 g

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

Accessibility

2 to fixGoogle 9590
  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 7 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is short (12 characters)

    Your title is only 12 characters: “Bowen Health”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (388 characters)

    Your meta description is 388 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/62a0dea88c4b5e3909a…”.

  • 15 links with vague text

    15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 187 internal links, 11 external

    The homepage links to 187 pages on bowenhealth.org and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Making healthcare accessible for you.”.

  • Canonical URL set

    The canonical URL is https://www.bowenhealth.org/.

  • 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.bowenhealth.org/sitemap.xml.

AI search readiness

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

3 to fix83
  • 2 linked pages hidden from search

    https://www.bowenhealth.org/who-we-are and https://www.bowenhealth.org/leadership are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.bowenhealth.org/who-we-are and https://www.bowenhealth.org/leadership have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.bowenhealth.org/who-we-are 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 56 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

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

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

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

Google 96100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 664 words of visible text.

2 checks passed
  • 27 calls to action

    The homepage has 27 calls to action, for example “REQUEST RECORDS”, “SCHEDULE APPOINTMENT” and “Learn More”.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

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

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 bowenhealth.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
Squarespace
Hosting
Squarespace

Company

Employees
1,128

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on bowenhealth.org, including 20 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

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