ymcasuperiorcal.org website review

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

About 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

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

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

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

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

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

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

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

FontAwesome CDN costs a phone 157 ms of main-thread work and 492 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.

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

About 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Desktop scores 82 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 26.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NPLTP Youth Sports”.

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 148 requests on a phone: scripts 2.3 MB (35), images 1.5 MB (46) and fonts 189 KiB (4). Under 2 MB keeps phones on slow connections fast.

New Equipment Announcement Graphics (1).png.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example f9d66171742d557e6a0134ad134f0b8a.jpeg.webp at 992 px wide, shown at 315 px. Resized copies would save about 12 KiB.

4 images further down the page (272 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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.

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

Your title is 86 characters, so Google will cut it off around 60: “YMCA of Superior California | Strengthening Community Through Youth, Health & Wellness”.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 96 pages on ymcasuperiorcal.org and 20 external pages.

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.

There is no https://www.ymcasuperiorcal.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.

https://www.ymcasuperiorcal.org/join-online, https://www.ymcasuperiorcal.org/aquatics, https://www.ymcasuperiorcal.org/health, https://www.ymcasuperiorcal.org/social-responsibility, https://www.ymcasuperiorcal.org/swimclinics and https://www.ymcasuperiorcal.org/swimlessons and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Identifier '__atftcframe' has already been declared”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,006 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

Opening the homepage sets 13 cookies (measured from a US location before any click).

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.

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