Website review, no card needed

neighbor.org logo

neighbor.org website review

Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 91 checks

This review found 47 issues worth fixing on neighbor.org, 18 of them high impact, across 91 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
5.3 s4.5 sMay 30Nov 144.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.0 s
Jun 6, 20264.7 s
Jun 13, 20264.6 s
Jun 20, 20264.6 s
Jun 27, 20264.6 s
Jul 4, 20264.7 s
Jul 11, 20264.8 s
Jul 18, 20264.8 s
Jul 25, 20264.9 s
Aug 1, 20264.9 s
Aug 8, 20265.0 s
Aug 15, 20265.1 s
Aug 22, 20265.2 s
Aug 29, 20265.1 s
Sep 5, 20265.0 s
Sep 12, 20264.8 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.6 s
Oct 10, 20264.6 s
Oct 17, 20264.7 s
Oct 24, 20264.8 s
Oct 31, 20264.7 s
Nov 7, 20264.8 s
Nov 14, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
322 ms219 msMay 30Nov 14268 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026286 ms
Jun 6, 2026286 ms
Jun 13, 2026278 ms
Jun 20, 2026266 ms
Jun 27, 2026256 ms
Jul 4, 2026257 ms
Jul 11, 2026244 ms
Jul 18, 2026236 ms
Jul 25, 2026236 ms
Aug 1, 2026232 ms
Aug 8, 2026231 ms
Aug 15, 2026249 ms
Aug 22, 2026243 ms
Aug 29, 2026240 ms
Sep 5, 2026263 ms
Sep 12, 2026261 ms
Sep 19, 2026273 ms
Sep 26, 2026285 ms
Oct 3, 2026290 ms
Oct 10, 2026306 ms
Oct 17, 2026307 ms
Oct 24, 2026310 ms
Oct 31, 2026288 ms
Nov 7, 2026283 ms
Nov 14, 2026268 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 neighbor.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. neighbor.org at 1.1 s1.1 s
  2. neighbor.org at 2.3 s2.3 s
  3. neighbor.org at 3.4 s3.4 s
  4. neighbor.org at 4.6 s4.6 s
  5. neighbor.org at 5.7 s5.7 s
  6. neighbor.org at 6.9 s6.9 s
  7. neighbor.org at 8.0 s8.0 s
  8. neighbor.org at 9.2 s9.2 s

Speed

13 to fix35
  • Reduce unused JavaScript

    1.6 s · 2.3 MB

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

  • blackbaudcdn.net adds 1.9 s

    1.9 s

    blackbaudcdn.net costs a phone 1.9 s of main-thread work and 4.1 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

    2.3 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 7.4 s

    A phone's processor spends 7.4 s on main-thread work while loading, 4.6 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 (blackbaudcdn.net, Google Tag Manager and Facebook and others), adding 6.8 MB and 3.8 s of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 2.1 MB

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

  • Improve image delivery

    500 ms · 1.6 MB

    33 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Reduce unused CSS

    590 ms · 192 KiB

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

  • Google Tag Manager adds 628 ms

    628 ms

    Google Tag Manager costs a phone 628 ms of main-thread work and 1,021 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.

  • Facebook adds 467 ms

    467 ms

    Facebook costs a phone 467 ms of main-thread work and 332 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 475 ms. During a long task the page ignores taps.

  • Google CDN adds 278 ms

    278 ms

    Google CDN costs a phone 278 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.

  • Font display

    250 ms

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

  • Legacy JavaScript

    38 KiB

    Polyfills for old browsers add 38 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.

1 checks passed
  • Server response: 60 ms

    60 ms

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

Core Web Vitals

11 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 LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 15.5 s

    15.5 s

    Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “San Diego Thrift Store & AuctionsSan…”.

  • Speed Index: 22.6 s

    22.6 s

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

  • Time to Interactive: 57.9 s

    57.9 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user INP: 307 ms

    307 ms

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

  • 55 images without width and height

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

2 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

3 to fix53
  • Page weight: 12.8 MB in 313 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 313 requests on a phone: scripts 6.0 MB (144), images 4.5 MB (50) and other files 1.4 MB (75). Under 2 MB keeps phones on slow connections fast.

  • 27 images below the first screen load straight away

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

  • 13 images in older formats

    13 images (489 KiB) are 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 3.6 g of CO₂ per visit

    3.63 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7588
  • 6 text elements with low contrast

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

  • 3 tap targets too small

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (23 elements)

    All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • Zoom is disabled

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

  • 7 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

4 to fixGoogle 9281
  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “Helping San Diego Homeless Shelters Near Me: Volunteer, Donate | Father Joe's Villages”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“San Diego Thrift Store & Auctions”, “Join Champions of Hope and become a monthly suppo…” and “Shop With Purpose”). One clear main headline is easier for people and search engines.

  • Meta description is long (161 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 153 internal links, 20 external

    The homepage links to 153 pages on neighbor.org and 20 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://my.neighbor.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://my.neighbor.org/sitemap_index.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://my.neighbor.org/llms.txt (14 KiB, 132 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://my.neighbor.org/detox-program 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 39 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

  • Only about 229 words

    The homepage has only about 229 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

4 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Careers – Join Our Team”, “Contact Us” and “SCHEDULE PICK-UP”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 4 mores (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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 1 of them by other companies (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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 neighbor.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
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on neighbor.org, including 24 speed issues, 4 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