Website review, no card needed

pathwaystohousingpa.org logo

pathwaystohousingpa.org website review

Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 84 checks

This review found 35 issues worth fixing on pathwaystohousingpa.org, 10 of them high impact, across 84 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
1.5 s958 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.2 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.3 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
118 ms76 msMay 2Oct 3105 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202690 ms
May 9, 202695 ms
May 16, 202695 ms
May 23, 202692 ms
May 30, 202690 ms
Jun 6, 202686 ms
Jun 13, 202683 ms
Jun 20, 202681 ms
Jun 27, 202683 ms
Jul 4, 202687 ms
Jul 11, 202692 ms
Jul 18, 202699 ms
Jul 25, 202689 ms
Aug 1, 202681 ms
Aug 8, 202688 ms
Aug 15, 202690 ms
Aug 22, 202692 ms
Aug 29, 202698 ms
Sep 5, 202697 ms
Sep 12, 2026102 ms
Sep 19, 2026113 ms
Sep 26, 2026113 ms
Oct 3, 2026105 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 pathwaystohousingpa.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix46
  • Improve image delivery

    5.0 s · 1.5 MB

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

  • Reduce unused JavaScript

    3.9 s · 762 KiB

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

  • Render-blocking requests

    3.3 s

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

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46 (desktop: 71). 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 (YouTube, Google Tag Manager and jQuery CDN and others), adding 1.8 MB and 844 ms of main-thread time.

  • Reduce unused CSS

    610 ms · 192 KiB

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

  • YouTube adds 467 ms

    467 ms

    YouTube costs a phone 467 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 341 ms

    341 ms

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

  • 7 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 71 but mobile only 46. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    10 KiB

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

  • Use efficient cache lifetimes

    5 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 937 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 20.3 s

    20.3 s

    Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “participant smirking at camera outside, trees in background”.

  • Time to Interactive: 20.4 s

    20.4 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Total Blocking Time: 429 ms

    429 ms

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

  • 2 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 420 ms

    420 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

6 to fix43
  • 1 image over 500 KB

    [email protected] weighs 699 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.9 MB in 61 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 61 requests on a phone: images 1.8 MB (15), scripts 1.4 MB (14) and fonts 464 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.6 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.

  • An image on the first screen is lazy-loaded

    DSC_9133.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).

  • 6 images below the first screen load straight away

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

  • 2 images far larger than shown

    175 KiB

    2 images are downloaded at several times the size a phone draws them, for example 1.jpg at 1,000 px wide, shown at 240 px. Resized copies would save about 175 KiB.

  • About 1.1 g of CO₂ per visit

    1.09 g

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

Accessibility

Google 100100
  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 10077
  • Title is short (22 characters)

    Your title is only 22 characters: “Pathways to Housing PA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (65 characters)

    Your meta description is only 65 characters: “We believe that housing is a basic human right. It's that simple.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 101 internal links, 5 external

    The homepage links to 101 pages on pathwaystohousingpa.org and 5 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Homepage”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://pathwaystohousingpa.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.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://pathwaystohousingpa.org/our-team-leadership, https://pathwaystohousingpa.org/careers, https://pathwaystohousingpa.org/providing-homes, https://pathwaystohousingpa.org/restoring-health and https://pathwaystohousingpa.org/news 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 34 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

1 to fixGoogle 7797
  • 5 third-party cookies

    5 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”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix61
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

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

  • Only about 196 words

    The homepage has only about 196 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.

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

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Subscribe”, “Contact Us” and “Sign Up”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 pathwaystohousingpa.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
Drupal
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on pathwaystohousingpa.org, including 14 speed issues, 5 SEO issues and 6 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