Website review, no card needed
fourthstreetclinic.org website review
Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 84 checks
This review found 40 issues worth fixing on fourthstreetclinic.org, 16 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 94 ms |
| May 9, 2026 | 88 ms |
| May 16, 2026 | 88 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 110 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 93 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 109 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 115 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
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Use efficient cache lifetimes
19.4 s · 4.0 MB124 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).
Reduce unused JavaScript
6.6 s · 946 KiBAbout 946 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Improve image delivery
2.1 s · 683 KiB23 images could be 683 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.9 MB and 989 ms of main-thread time.
Reduce unused CSS
750 ms · 234 KiBAbout 234 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
750 ms18 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 445 ms
445 msGoogle Tag Manager costs a phone 445 ms of main-thread work and 862 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 386 ms
386 msGoogle CDN costs a phone 386 ms of main-thread work and 734 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
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
200 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 171 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.
1 checks passed
Server response: 124 ms
124 msYour server sent the HTML in 124 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.7 s
3.7 sReal visitors wait 3.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 32.0 s
32.0 sYour largest element takes 32.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DONATE MAIN CLINIC MAKE AN APPOINTMENT STORIES FROM THE STR…”.
Time to Interactive: 32.2 s
32.2 sThe page becomes fully interactive after 32.2 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 94 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 593 ms
593 msScripts block taps and scrolling for 593 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 147 requests
6.3 MBYour homepage downloads 6.3 MB in 147 requests on a phone: images 3.4 MB (31), scripts 2.0 MB (88) and other files 353 KiB (5). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (118 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.
4 images below the first screen load straight away
4 images further down the page (131 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 214.5 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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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 (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
106 internal links, 0 external
The homepage links to 106 pages on fourthstreetclinic.org and 0 external pages.
7 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Fourth Street Clinic provides high-quality and extensive health care and support services to homeless men, women and ch…”.
Title: 61 characters
Your title is a healthy 61 characters: “Homelessness Hurts. Health Care Helps. | Fourth Street Clinic”.
Canonical URL set
The canonical URL is https://fourthstreetclinic.org/.
Structured data in place
Structured data found: BreadcrumbList, 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://fourthstreetclinic.org/sitemap_index.xml.
AI search readiness
Some text only appears after JavaScript runs
50%The HTML your server sends has 442 of the 877 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
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.
Other pages
3 pages share a title
https://fourthstreetclinic.org/hours-location, https://fourthstreetclinic.org/satellitesites and https://fourthstreetclinic.org/holidayhours all use the title “Hours & Location Homeless Health Care | Fourth Street Clinic”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://fourthstreetclinic.org/hours-location, https://fourthstreetclinic.org/satellitesites and https://fourthstreetclinic.org/holidayhours use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://fourthstreetclinic.org/make-an-appointment, https://fourthstreetclinic.org/services, https://fourthstreetclinic.org/insurance, https://fourthstreetclinic.org/hours-location, https://fourthstreetclinic.org/satellitesites and https://fourthstreetclinic.org/holidayhours and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages slow to respond
https://fourthstreetclinic.org/make-an-appointment, https://fourthstreetclinic.org/services, https://fourthstreetclinic.org/insurance, https://fourthstreetclinic.org/hours-location, https://fourthstreetclinic.org/satellitesites and https://fourthstreetclinic.org/holidayhours and 9 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 36 found) and read each the way a search engine does.
5 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
39 of 42 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 877 words of copy
The homepage carries about 877 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join Us” and “Open submenu of Join Us”.
4 calls to action
The homepage has 4 calls to action, for example “Join Us”, “Open submenu of Join Us” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
8 other companies contacted
Loading the homepage contacts 8 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 fourthstreetclinic.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
Company
- Headquarters
- Salt Lake City
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on fourthstreetclinic.org, including 22 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.