Website review, no card needed

caringbridge.org logo

caringbridge.org website review

Visit site (opens in a new tab)Reviewed 11 October 202640 issues · 73 checks

This review found 40 issues worth fixing on caringbridge.org, 24 of them high impact, across 73 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
7.2 s3.8 sApr 18Oct 34.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20266.5 s
Apr 25, 20266.5 s
May 2, 20266.4 s
May 9, 20266.4 s
May 16, 20266.4 s
May 23, 20266.6 s
May 30, 20266.7 s
Jun 6, 20266.8 s
Jun 13, 20266.8 s
Jun 20, 20266.5 s
Jun 27, 20265.9 s
Jul 4, 20264.9 s
Jul 11, 20264.4 s
Jul 18, 20264.4 s
Jul 25, 20264.4 s
Aug 1, 20264.4 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.4 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.2 s
Oct 3, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
171 ms147 msApr 18Oct 3150 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026168 ms
Apr 25, 2026163 ms
May 2, 2026161 ms
May 9, 2026156 ms
May 16, 2026155 ms
May 23, 2026158 ms
May 30, 2026161 ms
Jun 6, 2026163 ms
Jun 13, 2026163 ms
Jun 20, 2026162 ms
Jun 27, 2026161 ms
Jul 4, 2026161 ms
Jul 11, 2026160 ms
Jul 18, 2026159 ms
Jul 25, 2026157 ms
Aug 1, 2026155 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026153 ms
Aug 29, 2026152 ms
Sep 5, 2026153 ms
Sep 12, 2026153 ms
Sep 19, 2026152 ms
Sep 26, 2026151 ms
Oct 3, 2026150 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 caringbridge.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix36
  • Reduce unused JavaScript

    2.4 s · 679 KiB

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

  • Use efficient cache lifetimes

    1.9 s · 462 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Reduce unused CSS

    1.3 s · 293 KiB

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

  • Mobile performance score: 36

    36/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookie-Script.com and others), adding 1.3 MB and 1.2 s of main-thread time.

  • Google Tag Manager adds 515 ms

    515 ms

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

  • Main-thread work: 3.2 s

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

  • Facebook adds 272 ms

    272 ms

    Facebook costs a phone 272 ms of main-thread work and 307 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.

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. 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).

  • Phones get a much slower page than desktops

    Desktop scores 62 but mobile only 36. 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 JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix33
  • 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 CLS: 0.44

    0.44

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Surrounded with support at every step of the health journey”.

  • Time to Interactive: 18.2 s

    18.2 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • Total Blocking Time: 992 ms

    992 ms

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Tap response (INP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user INP: 169 ms

    169 ms

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

  • Real-user TTFB: 742 ms

    742 ms

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

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

    -36%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 6.5 s to 4.2 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).

Images and page weight

2 to fix81
  • Page weight: 2.5 MB in 100 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 100 requests on a phone: scripts 1.7 MB (51), other files 360 KiB (28) and fonts 230 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    communicate_box_1_360_x3hpxg.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.7 g of CO₂ per visit

    0.71 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.2 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

4 to fixGoogle 8493
  • 2 buttons without a name

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

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 3 links without text

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

1 checks passed
  • 43 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: 43 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 7755
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 2 links with vague text

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

3 checks passed
  • 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://caringbridge.org/sitemap-index.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 745 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26035446&Ver=2&mid=2353faa5-38af-48dd-9f2f-fa03463d302c&bo=1&sid=7c61e4c0c5cd11f18665772db6dd80bd&vid=7c620000c5cd11f19dab53471bc52ae4&vids=1&msclkid=N&page_path=%2F&s.

  • 5 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

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

4 to fix30
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

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

    The homepage carries about 745 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Heap and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 19 cookies set on arrival

    19

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

  • 24 other companies contacted

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

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 caringbridge.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on caringbridge.org, including 18 speed issues, 7 SEO issues and 4 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