Website review, no card needed

lifeshare.org logo

lifeshare.org website review

Visit site (opens in a new tab)Reviewed 27 October 202633 issues · 79 checks

This review found 33 issues worth fixing on lifeshare.org, 18 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
5.6 s2.8 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.2 s
May 16, 20265.2 s
May 23, 20264.8 s
May 30, 20264.7 s
Jun 6, 20264.6 s
Jun 13, 20264.6 s
Jun 20, 20264.8 s
Jun 27, 20264.7 s
Jul 4, 20265.0 s
Jul 11, 20265.0 s
Jul 18, 20264.8 s
Jul 25, 20264.7 s
Aug 1, 20263.8 s
Aug 8, 20263.6 s
Aug 15, 20263.3 s
Aug 22, 20263.2 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
129 ms106 msMay 9Oct 24118 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026118 ms
May 16, 2026116 ms
May 23, 2026116 ms
May 30, 2026112 ms
Jun 6, 2026113 ms
Jun 13, 2026112 ms
Jun 20, 2026111 ms
Jun 27, 2026112 ms
Jul 4, 2026115 ms
Jul 11, 2026117 ms
Jul 18, 2026119 ms
Jul 25, 2026119 ms
Aug 1, 2026111 ms
Aug 8, 2026109 ms
Aug 15, 2026112 ms
Aug 22, 2026112 ms
Aug 29, 2026117 ms
Sep 5, 2026125 ms
Sep 12, 2026124 ms
Sep 19, 2026122 ms
Sep 26, 2026126 ms
Oct 3, 2026120 ms
Oct 10, 2026119 ms
Oct 17, 2026117 ms
Oct 24, 2026118 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 lifeshare.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lifeshare.org at 1.7 s1.7 s
  2. lifeshare.org at 3.5 s3.5 s
  3. lifeshare.org at 5.2 s5.2 s
  4. lifeshare.org at 6.9 s6.9 s
  5. lifeshare.org at 8.7 s8.7 s
  6. lifeshare.org at 10.4 s10.4 s
  7. lifeshare.org at 12.1 s12.1 s
  8. lifeshare.org at 13.9 s13.9 s

Speed

12 to fix26
  • Use efficient cache lifetimes

    3.1 s · 16.5 MB

    68 files are served with short cache lifetimes, so returning visitors download them again (16.5 MB).

  • Reduce unused JavaScript

    10.9 s · 3.6 MB

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

  • Improve image delivery

    3.1 s · 1.1 MB

    8 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

  • Font display

    2.5 s

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

  • YouTube adds 2.0 s

    2.0 s

    YouTube costs a phone 2.0 s of main-thread work and 3.8 MB 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.

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 8.7 s

    A phone's processor spends 8.7 s on main-thread work while loading, 4.9 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 (YouTube, Google Tag Manager and Google CDN and others), adding 6.1 MB and 3.8 s of main-thread time.

  • Google Tag Manager adds 929 ms

    929 ms

    Google Tag Manager costs a phone 929 ms of main-thread work and 1.2 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 433 ms

    433 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 235 KiB

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

  • Legacy JavaScript

    36 KiB

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

  • 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: 25 ms

    25 ms

    Your server sent the HTML in 25 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.

  • First Contentful Paint: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 26.6 s

    26.6 s

    Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mayor Tom Arceneaux”.

  • Speed Index: 27.0 s

    27.0 s

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

  • Time to Interactive: 52.3 s

    52.3 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 2.3 s

    2.3 s

    Real visitors see the first content after 2.3 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

    0%

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

4 checks passed
  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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 39% faster for real visitors

    -39%

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

  • Cumulative Layout Shift: 0.088

    0.088

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

Images and page weight

1 to fix33
  • Page weight: 30.8 MB in 187 requests

    30.8 MB

    Your homepage downloads 30.8 MB in 187 requests on a phone: media 20.6 MB (4), scripts 5.7 MB (52) and images 3.0 MB (25). Under 2 MB keeps phones on slow connections fast.

  • About 8.7 g of CO₂ per visit

    8.74 g

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

Accessibility

5 to fixGoogle 7167
  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • 5 text elements with low contrast

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 3 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 6 H1 headlines

    There are 6 <h1> headlines (“Mayor Tom Arceneaux”, “” and “”). One clear main headline is easier for people and search engines.

  • 5 links with vague text

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

  • 56 internal links, 18 external

    The homepage links to 56 pages on lifeshare.org and 18 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Lifeshare Blood Center is a trusted source of blood donations & services in LA, TX, & AR. Help us save lives by donatin…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “LifeShare Blood Center | Donate Blood, Share Your Story”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.lifeshare.org/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.lifeshare.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.

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.

  • Organization data: 4 of 6 facts

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.lifeshare.org/lssbb has no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages slow to respond

    https://www.lifeshare.org/donorpass, https://www.lifeshare.org/host-a-blood-drive, https://www.lifeshare.org/faqs, https://www.lifeshare.org/therapeutic-phlebotomy-service, https://www.lifeshare.org/about and https://www.lifeshare.org/board-of-trustees-executive-management and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 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 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

1 to fixGoogle 7396
  • 7 third-party cookies

    7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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

2 to fix67
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,039 words of copy

    The homepage carries about 1,039 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 lifeshare.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Employees
235

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on lifeshare.org, including 21 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