Website review, no card needed

greaternaplesymca.org logo

greaternaplesymca.org website review

Visit site (opens in a new tab)Reviewed 28 October 202638 issues · 88 checks

This review found 38 issues worth fixing on greaternaplesymca.org, 13 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
1.2 s920 msMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 2026974 ms
Jul 25, 2026955 ms
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
120 ms86 msMay 9Oct 24103 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026111 ms
May 23, 2026116 ms
May 30, 2026107 ms
Jun 6, 2026104 ms
Jun 13, 2026104 ms
Jun 20, 2026103 ms
Jun 27, 2026103 ms
Jul 4, 2026103 ms
Jul 11, 202695 ms
Jul 18, 202694 ms
Jul 25, 202690 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 2026101 ms
Aug 22, 2026108 ms
Aug 29, 2026110 ms
Sep 5, 2026113 ms
Sep 12, 2026110 ms
Sep 19, 2026106 ms
Sep 26, 2026107 ms
Oct 3, 2026108 ms
Oct 10, 2026110 ms
Oct 17, 2026105 ms
Oct 24, 2026103 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 greaternaplesymca.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. greaternaplesymca.org at 0.4 s0.4 s
  2. greaternaplesymca.org at 0.8 s0.8 s
  3. greaternaplesymca.org at 1.1 s1.1 s
  4. greaternaplesymca.org at 1.5 s1.5 s
  5. greaternaplesymca.org at 1.9 s1.9 s
  6. greaternaplesymca.org at 2.3 s2.3 s
  7. greaternaplesymca.org at 2.6 s2.6 s
  8. greaternaplesymca.org at 3.0 s3.0 s

Speed

11 to fix54
  • Use efficient cache lifetimes

    12.7 s · 4.9 MB

    44 files are served with short cache lifetimes, so returning visitors download them again (4.9 MB).

  • Improve image delivery

    1.5 s · 4.3 MB

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

  • Reduce unused JavaScript

    2.4 s · 679 KiB

    About 679 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.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (elfsightcdn.com, Google Tag Manager and Facebook and others), adding 5.5 MB and 1.3 s of main-thread time.

  • elfsightcdn.com adds 781 ms

    781 ms

    elfsightcdn.com costs a phone 781 ms of main-thread work and 4.6 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.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 32). Pages that score under 90 lose visitors before the first paint.

  • Font display

    700 ms

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

  • Main-thread work: 2.6 s

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

  • Google Tag Manager adds 228 ms

    228 ms

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

  • Facebook adds 167 ms

    167 ms

    Facebook costs a phone 167 ms of main-thread work and 302 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.

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 64 KiB

    64 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 22.5 s

    22.5 s

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

  • Time to Interactive: 28.7 s

    28.7 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Total Blocking Time: 435 ms

    435 ms

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 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.4 s

    1.4 s

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

  • Real-user INP: 101 ms

    101 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 467 ms

    467 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

4 to fix35
  • Page weight: 9.5 MB in 107 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 107 requests on a phone: images 7.8 MB (23), scripts 1.5 MB (28) and other files 97 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (1.5 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.

  • 1 image far larger than shown

    101 KiB

    1 image is downloaded at several times the size a phone draws it, for example four-starratingbadge_transparent_2026.png at 1,801 px wide, shown at 100 px. Resized copies would save about 101 KiB.

  • 1 image below the first screen load straight away

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

  • About 2.7 g of CO₂ per visit

    2.68 g

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

Accessibility

6 to fixGoogle 7790
  • Invalid ARIA attributes

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 28 text elements with low contrast

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

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • 7 links without text

    7 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 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9276
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 18 H1 headlines

    There are 18 <h1> headlines (“YMCA of Collier County”, “Building a Stronger Community” and “Chipping in to change lives”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (230 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links with vague text

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

  • 106 internal links, 16 external

    The homepage links to 106 pages on greaternaplesymca.org and 16 external pages.

3 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “YMCA Collier - Fitness Gym. Youth Programs. Community Resources”.

  • 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://ymcacollier.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://ymcacollier.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 (766 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 12 pages without a meta description

    https://ymcacollier.org/schedules.html, https://ymcacollier.org/hours.html, https://ymcacollier.org/careers.html, https://ymcacollier.org/y360.html, https://ymcacollier.org/corporatemembership.html and https://ymcacollier.org/military-outreach.html and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “missing ) after argument list”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 567 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 8 calls to action

    The homepage has 8 calls to action, for example “Join the Y!”, “Contact Us” and “LEARN MORE”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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 (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 greaternaplesymca.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Leaseweb

Company

Headquarters
Naples

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on greaternaplesymca.org, including 15 speed issues, 7 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