Website review, no card needed

mlc-wels.edu logo

mlc-wels.edu website review

Visit site (opens in a new tab)Reviewed 30 October 202656 issues · 99 checks

This review found 56 issues worth fixing on mlc-wels.edu, 26 of them high impact, across 99 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.0 s3.1 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20263.7 s
Sep 12, 20264.0 s
Sep 19, 20264.5 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.6 s
Oct 17, 20264.5 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
101 ms83 msMay 9Oct 2490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202686 ms
May 16, 202686 ms
May 23, 202685 ms
May 30, 202685 ms
Jun 6, 202685 ms
Jun 13, 202685 ms
Jun 20, 202687 ms
Jun 27, 202693 ms
Jul 4, 202694 ms
Jul 11, 202690 ms
Jul 18, 202690 ms
Jul 25, 202689 ms
Aug 1, 202693 ms
Aug 8, 202694 ms
Aug 15, 202695 ms
Aug 22, 202695 ms
Aug 29, 202694 ms
Sep 5, 202695 ms
Sep 12, 202697 ms
Sep 19, 202699 ms
Sep 26, 202698 ms
Oct 3, 202696 ms
Oct 10, 202692 ms
Oct 17, 202690 ms
Oct 24, 202690 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

Full-page screenshot of mlc-wels.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mlc-wels.edu at 2.1 s2.1 s
  2. mlc-wels.edu at 4.1 s4.1 s
  3. mlc-wels.edu at 6.2 s6.2 s
  4. mlc-wels.edu at 8.3 s8.3 s
  5. mlc-wels.edu at 10.3 s10.3 s
  6. mlc-wels.edu at 12.4 s12.4 s
  7. mlc-wels.edu at 14.5 s14.5 s
  8. mlc-wels.edu at 16.6 s16.6 s

Speed

17 to fix37
  • Use efficient cache lifetimes

    49.0 s · 13.2 MB

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

  • Reduce unused JavaScript

    14.8 s · 2.8 MB

    About 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 14.8 s faster on a phone.

  • Improve image delivery

    9.7 s · 4.9 MB

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

  • Render-blocking requests

    9.4 s

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

  • Reduce unused CSS

    7.6 s · 1.6 MB

    About 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.6 s faster on a phone.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 3.2 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.

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 7.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, googleapis.com and Other Google APIs/SDKs and others), adding 4.8 MB and 2.0 s of main-thread time.

  • Font display

    800 ms

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

  • Minify CSS

    600 ms · 106 KiB

    106 KiB could be saved by minifying CSS.

  • googleapis.com adds 538 ms

    538 ms

    googleapis.com costs a phone 538 ms of main-thread work and 755 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.

  • Minify JavaScript

    450 ms · 101 KiB

    101 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    350 ms · 67 KiB

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

  • 20 long tasks on the main thread

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

  • 1,950 HTML elements

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

  • google.com adds 22 ms

    22 ms

    google.com costs a phone 22 ms of main-thread work and 389 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.

  • Document request latency

    120 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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.

1 checks passed
  • Server response: 78 ms

    78 ms

    Your server sent the HTML in 78 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • Fails Core Web Vitals for real visitors

    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-user LCP: 6.7 s

    6.7 s

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

  • Real-user FCP: 5.6 s

    5.6 s

    Real visitors see the first content after 5.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • First Contentful Paint: 10.5 s

    10.5 s

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

  • Largest Contentful Paint: 85.1 s

    85.1 s

    Your largest element takes 85.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide background”.

  • Speed Index: 37.1 s

    37.1 s

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

  • Time to Interactive: 90.6 s

    90.6 s

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

  • Total Blocking Time: 758 ms

    758 ms

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

  • Largest content (LCP) got 31% slower for real visitors

    +31%

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

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user INP: 139 ms

    139 ms

    Real visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 36.8 MB in 264 requests

    36.8 MB

    Your homepage downloads 36.8 MB in 264 requests on a phone: media 18.2 MB (4), images 8.9 MB (41) and scripts 5.0 MB (92). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    970 KiB

    3 images are downloaded at several times the size a phone draws them, for example 2024-Place-to-Grow-scaled.jpg at 2,560 px wide, shown at 463 px. Resized copies would save about 970 KiB.

  • 13 images in older formats

    13 images (3.2 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 10.4 g of CO₂ per visit

    10.44 g

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

Accessibility

9 to fixGoogle 8588
  • 8 text elements with low contrast

    8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (66 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 4 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (5 elements)

    Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7783
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 3 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 186 internal links, 49 external

    The homepage links to 186 pages on mlc-wels.edu and 49 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “You: Knighted for Ministry”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Martin Luther College – The WELS College of Ministry”.

  • Canonical URL set

    The canonical URL is https://mlc-wels.edu/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://mlc-wels.edu/sitemap.xml.

AI search readiness

1 to fix88
  • 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://mlc-wels.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 (1,157 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://mlc-wels.edu/calendar is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://mlc-wels.edu/strategic-plan, https://mlc-wels.edu/streams, https://mlc-wels.edu/a-z, https://mlc-wels.edu/about/mission-statement, https://mlc-wels.edu/about/leadership and https://mlc-wels.edu/directory and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://mlc-wels.edu/a-z, https://mlc-wels.edu/directory and https://mlc-wels.edu/contact took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    17 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 837 words of copy

    The homepage carries about 837 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Apply Today” and “Apply for Aid”.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 mlc-wels.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 1995.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Nutelecom

Company

Founded
1995
Headquarters
New Ulm

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on mlc-wels.edu, including 28 speed issues, 4 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25