Website review, no card needed

fspymca.org logo

fspymca.org website review

Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 89 checks

This review found 44 issues worth fixing on fspymca.org, 17 of them high impact, across 89 checks. The most urgent: improve image delivery. 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.5 s1.1 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.5 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
179 ms103 msMay 2Oct 17131 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026170 ms
May 9, 2026151 ms
May 16, 2026155 ms
May 23, 2026149 ms
May 30, 2026152 ms
Jun 6, 2026129 ms
Jun 13, 2026144 ms
Jun 20, 2026154 ms
Jun 27, 2026138 ms
Jul 4, 2026129 ms
Jul 11, 2026120 ms
Jul 18, 2026112 ms
Jul 25, 2026116 ms
Aug 1, 2026121 ms
Aug 8, 2026121 ms
Aug 15, 2026120 ms
Aug 22, 2026120 ms
Aug 29, 2026129 ms
Sep 5, 2026133 ms
Sep 12, 2026137 ms
Sep 19, 2026145 ms
Sep 26, 2026113 ms
Oct 3, 2026114 ms
Oct 10, 2026133 ms
Oct 17, 2026131 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 fspymca.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fspymca.org at 0.5 s0.5 s
  2. fspymca.org at 1.0 s1.0 s
  3. fspymca.org at 1.5 s1.5 s
  4. fspymca.org at 2.0 s2.0 s
  5. fspymca.org at 2.4 s2.4 s
  6. fspymca.org at 2.9 s2.9 s
  7. fspymca.org at 3.4 s3.4 s
  8. fspymca.org at 3.9 s3.9 s

Speed

11 to fix47
  • Improve image delivery

    36.1 s · 11.7 MB

    17 images could be 11.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 36.1 s faster on a phone.

  • Reduce unused JavaScript

    7.7 s · 1.9 MB

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

  • Reduce unused CSS

    1.4 s · 412 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 47

    47/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 3.4 MB and 1.3 s of main-thread time.

  • YouTube adds 646 ms

    646 ms

    YouTube costs a phone 646 ms of main-thread work and 1.9 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.

  • Main-thread work: 3.9 s

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

  • Google Tag Manager adds 276 ms

    276 ms

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

  • 1,690 HTML elements

    The page has 1,690 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Google CDN adds 71 ms

    71 ms

    Google CDN costs a phone 71 ms of main-thread work and 356 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.

  • 15 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    38 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

  • Minify CSS

    10 KiB

    10 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: 87 ms

    87 ms

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

Core Web Vitals

10 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: 12.9 s

    12.9 s

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

  • Largest Contentful Paint: 96.2 s

    96.2 s

    Your largest element takes 96.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 16.2 s

    16.2 s

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

  • Time to Interactive: 98.0 s

    98.0 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Largest content (LCP) got 37% slower for real visitors

    +37%

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

  • Cumulative Layout Shift: 0.124

    0.124

    The layout shifts by 0.124 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 233 ms

    233 ms

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user INP: 186 ms

    186 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 347 ms

    347 ms

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

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

    -18%

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

Images and page weight

5 to fix28
  • Page weight: 23.3 MB in 213 requests

    23.3 MB

    Your homepage downloads 23.3 MB in 213 requests on a phone: images 17.3 MB (36), scripts 4.1 MB (105) and other files 1.0 MB (29). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.

  • 18 images in older formats

    18 images (6.2 MB) 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.

  • 5 images below the first screen load straight away

    5 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    335 KiB

    2 images are downloaded at several times the size a phone draws them, for example 0000614_797x1200-797x797.jpg at 797 px wide, shown at 250 px. Resized copies would save about 335 KiB.

  • About 6.6 g of CO₂ per visit

    6.62 g

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

Accessibility

8 to fixGoogle 8390
  • Images must have alternative text (4 elements)

    Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

  • 17 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

    All page content should be contained by landmarks: 3 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.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 46 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: 46 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

2 to fixGoogle 9288
  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “Fanwood-Scotch Plains YMCA :: Youth Development, Healthy Living, Social Responsibility”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“THE BEST SUMMERS HAPPEN AT THE Y!” and “Visit Our State-of-the-Art Wellness Center!”). One clear main headline is easier for people and search engines.

  • 131 internal links, 4 external

    The homepage links to 131 pages on fspymca.org and 4 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Dedicated to improving the quality of life of the individuals, families and communities through programs that build who…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://fspymca.org/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://fspymca.org/programs has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://fspymca.org/programs, https://fspymca.org/programs/child-care-camp, https://fspymca.org/programs/child-care-camp/child-care, https://fspymca.org/programs/child-care-camp/preschool-enrichment, https://fspymca.org/programs/child-care-camp/school-age-child-care-2 and https://fspymca.org/programs/child-care-camp/camp and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://fspymca.org/programs/child-care-camp/child-care, https://fspymca.org/counselor-in-training-cit-program, https://fspymca.org/programs/child-care-camp/kids-night-out and https://fspymca.org/programs/swimming took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 92 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 7797
  • 5 third-party cookies

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

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    17 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

    The homepage carries about 889 words of visible text.

3 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Register”, “Join the Y” and “Contact, Hours & Directions”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 27 other companies contacted

    Loading the homepage contacts 27 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 fspymca.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on fspymca.org, including 21 speed issues, 2 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

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