mountunion.edu website review

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

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

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

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

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

Google Tag Manager costs a phone 1.7 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

About 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

Facebook costs a phone 342 ms of main-thread work and 253 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.

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

Polyfills for old browsers add 30 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.

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 187.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “chapman hall in spring”.

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

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

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

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

Real visitors wait 2.9 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.

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

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

5 images 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' tap response (inp) went from 114 ms to 134 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.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 62.4 MB in 175 requests on a phone: images 59.5 MB (61), scripts 2.1 MB (43) and fonts 476 KiB (6). Under 2 MB keeps phones on slow connections fast.

19 images weigh 56.3 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example U. Mount Union 09.2016-1073.jpg at 4,000 px wide, shown at 390 px. Resized copies would save about 9.7 MB.

33 images (59.0 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.

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

6 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

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 209 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

The homepage links to 106 pages on mountunion.edu and 36 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.mountunion.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.

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

1 image failed to load on a phone, for example https://trck.youvisit.com/page/120060.png?embed=4114664110281274&pageSessionId=91b169ff-05a8-44bb-8e44-d8f8eb761b89&source=vhost.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 22 cookies, 3 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.