Website review, no card needed

ywcachicago.org logo

ywcachicago.org website review

Visit site (opens in a new tab)Reviewed 26 October 202637 issues · 85 checks

This review found 37 issues worth fixing on ywcachicago.org, 16 of them high impact, across 85 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
3.8 s2.5 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.6 s
Jun 20, 20263.3 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.0 s
Aug 22, 20263.2 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
113 ms96 msMay 9Oct 24105 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202699 ms
May 16, 2026101 ms
May 23, 2026105 ms
May 30, 2026107 ms
Jun 6, 2026106 ms
Jun 13, 2026111 ms
Jun 20, 2026105 ms
Jun 27, 202698 ms
Jul 4, 2026100 ms
Jul 11, 2026102 ms
Jul 18, 2026102 ms
Jul 25, 2026102 ms
Aug 1, 2026103 ms
Aug 8, 2026101 ms
Aug 15, 2026100 ms
Aug 22, 2026105 ms
Aug 29, 2026109 ms
Sep 5, 2026110 ms
Sep 12, 2026110 ms
Sep 19, 2026110 ms
Sep 26, 2026106 ms
Oct 3, 2026103 ms
Oct 10, 2026106 ms
Oct 17, 2026104 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 ywcachicago.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ywcachicago.org at 0.7 s0.7 s
  2. ywcachicago.org at 1.4 s1.4 s
  3. ywcachicago.org at 2.1 s2.1 s
  4. ywcachicago.org at 2.8 s2.8 s
  5. ywcachicago.org at 3.4 s3.4 s
  6. ywcachicago.org at 4.1 s4.1 s
  7. ywcachicago.org at 4.8 s4.8 s
  8. ywcachicago.org at 5.5 s5.5 s

Speed

13 to fix29
  • Reduce unused JavaScript

    5.7 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 5.7 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Improve image delivery

    2.3 s · 445 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 325 KiB

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

  • Reduce unused CSS

    1.1 s · 181 KiB

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

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 7.7 s

    A phone's processor spends 7.7 s on main-thread work while loading, 3.1 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 (Squarespace, Google CDN and Google Tag Manager and others), adding 3.7 MB and 2.7 s of main-thread time.

  • Squarespace adds 888 ms

    888 ms

    Squarespace costs a phone 888 ms of main-thread work and 1.3 MB 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 773 ms

    773 ms

    Google CDN costs a phone 773 ms of main-thread work and 1.1 MB 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 549 ms

    549 ms

    Google Tag Manager costs a phone 549 ms of main-thread work and 632 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 383 ms. During a long task the page ignores taps.

  • everyaction.com adds 229 ms

    229 ms

    everyaction.com costs a phone 229 ms of main-thread work and 313 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 · 114 KiB

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

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

    52 ms

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

Core Web Vitals

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

  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 22.4 s

    22.4 s

    Your largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YWCA Metropolitan Chicago is dedicated to eliminating racis…”.

  • Time to Interactive: 27.5 s

    27.5 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 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) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user TTFB: 743 ms

    743 ms

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 135 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 135 requests on a phone: scripts 3.3 MB (63), images 601 KiB (22) and other files 504 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (47 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 1.5 g of CO₂ per visit

    1.46 g

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

2 checks passed
  • 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

3 to fixGoogle 9396
  • 5 text elements with low contrast

    5 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 (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • 4 H1 headlines

    There are 4 <h1> headlines (“YWCA Metropolitan Chicago is dedicated to elimina…”, “What We Do ↘” and “Community Impact ↘”). One clear main headline is easier for people and search engines.

  • Meta description is long (397 characters)

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

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/651af12c3ba5380699d…”.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 93 internal links, 10 external

    The homepage links to 93 pages on ywcachicago.org and 10 external pages.

5 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “YWCA Metropolitan Chicago | Dignity For All”.

  • Canonical URL set

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

  • 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://ywcachicago.org/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo and description. 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://ywcachicago.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 (574 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 6 pages without a meta description

    https://ywcachicago.org/locations, https://ywcachicago.org/luncheon, https://ywcachicago.org/150, https://ywcachicago.org/plannedgiving, https://ywcachicago.org/monthlygiving and https://ywcachicago.org/otherwaystogive have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://ywcachicago.org/advancing-healing-safety-and-belonging and https://ywcachicago.org/unleashing-youth-family-potential use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://ywcachicago.org/luncheon, https://ywcachicago.org/our-work, https://ywcachicago.org/supportywca, https://ywcachicago.org/monthlygiving and https://ywcachicago.org/otherwaystogive have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://ywcachicago.org/our-work, https://ywcachicago.org/supportywca and https://ywcachicago.org/otherwaystogive have 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 29 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.

  • 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

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'insertAdjacentHTML')”.

2 checks passed
  • Tap targets are thumb-sized

    18 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 465 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE” and “APPLY NOW”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Learn More”, “Apply Now” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 2 cookies set on arrival

    2

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 ywcachicago.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
Squarespace
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 37 issues on ywcachicago.org, including 22 speed issues, 4 SEO issues and 1 conversion gap. 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