Website review, no card needed

whitman-walker.org logo

whitman-walker.org website review

Visit site (opens in a new tab)Reviewed 18 November 202643 issues · 91 checks

This review found 43 issues worth fixing on whitman-walker.org, 18 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
4.8 s3.5 sMay 30Nov 144.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.6 s
Jun 20, 20264.6 s
Jun 27, 20264.6 s
Jul 4, 20264.6 s
Jul 11, 20264.5 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.4 s
Aug 8, 20264.3 s
Aug 15, 20264.2 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20264.2 s
Sep 26, 20264.2 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.3 s
Oct 24, 20264.4 s
Oct 31, 20264.5 s
Nov 7, 20264.6 s
Nov 14, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
159 ms114 msMay 30Nov 14133 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jun 6, 2026127 ms
Jun 13, 2026129 ms
Jun 20, 2026131 ms
Jun 27, 2026128 ms
Jul 4, 2026128 ms
Jul 11, 2026123 ms
Jul 18, 2026124 ms
Jul 25, 2026125 ms
Aug 1, 2026122 ms
Aug 8, 2026121 ms
Aug 15, 2026123 ms
Aug 22, 2026119 ms
Aug 29, 2026126 ms
Sep 5, 2026130 ms
Sep 12, 2026127 ms
Sep 19, 2026135 ms
Sep 26, 2026137 ms
Oct 3, 2026147 ms
Oct 10, 2026153 ms
Oct 17, 2026154 ms
Oct 24, 2026148 ms
Oct 31, 2026137 ms
Nov 7, 2026133 ms
Nov 14, 2026133 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 whitman-walker.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. whitman-walker.org at 1.2 s1.2 s
  2. whitman-walker.org at 2.5 s2.5 s
  3. whitman-walker.org at 3.7 s3.7 s
  4. whitman-walker.org at 5.0 s5.0 s
  5. whitman-walker.org at 6.2 s6.2 s
  6. whitman-walker.org at 7.5 s7.5 s
  7. whitman-walker.org at 8.7 s8.7 s
  8. whitman-walker.org at 10.0 s10.0 s

Speed

13 to fix40
  • Improve image delivery

    8.2 s · 1.8 MB

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

  • Render-blocking requests

    3.2 s

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

  • Document request latency

    1.0 s

    The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Mobile performance score: 40

    40/100

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

  • Reduce initial server response time

    976 ms

    Reduce initial server response time. Google estimates savings of 976 ms on a phone.

  • Reduce unused JavaScript

    450 ms · 500 KiB

    About 500 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, fundraiseup.com and fouanalytics.com and others), adding 1.4 MB and 803 ms of main-thread time.

  • Google Tag Manager adds 435 ms

    435 ms

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

  • Reduce unused CSS

    300 ms · 190 KiB

    About 190 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.

  • Font display

    300 ms

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

  • Main-thread work: 2.8 s

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

  • 1,531 HTML elements

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

  • Server response: 1.1 s

    1.1 s

    Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Use efficient cache lifetimes

    241 KiB

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

  • Legacy JavaScript

    200 ms · 19 KiB

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

  • 5 long tasks on the main thread

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

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

Core Web Vitals

10 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 CLS: 0.67

    0.67

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

  • Real-user FCP: 4.3 s

    4.3 s

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

  • Real-user TTFB: 3.5 s

    3.5 s

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

  • Largest Contentful Paint: 17.0 s

    17.0 s

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

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 22.6 s

    22.6 s

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

  • Cumulative Layout Shift: 0.424

    0.424

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

  • 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

    +7%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 122 ms to 133 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-11-14, real Chrome visitors' largest content (lcp) went from 4.6 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user INP: 156 ms

    156 ms

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

  • Total Blocking Time: 169 ms

    169 ms

    Scripts block the page for only 169 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix38
  • Page weight: 5.5 MB in 184 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 184 requests on a phone: images 2.2 MB (12), scripts 1.6 MB (77) and fonts 1.4 MB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    2025-whitman-walker-animated-logo.gif weighs 1.6 MB. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (2.1 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.

  • 2 images below the first screen load straight away

    2 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.6 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 8391
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 21 text elements with low contrast

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

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

    All page content should be contained by landmarks: 27 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 (1 element)

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3, 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 10 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No XML sitemap

    No XML sitemap at https://whitman-walker.org/sitemap.xml, so Google discovers your pages only by following links.

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

  • 200 internal links, 18 external

    The homepage links to 200 pages on whitman-walker.org and 18 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Inclusive health care in Washington, DC: primary care, HIV and sexual health, gender-affirming care, dental and mental …”.

  • One H1 headline

    Your main headline reads: “Welcome to Whitman-Walker Health”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Whitman-Walker Health | LGBTQ+ Inclusive Health Care in DC”.

  • Canonical URL set

    The canonical URL is https://www.whitman-walker.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, MedicalOrganization, Organization and WebPage.

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

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 (1,101 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.whitman-walker.org/llms.txt (8 KiB, 86 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.whitman-walker.org/events has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.whitman-walker.org/events has no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://www.whitman-walker.org/about, https://www.whitman-walker.org/about/careers, https://www.whitman-walker.org/about/leadership, https://www.whitman-walker.org/about/providers, https://www.whitman-walker.org/locations and https://www.whitman-walker.org/about/quality-standards and 3 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 58 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 17 small tap targets

    17 of 82 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 511 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join a Research Study”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Join a Study” and “Schedule Online”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and “more than 20,000 patients”.

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 12 cookies set on arrival

    12

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 whitman-walker.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
GoDaddy

Hiring

Hiring
18 open roles
Job board
adp

Company

Employees
305

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on whitman-walker.org, including 23 speed issues, 2 SEO issues and 1 conversion gap. 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