mathforamerica.org website review

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Google Analytics and Plausible and others), adding 600 KiB and 291 ms of main-thread time.

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

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

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

5 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Desktop scores 94 but mobile only 64. 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.

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Teachers on board”.

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

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

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

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

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

Header_N4A1803.jpg 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 logo.svg at 158 px wide, shown at 1 px. Resized copies would save about 125 KiB.

2 images (80 KiB) 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.

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

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

Your title is only 10 characters: “Home | MƒA”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No XML sitemap at https://www.mathforamerica.org/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 59 pages on mathforamerica.org and 10 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.mathforamerica.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.mathforamerica.org/brief, https://www.mathforamerica.org/explore/words and https://www.mathforamerica.org/explore/numbers all use the title “Explore MƒA | MƒA”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.mathforamerica.org/application-info/mt, whose canonical is https://www.mathforamerica.org/application-info/mt/eligibility. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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 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 440 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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