ymywha.com website review

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

8 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

About 485 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and cdn-cookieyes.com and others), adding 635 KiB and 349 ms of main-thread time.

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

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

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

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

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GET YOUR SWEAT ON • YOUR WAY! IT ALL STARTS INSIDE BUILDING…”.

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

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

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

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

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

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

Heritage-Words-Podcast-EN-768x768.png weighs 611 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.5 MB in 120 requests on a phone: images 1.4 MB (16), scripts 1.0 MB (41) and fonts 906 KiB (5). Under 2 MB keeps phones on slow connections fast.

3 images (1.1 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 is downloaded at several times the size a phone draws it, for example Logo_YM-YWHA_long_PMS-Orange.png at 474 px wide, shown at 100 px. Resized copies would save about 31 KiB.

2 images further down the page (100 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 0.98 g of CO₂e: 117.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 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: 15 elements on the page fail this check, rated moderate 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.

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

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

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

No XML sitemap at https://ymywha.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 235 pages on ymywha.com and 27 external pages.

Your Organization JSON-LD is missing logo, 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.

There is no https://ymywha.com/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://ymywha.com/fitness-aquatics/health-fitness/fitness-packages and https://ymywha.com/en/fitness-aquatics/health-fitness/fitness-packages all use the title “Sylvan Adams YM-YWHA Fitness Packages”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ymywha.com/fitness-aquatics/health-fitness/fitness-packages and https://ymywha.com/en/fitness-aquatics/health-fitness/fitness-packages use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ymywha.com/fitness-aquatics/health-fitness/fitness-packages, whose canonical is https://ymywha.com/en/fitness-aquatics/health-fitness/fitness-packages. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ymywha.com/en/hours-and-schedules, https://ymywha.com/en/sports-recreation/recreation/recreation-guide, https://ymywha.com/en/fitness-aquatics/health-fitness/powerwatts, https://ymywha.com/en/sports-recreation/sports-leagues/wrestling and https://ymywha.com/en/sports-recreation/sports-leagues/maccabi-games have no <h1> headline, so visitors and search engines get no clear main topic.

https://ymywha.com/en/sports-recreation/recreation/recreation-guide, https://ymywha.com/fitness-aquatics/health-fitness/fitness-packages, https://ymywha.com/en/fitness-aquatics/health-fitness/fitness-packages, https://ymywha.com/en/training-and-specialty-classes, https://ymywha.com/en/fitness-aquatics/health-fitness/powerwatts and https://ymywha.com/en/concordia-weightlifting and 5 others took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 480 words of visible text.

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

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

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