Website review, no card needed
nmc.edu website review
Visit site (opens in a new tab)Reviewed 18 November 202635 issues · 84 checks
This review found 35 issues worth fixing on nmc.edu, 10 of them high impact, across 84 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 949 ms |
| Jun 6, 2026 | 976 ms |
| Jun 13, 2026 | 971 ms |
| Jun 20, 2026 | 986 ms |
| Jun 27, 2026 | 996 ms |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 979 ms |
| Oct 17, 2026 | 982 ms |
| Oct 24, 2026 | 981 ms |
| Oct 31, 2026 | 971 ms |
| Nov 7, 2026 | 988 ms |
| Nov 14, 2026 | 975 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 132 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 142 ms |
| Oct 31, 2026 | 139 ms |
| Nov 7, 2026 | 134 ms |
| Nov 14, 2026 | 121 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
3.0 s · 873 KiB8 images could be 873 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Reduce unused JavaScript
2.0 s · 355 KiBAbout 355 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Use efficient cache lifetimes
1.1 s · 206 KiB7 files are served with short cache lifetimes, so returning visitors download them again (206 KiB).
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Crazy Egg and others), adding 902 KiB and 691 ms of main-thread time.
Google Tag Manager adds 407 ms
407 msGoogle Tag Manager costs a phone 407 ms of main-thread work and 536 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 744 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NMC students and others hold signs raising homelessness awa…”.
Time to Interactive: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 103 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 330 ms
330 msScripts block taps and scrolling for 330 ms in total while the page loads. Good is under 200 ms.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 414 ms
414 msReal visitors wait 414 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 88 requests
2.6 MBYour homepage downloads 2.6 MB in 88 requests on a phone: images 1.5 MB (35), scripts 952 KiB (22) and fonts 110 KiB (3). Under 2 MB keeps phones on slow connections fast.
15 images in older formats
15 images (1.3 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.
2 images far larger than shown
2 KiB2 images are downloaded at several times the size a phone draws them, for example homepage-featured-item-community-college-guarantee-2026.jpg at 1,176 px wide, shown at 390 px. Resized copies would save about 2 KiB.
8 images below the first screen load straight away
8 images further down the page (285 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (96 characters)
Your title is 96 characters, so Google will cut it off around 60: “NMC | Northwestern Michigan College | Degrees, Certificates & Transfer Programs in Traver…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
135 internal links, 21 external
The homepage links to 135 pages on nmc.edu and 21 external pages.
5 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Start your next chapter at Northwestern Michigan College in Traverse City. Explore degrees, career programs and transfe…”.
One H1 headline
Your main headline reads: “Northwestern Michigan College - Affordable degrees and certificates”.
Canonical URL set
The canonical URL is https://www.nmc.edu/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.nmc.edu/site-map.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.nmc.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (591 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.nmc.edu/about/foundation/index.html has no meta description, so Google writes the search snippet from whatever text it finds.
9 links to non-canonical URLs
Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://www.nmc.edu/student-services/index.html, whose canonical is https://www.nmc.edu/student-services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.nmc.edu/about/foundation/index.html, https://www.nmc.edu/admissions/launchpad/quick-start.html and https://www.nmc.edu/admissions/launchpad/orientation.html have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187182362&Ver=2&mid=c4a79bf6-100f-4633-ad0d-a217d3cc7865&bo=1&sid=399e8b30e36f11f1a7b1bb193f7417ee&vid=399eb820e36f11f18f29a9cdb4350795&vids=1&msclkid=N&pi=918639831&l.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Ignoring duplicate Content-Security-Policy directive 'default-src'.”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
33 of 34 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 448 words of copy
The homepage carries about 448 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Apply now for free” and “Request more info”.
13 calls to action
The homepage has 13 calls to action, for example “Apply Now”, “Request Info” and “Request More Information”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
No consent tool detected
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.
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at nmc.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Merit Network Inc.
Company
- Employees
- 637
- Founded
- 1951
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on nmc.edu, including 14 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.