schoolcraft.edu website review

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

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

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

8 third-party services load with your homepage (ocelotbot.com, Google Tag Manager and 451.io and others), adding 1.5 MB and 890 ms of main-thread time.

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

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

ocelotbot.com costs a phone 354 ms of main-thread work and 289 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.

Google Tag Manager costs a phone 249 ms of main-thread work and 301 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.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

451.io costs a phone 134 ms of main-thread work and 565 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.

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.

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

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 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We help students reach their full potential in their academ…”.

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

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

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

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

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-31, real Chrome visitors' tap response (inp) went from 75 ms to 77 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.1 MB in 108 requests on a phone: images 2.4 MB (9), scripts 1.2 MB (30) and fonts 264 KiB (12). Under 2 MB keeps phones on slow connections fast.

aside-student.png weighs 772 KiB. On a phone connection a single image that size takes seconds.

3 images further down the page (861 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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.

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

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

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

The homepage links to 73 pages on schoolcraft.edu and 22 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.schoolcraft.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.schoolcraft.edu/semester-guide, https://www.schoolcraft.edu/events, https://www.schoolcraft.edu/news, https://www.schoolcraft.edu/information-for, https://www.schoolcraft.edu/information-for/for-parents-families and https://www.schoolcraft.edu/information-for/for-future-students and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.schoolcraft.edu/information-for 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.

https://www.schoolcraft.edu/information-for, https://www.schoolcraft.edu/information-for/for-parents-families and https://www.schoolcraft.edu/information-for/for-community took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Error loading data: TypeError: Cannot read properties of null (reading 'content')”.

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.

The homepage carries about 669 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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 (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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.