wcaeagles.org website review

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Google CDN and Bootstrap CDN and others), adding 337 KiB and 265 ms of main-thread time.

About 26 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.

About 167 KiB of JavaScript is downloaded but never used on this page.

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

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.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 75.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lady Eagles Volleyball Team. Discovering TRUTH in Athletics.”.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 73 ms to 89 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.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 21.3 MB in 54 requests on a phone: images 20.7 MB (27), scripts 420 KiB (10) and fonts 117 KiB (2). Under 2 MB keeps phones on slow connections fast.

8 images weigh 17.2 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example slideshow39_6.png at 1,680 px wide, shown at 390 px. Resized copies would save about 710 KiB.

19 images (19.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.

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

Certain ARIA roles must be contained by particular parents: 7 elements on the page fail this check, rated critical by axe-core.

All page content should be contained by landmarks: 3 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: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (8 elements).

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

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

Your meta description is 170 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.

There is no robots.txt at wcaeagles.org/robots.txt, the first file search crawlers ask for.

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

4 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 85 pages on wcaeagles.org and 28 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.wcaeagles.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.wcaeagles.org/tour-wca/wca-parents.cfm and https://www.wcaeagles.org/admissions/visit.cfm have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “$(...).cycle is not a function”.

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.

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

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

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 8 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.