mhu.edu website review

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

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

Your mobile performance score is 48 (desktop: 93). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Adroll and others), adding 1.5 MB and 896 ms of main-thread time.

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

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

blackbaudhosting.com costs a phone 92 ms of main-thread work and 399 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.

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

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

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

Desktop scores 93 but mobile only 48. 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.

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Visit Us! Tour our beautiful campus Sign Up!”.

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

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

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

Real visitors see the first content after 2.6 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.

The layout shifts by 0.183 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 6.5 MB in 192 requests on a phone: images 4.7 MB (82), scripts 1.4 MB (42) and other files 239 KiB (49). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA input fields must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (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.

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

The homepage links to 374 pages on mhu.edu and 36 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.mhu.edu/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.mhu.edu/about/what-to-do-and-see, https://www.mhu.edu/about/what-to-do-and-see/museum, https://www.mhu.edu/about/what-to-do-and-see/ramsey-center, https://www.mhu.edu/about/what-to-do-and-see/ramsey-center/lunsford-festival, https://www.mhu.edu/about/what-to-do-and-see/bailey-mountain-cloggers and https://www.mhu.edu/academics/majors-and-minors/sart-southern-appalachian-repertory-theatre and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mhu.edu/academics/majors-and-minors/sart-southern-appalachian-repertory-theatre, whose canonical is https://www.mhu.edu/academics/majors-and-minors/theatre-arts-old__trashed/sart-southern-appalachian-repertory-theatre. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mhu.edu/about/what-to-do-and-see/museum, https://www.mhu.edu/about/what-to-do-and-see/ramsey-center/lunsford-festival and https://www.mhu.edu/about/what-to-do-and-see/summer-opportunities-at-mars-hill have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mhu.edu/about/what-to-do-and-see/museum, https://www.mhu.edu/about/what-to-do-and-see/ramsey-center and https://www.mhu.edu/about/what-to-do-and-see/bailey-mountain-cloggers took over 3 s to send their HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot set properties of undefined (setting 'value')”.

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 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 513 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 19 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.