uwalumni.com website review

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

16 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

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

ZenDesk costs a phone 458 ms of main-thread work and 476 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.

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

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

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

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

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

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

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

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.

2 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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

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

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

Your homepage downloads 4.0 MB in 93 requests on a phone: images 2.3 MB (20), scripts 1.3 MB (41) and fonts 180 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

27 elements hidden from screen readers can still receive keyboard focus.

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

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

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.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

There are 5 <h1> headlines (“Your Guide to Old and New Madison Favorites”, “Nominations Are Open” and “Brought to You by Badgers”). One clear main headline is easier for people and search engines.

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

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

1 link has no real href, so search engines can't follow it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 77 pages on uwalumni.com and 29 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.uwalumni.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://www.uwalumni.com/membership/renew, https://www.uwalumni.com/update-info, https://www.uwalumni.com/email, https://www.uwalumni.com/events, https://www.uwalumni.com/news and https://www.uwalumni.com/membership and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

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.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel 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 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.