mnautism.org website review

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

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

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

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

25 KiB could be saved by minifying JavaScript.

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

5 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and bloomerang.co and others), adding 473 KiB and 171 ms of main-thread time.

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

3 long tasks block the main thread while loading, the longest for 93 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.

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 32.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 8.0 MB in 95 requests on a phone: images 6.8 MB (12), scripts 617 KiB (29) and fonts 444 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Your title is only 22 characters: “Homepage - MAC Midwest”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 75 pages on mnautism.org and 7 external pages.

Your Organization JSON-LD is missing 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://www.mnautism.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.mnautism.org/who-we-are, https://www.mnautism.org/our-team, https://www.mnautism.org/board-of-directors, https://www.mnautism.org/foundation-board, https://www.mnautism.org/careers and https://www.mnautism.org/news-articles and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage 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 429 ()”.

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.

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 has only about 5 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

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.