Website review, no card needed
hosparrow.org website review
Visit site (opens in a new tab)Reviewed 22 October 202620 issues · 84 checks
This review found 20 issues worth fixing on hosparrow.org, 9 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 910 ms |
| May 9, 2026 | 902 ms |
| May 16, 2026 | 914 ms |
| May 23, 2026 | 947 ms |
| May 30, 2026 | 953 ms |
| Jun 6, 2026 | 946 ms |
| Jun 13, 2026 | 971 ms |
| Jun 20, 2026 | 927 ms |
| Jun 27, 2026 | 943 ms |
| Jul 4, 2026 | 978 ms |
| Jul 11, 2026 | 982 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 983 ms |
| Aug 1, 2026 | 966 ms |
| Aug 8, 2026 | 916 ms |
| Aug 15, 2026 | 908 ms |
| Aug 22, 2026 | 946 ms |
| Aug 29, 2026 | 982 ms |
| Sep 5, 2026 | 993 ms |
| Sep 12, 2026 | 964 ms |
| Sep 19, 2026 | 999 ms |
| Sep 26, 2026 | 994 ms |
| Oct 3, 2026 | 997 ms |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 71 ms |
| May 9, 2026 | 70 ms |
| May 16, 2026 | 70 ms |
| May 23, 2026 | 70 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 72 ms |
| Jul 25, 2026 | 73 ms |
| Aug 1, 2026 | 75 ms |
| Aug 8, 2026 | 73 ms |
| Aug 15, 2026 | 71 ms |
| Aug 22, 2026 | 72 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 71 ms |
| Sep 19, 2026 | 72 ms |
| Sep 26, 2026 | 76 ms |
| Oct 3, 2026 | 79 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 80 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
Speed
Reduce unused JavaScript
2.4 s · 382 KiBAbout 382 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.8 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 95). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 81 KiBAbout 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google CDN adds 64 ms
64 msGoogle CDN costs a phone 64 ms of main-thread work and 347 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.
6 third-party services on the page
6 third-party services load with your homepage (Google CDN, Constant Contact and wpmucdn.com and others), adding 508 KiB and 104 ms of main-thread time.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
100 ms · 46 KiB3 files are served with short cache lifetimes, so returning visitors download them again (46 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 95 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 233 ms of it running JavaScript. That is comfortably low.
Server response: 37 ms
37 msYour server sent the HTML in 37 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Strength of a Sparrow Hope, Opportunity and Support We …”.
First Contentful Paint: 7.2 s
7.2 sThe first text or image appears after 7.2 s on a phone. Good is under 1.8 s.
Time to Interactive: 14.0 s
14.0 sThe page becomes fully interactive after 14.0 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 71 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 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.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 658 ms
658 msReal visitors wait 658 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 16 ms
16 msScripts block the page for only 16 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (41 KiB) is 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 0.5 g of CO₂ per visit
0.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 63.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.9 MB in 68 requests
1.9 MBYour homepage downloads 1.9 MB in 68 requests on a phone: scripts 734 KiB (33), images 679 KiB (5) and fonts 344 KiB (11). That is a lean page.
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
20 text elements with low contrast
20 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 (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Headings skip levels
Headings skip levels (h2 → h4, 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 4 images in the HTML carry an alt attribute.
37 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: 37 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (84 characters)
Your title is 84 characters, so Google will cut it off around 60: “Home of the Sparrow | Hope, Opportunity and Support that Empowers Women and Children”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
91 internal links, 17 external
The homepage links to 91 pages on hosparrow.org and 17 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “The Strength of a Sparrow Hope, Opportunityand Support We strive to empower women and children as they journey from hom…”.
One H1 headline
Your main headline reads: “Hope, Opportunityand Support”.
Canonical URL set
The canonical URL is https://hosparrow.org/.
Structured data in place
Structured data found: NGO, Person 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://hosparrow.org/sitemap.xml.
AI search readiness
No llms.txt
There is no https://hosparrow.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: 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 (762 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
7 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.
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 small tap targets
3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 635 words of copy
The homepage carries about 635 words of visible text.
6 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “Contact” and “Request a Speaker”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Matomo.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 hosparrow.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
- Matomo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on hosparrow.org, including 9 speed issues, 3 SEO issues and 3 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.