morainevalley.edu website review

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

8 images could be 446 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

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

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

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

YouTube costs a phone 370 ms of main-thread work and 991 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.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,244 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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 could be saved by minifying CSS.

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

Your largest element takes 25.9 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 26.6 s. Good is under 3.8 s.

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

Scripts block taps and scrolling for 508 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 161 ms to 146 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 1.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.7 MB in 147 requests on a phone: images 3.3 MB (39), scripts 1.9 MB (31) and stylesheets 168 KiB (32). Under 2 MB keeps phones on slow connections fast.

4 images (348 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 1.61 g of CO₂e: 193.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

Your title is 111 characters, so Google will cut it off around 60: “Moraine Valley Community College - Degrees & Certificates in Palos Hills, IL - Moraine Va…”.

Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 151 pages on morainevalley.edu and 37 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.morainevalley.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.morainevalley.edu/events/list and https://www.morainevalley.edu/events all use the title “Events from October 31 – November 14 – Moraine Valley Community Colle…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.morainevalley.edu/admissions/apply-now, https://www.morainevalley.edu/videos, https://www.morainevalley.edu/events/list, https://www.morainevalley.edu/about/news, https://www.morainevalley.edu/2026/10/30/petition-filing-for-moraine-valley-board-of-trustees-starts-nov-16 and https://www.morainevalley.edu/2026/10/29/moraine-valley-looks-to-expand-career-and-technical-education-programs-experiencing-rapid-growth-across-illinois and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.morainevalley.edu/events/list, whose canonical is https://www.morainevalley.edu/events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.morainevalley.edu/admissions/apply-now, https://www.morainevalley.edu/current-student and https://www.morainevalley.edu/admissions/international-student have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.morainevalley.edu/admissions/international-student has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

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

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: 8 testimonial or review blocks. 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.

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

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

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