Sacred Heart Community Service: website audit

Published October 7, 2026 · Unsolicited, unpaid, and independent

Sacred Heart Community Service has served San Jose since 1964, providing food, clothing, rent and utility help, job support, and help applying for public benefits. Many people find that help through its website, often on a phone. This free audit looks at how quickly and accessibly that website reaches them.

• Site: sacredheartcs.org (PageSpeed tested the www version it redirects to)
• Test: Google PageSpeed Insights, mobile, report from October 7, 2026, 2:04 PM
• Check it yourself: run a fresh test. Scores change as a site changes.

The four scores (lab test, mobile)

Accessibility, Best Practices, and SEO are all in Google's green range, which is a strong foundation. Performance is the clear outlier. The report also showed 1 of 2 checks passing in its newer Agentic Browsing section, which looks at how well automated assistants can read and use the page.

What real visitors experience (field data)

Separately from the lab test, Google reports how the page performed for real Chrome visitors over the previous 28 days. On mobile, the page did not pass Google's Core Web Vitals assessment.

In plain terms: the server responds quickly and the page reacts well to taps, but the main content takes about 3.5 seconds to appear for a typical mobile visitor, and parts of the page shift while it loads. Both are close to Google's targets, so focused fixes could move the page to passing.

Recommended fixes, highest impact first

These are the fixes that most often move scores like these. The live report lists the exact items for this page under Diagnostics, so start there and confirm each one.

1. Lighten the largest image or block at the top of the page. Compress it, serve a smaller version to phones, and don't lazy-load it. This is the main lever for the 3.5-second LCP.
2. Delay scripts that aren't needed in the first seconds, such as donation widgets, social embeds, analytics, and chat tools, until after the page loads or the visitor interacts.
3. Reserve space for anything that loads late, including images, banners, and embedded forms, with set widths and heights. That addresses the 0.11 layout shift.
4. Check the remaining accessibility and SEO items the report names, which are usually quick: missing labels, low-contrast text, or links without descriptive text.
5. Re-test after each change on mobile, and watch the field data improve over the following 28 days.

The site appears to run on a hosted website builder, which can limit how much of the underlying code can be changed. Image compression, removing unneeded add-ons, and reserving space for embeds are usually possible on any platform.