Website review, no card needed

jawonio.org logo

jawonio.org website review

Visit site (opens in a new tab)Reviewed 31 October 202647 issues · 94 checks

This review found 47 issues worth fixing on jawonio.org, 20 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
2.4 s1.6 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
168 ms97 msMay 9Oct 24105 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026154 ms
May 16, 2026160 ms
May 23, 2026142 ms
May 30, 2026130 ms
Jun 6, 2026122 ms
Jun 13, 2026122 ms
Jun 20, 2026130 ms
Jun 27, 2026139 ms
Jul 4, 2026131 ms
Jul 11, 2026128 ms
Jul 18, 2026119 ms
Jul 25, 2026118 ms
Aug 1, 2026116 ms
Aug 8, 2026112 ms
Aug 15, 2026127 ms
Aug 22, 2026127 ms
Aug 29, 2026119 ms
Sep 5, 2026140 ms
Sep 12, 2026136 ms
Sep 19, 2026136 ms
Sep 26, 2026134 ms
Oct 3, 2026111 ms
Oct 10, 2026107 ms
Oct 17, 2026105 ms
Oct 24, 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 jawonio.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jawonio.org at 0.6 s0.6 s
  2. jawonio.org at 1.1 s1.1 s
  3. jawonio.org at 1.7 s1.7 s
  4. jawonio.org at 2.3 s2.3 s
  5. jawonio.org at 2.8 s2.8 s
  6. jawonio.org at 3.4 s3.4 s
  7. jawonio.org at 3.9 s3.9 s
  8. jawonio.org at 4.5 s4.5 s

Speed

14 to fix30
  • Reduce unused JavaScript

    4.5 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

  • Improve image delivery

    4.0 s · 822 KiB

    2 images could be 822 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

  • Render-blocking requests

    3.8 s

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

  • Use efficient cache lifetimes

    1.9 s · 432 KiB

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

  • Reduce unused CSS

    1.2 s · 453 KiB

    About 453 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, hsappstatic.net and Hubspot and others), adding 3.6 MB and 1.8 s of main-thread time.

  • YouTube adds 527 ms

    527 ms

    YouTube costs a phone 527 ms of main-thread work and 1,018 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.

  • 20 long tasks on the main thread

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

  • hsappstatic.net adds 287 ms

    287 ms

    hsappstatic.net costs a phone 287 ms of main-thread work and 878 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.

  • Hubspot adds 270 ms

    270 ms

    Hubspot costs a phone 270 ms of main-thread work and 223 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 256 ms

    256 ms

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

  • Vimeo adds 45 ms

    45 ms

    Vimeo costs a phone 45 ms of main-thread work and 645 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.

  • Legacy JavaScript

    200 ms · 33 KiB

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

  • Font display

    50 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 3 ms

    3 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Largest Contentful Paint: 24.4 s

    24.4 s

    Your largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “More than just a job. A chance to change the lives of other…”.

  • Time to Interactive: 34.3 s

    34.3 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • First Contentful Paint: 6.1 s

    6.1 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 108 ms

    108 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Tap response (INP) got 33% faster for real visitors

    -33%

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

  • Cumulative Layout Shift: 0.096

    0.096

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

Images and page weight

4 to fix35
  • Page weight: 26.8 MB in 217 requests

    26.8 MB

    Your homepage downloads 26.8 MB in 217 requests on a phone: media 20.7 MB (3), scripts 3.2 MB (78) and images 1.7 MB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Jawonio_Logo_Copyright_Blue-scaled.png weighs 776 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (829 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.

  • 1 image far larger than shown

    41 KiB

    1 image is downloaded at several times the size a phone draws it, for example Jawonio_Logo_Copyright_White.png at 2,361 px wide, shown at 370 px. Resized copies would save about 41 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (53 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 7.6 g of CO₂ per visit

    7.60 g

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

Accessibility

8 to fixGoogle 8290
  • Invalid ARIA attributes

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

  • 9 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

    All page content should be contained by landmarks: 20 elements on the page fail 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 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (466 characters)

    Your meta description is 466 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 123 internal links, 14 external

    The homepage links to 123 pages on jawonio.org and 14 external pages.

6 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Jawonio | The Premiere Provider of Lifespan Services”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://jawonio.org/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://jawonio.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 (836 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 2 pages share a meta description

    https://jawonio.org/jawonio-inc and https://jawonio.org/residential-opportunities-inc use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://jawonio.org/Outpatient-article-16-clinic, whose canonical is https://jawonio.org/outpatient-article-16-clinic. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages without an H1

    https://jawonio.org/about, https://jawonio.org/randi-rios-castro, https://jawonio.org/jawonio-inc, https://jawonio.org/residential-opportunities-inc, https://jawonio.org/leadership-team and https://jawonio.org/jawonio-in-the-news and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://jawonio.org/leadership-team has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 56 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.

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

  • 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

4 to fixGoogle 5483
  • 8 third-party cookies

    8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 7 small tap targets

    7 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 5 low-resolution images

    5 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 294 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact”, “Start a Fundraiser” and “Join Our Team”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and HubSpot.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 3 of them by other companies (measured from a US location before any click).

  • 33 other companies contacted

    Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 jawonio.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
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
WP Engine

Company

Employees
600

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on jawonio.org, including 22 speed issues, 3 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

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