Website review, no card needed

moody.edu logo

moody.edu website review

Visit site (opens in a new tab)Reviewed 2 November 202633 issues · 69 checks

This review found 33 issues worth fixing on moody.edu, 10 of them high impact, across 69 checks. The most urgent: reduce unused JavaScript. 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.4 s3.1 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20264.2 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.7 s
Jun 27, 20264.9 s
Jul 4, 20264.8 s
Jul 11, 20264.7 s
Jul 18, 20264.5 s
Jul 25, 20264.1 s
Aug 1, 20264.4 s
Aug 8, 20264.4 s
Aug 15, 20264.5 s
Aug 22, 20264.7 s
Aug 29, 20264.9 s
Sep 5, 20265.1 s
Sep 12, 20265.0 s
Sep 19, 20264.7 s
Sep 26, 20264.4 s
Oct 3, 20264.3 s
Oct 10, 20264.0 s
Oct 17, 20264.1 s
Oct 24, 20263.9 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
163 ms140 msMay 16Oct 31152 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026143 ms
May 23, 2026145 ms
May 30, 2026145 ms
Jun 6, 2026148 ms
Jun 13, 2026147 ms
Jun 20, 2026155 ms
Jun 27, 2026158 ms
Jul 4, 2026152 ms
Jul 11, 2026152 ms
Jul 18, 2026151 ms
Jul 25, 2026152 ms
Aug 1, 2026158 ms
Aug 8, 2026157 ms
Aug 15, 2026156 ms
Aug 22, 2026153 ms
Aug 29, 2026152 ms
Sep 5, 2026153 ms
Sep 12, 2026157 ms
Sep 19, 2026158 ms
Sep 26, 2026160 ms
Oct 3, 2026158 ms
Oct 10, 2026155 ms
Oct 17, 2026158 ms
Oct 24, 2026154 ms
Oct 31, 2026152 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 moody.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moody.edu at 0.6 s0.6 s
  2. moody.edu at 1.2 s1.2 s
  3. moody.edu at 1.8 s1.8 s
  4. moody.edu at 2.4 s2.4 s
  5. moody.edu at 3.0 s3.0 s
  6. moody.edu at 3.6 s3.6 s
  7. moody.edu at 4.2 s4.2 s
  8. moody.edu at 4.8 s4.8 s

Speed

7 to fix66
  • Reduce unused JavaScript

    1.1 s · 695 KiB

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

  • Use efficient cache lifetimes

    950 ms · 473 KiB

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

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. 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, azure.com and ShareThis and others), adding 1.2 MB and 623 ms of main-thread time.

  • Google Tag Manager adds 563 ms

    563 ms

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

  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    608 KiB

    11 images could be 608 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

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

    A phone's processor spends 1.7 s on main-thread work while loading, 703 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

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

  • Time to Interactive: 12.9 s

    12.9 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Real-user TTFB: 880 ms

    880 ms

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Learn Biblically. Live Boldly.”. Most of its time is element render delay (2.4 s).

  • Total Blocking Time: 393 ms

    393 ms

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

  • Tap response (INP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user INP: 150 ms

    150 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 11.7 MB in 55 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 55 requests on a phone: media 9.3 MB (1), scripts 1.4 MB (16) and images 877 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • About 3.3 g of CO₂ per visit

    3.31 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fix90
  • 16 tap targets too small

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

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

SEO

4 to fixGoogle 8582
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 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 set, so this is minor.

6 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Moody Bible Institute offers accredited Christian higher education in Chicago, Washington, Michigan and online, with co…”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Bible College and Ministry Training”.

  • Canonical URL set

    The canonical URL is https://www.moody.edu/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.moody.edu/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 906 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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

Best practices

3 to fixGoogle 7785
  • 11 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

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

    The homepage carries about 906 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Apply Now”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 moody.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
Optimizely AB

Company

Employees
547
Founded
1886
Headquarters
Chicago

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on moody.edu, including 16 speed issues, 4 SEO issues and 3 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