Website review, no card needed

broadwaycares.org logo

broadwaycares.org website review

Visit site (opens in a new tab)Reviewed 25 October 202646 issues · 97 checks

This review found 46 issues worth fixing on broadwaycares.org, 20 of them high impact, across 97 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
3.0 s1.1 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.7 s
May 9, 20262.8 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
126 ms103 msMay 2Oct 17107 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026123 ms
May 9, 2026115 ms
May 16, 2026113 ms
May 23, 2026112 ms
May 30, 2026111 ms
Jun 6, 2026111 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026113 ms
Jul 4, 2026114 ms
Jul 11, 2026109 ms
Jul 18, 2026109 ms
Jul 25, 2026108 ms
Aug 1, 2026111 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026119 ms
Aug 29, 2026117 ms
Sep 5, 2026120 ms
Sep 12, 2026121 ms
Sep 19, 2026120 ms
Sep 26, 2026111 ms
Oct 3, 2026108 ms
Oct 10, 2026106 ms
Oct 17, 2026107 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 broadwaycares.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. broadwaycares.org at 1.0 s1.0 s
  2. broadwaycares.org at 2.0 s2.0 s
  3. broadwaycares.org at 3.0 s3.0 s
  4. broadwaycares.org at 4.0 s4.0 s
  5. broadwaycares.org at 5.0 s5.0 s
  6. broadwaycares.org at 6.0 s6.0 s
  7. broadwaycares.org at 7.0 s7.0 s
  8. broadwaycares.org at 8.0 s8.0 s

Speed

14 to fix18
  • Use efficient cache lifetimes

    8.3 s · 4.5 MB

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

  • Improve image delivery

    2.6 s · 2.7 MB

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

  • Render-blocking requests

    3.5 s

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

  • classy.org adds 1.5 s

    1.5 s

    classy.org costs a phone 1.5 s of main-thread work and 1.2 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.

  • Reduce unused CSS

    1.1 s · 547 KiB

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

  • Main-thread work: 11.4 s

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

  • Mobile performance score: 18

    18/100

    Your mobile performance score is 18 (desktop: 16). 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 (classy.org, PayPal and Google Tag Manager and others), adding 5.3 MB and 4.4 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 3.0 MB

    About 3.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • PayPal adds 682 ms

    682 ms

    PayPal costs a phone 682 ms of main-thread work and 970 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.

  • Google Tag Manager adds 612 ms

    612 ms

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

  • Google CDN adds 559 ms

    559 ms

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

  • YouTube adds 478 ms

    478 ms

    YouTube costs a phone 478 ms of main-thread work and 1.1 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.

  • 20 long tasks on the main thread

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

  • Minify CSS

    150 ms · 62 KiB

    62 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    58 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 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: 13.1 s

    13.1 s

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

  • Speed Index: 19.1 s

    19.1 s

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

  • Time to Interactive: 71.5 s

    71.5 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Real-user CLS: 0.19

    0.19

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

  • Cumulative Layout Shift: 0.181

    0.181

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

  • 22 images without width and height

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

6 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 99 ms

    99 ms

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 688 ms

    688 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

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

    -51%

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

Images and page weight

3 to fix45
  • Page weight: 14.2 MB in 311 requests

    14.2 MB

    Your homepage downloads 14.2 MB in 311 requests on a phone: scripts 7.0 MB (104), images 4.2 MB (53) and other files 1.2 MB (96). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (2.0 MB) 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 4.0 g of CO₂ per visit

    4.03 g

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

2 checks passed
  • 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

8 to fixGoogle 8588
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • 11 text elements with low contrast

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

  • 2 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 8375
  • No meta description

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

  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Broadway Cares/Equity Fights AIDS – What we do together, makes a difference”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Broadway Cares Equity Fights Aids” and “Broadway Cares/Equity Fights Aids”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 75 internal links, 37 external

    The homepage links to 75 pages on broadwaycares.org and 37 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://broadwaycares.org/.

  • Structured data in place

    Structured data found: Event, Organization and WebSite.

  • 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://broadwaycares.org/wp-sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://broadwaycares.org/about-broadway-cares-equity-fights-aids, https://broadwaycares.org/mission-statement, https://broadwaycares.org/broadway-cares-staff, https://broadwaycares.org/board, https://broadwaycares.org/annualreport/annual-report-2025 and https://broadwaycares.org/behindthescenes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

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

Best practices

3 to fixGoogle 6987
  • 6 third-party cookies

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Unable to download payment manifest "https://google.com/pay". ERR_SOCKET_NOT_CONNECTED (-15)”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    36 of 41 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

  • About 490 words of copy

    The homepage carries about 490 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop For The Cause”, “Contact” and “Shop”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 13 cookies set on arrival

    13

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

  • 45 other companies contacted

    Loading the homepage contacts 45 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 broadwaycares.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on broadwaycares.org, including 23 speed issues, 5 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