Website review, no card needed

truett.edu logo

truett.edu website review

Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 80 checks

This review found 35 issues worth fixing on truett.edu, 12 of them high impact, across 80 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
2.2 s913 msMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.6 s
Oct 31, 20261.7 s
Nov 7, 20261.6 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
127 ms82 msMay 30Nov 14103 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jun 6, 2026112 ms
Jun 13, 2026108 ms
Jun 20, 2026109 ms
Jun 27, 2026107 ms
Jul 4, 2026112 ms
Jul 11, 2026113 ms
Jul 18, 2026106 ms
Jul 25, 2026105 ms
Aug 1, 2026101 ms
Aug 8, 202699 ms
Aug 15, 202696 ms
Aug 22, 202693 ms
Aug 29, 202691 ms
Sep 5, 202688 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202694 ms
Oct 17, 202696 ms
Oct 24, 2026103 ms
Oct 31, 202696 ms
Nov 7, 202687 ms
Nov 14, 2026103 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 truett.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. truett.edu at 0.4 s0.4 s
  2. truett.edu at 0.8 s0.8 s
  3. truett.edu at 1.2 s1.2 s
  4. truett.edu at 1.6 s1.6 s
  5. truett.edu at 2.0 s2.0 s
  6. truett.edu at 2.4 s2.4 s
  7. truett.edu at 2.8 s2.8 s
  8. truett.edu at 3.2 s3.2 s

Speed

10 to fix54
  • Use efficient cache lifetimes

    2.7 s · 520 KiB

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

  • Reduce unused JavaScript

    2.4 s · 368 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    1.3 MB

    4 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. 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 curator.io and others), adding 1.2 MB and 649 ms of main-thread time.

  • Google Tag Manager adds 334 ms

    334 ms

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

  • Reduce unused CSS

    300 ms · 59 KiB

    About 59 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.

  • Legacy JavaScript

    300 ms · 32 KiB

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

  • Facebook adds 192 ms

    192 ms

    Facebook costs a phone 192 ms of main-thread work and 304 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 217 ms. During a long task the page ignores taps.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

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

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 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.

  • Largest Contentful Paint: 12.1 s

    12.1 s

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

  • Time to Interactive: 12.2 s

    12.2 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Total Blocking Time: 330 ms

    330 ms

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

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

    +14%

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

4 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Tap response (INP) got 19% faster for real visitors

    -19%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 122 ms to 103 ms 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

5 to fix31
  • 1 image over 500 KB

    Ms-Gloria_Digital-Assets_Facebook-Header-V1.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    671 KiB

    1 image is downloaded at several times the size a phone draws it, for example Ms-Gloria_Digital-Assets_Facebook-Header-V1.jpg at 1,640 px wide, shown at 351 px. Resized copies would save about 671 KiB.

  • Page weight: 3.1 MB in 95 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 95 requests on a phone: images 1.7 MB (24), scripts 971 KiB (33) and fonts 248 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (1.1 MB) is 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.

  • An image on the first screen is lazy-loaded

    Ms-Gloria_Digital-Assets_Facebook-Header-V1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.9 g of CO₂ per visit

    0.88 g

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

Accessibility

2 to fixGoogle 9798
  • 1 link without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 9287
  • No meta description

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 150 internal links, 43 external

    The homepage links to 150 pages on truett.edu and 43 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “#1 Christian College in Georgia”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Homepage - Truett McConnell University”.

  • Canonical URL set

    The canonical URL is https://tmu.edu/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

    There is no https://tmu.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.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (828 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 10 pages without a meta description

    https://tmu.edu/request-information, https://tmu.edu/admissions/visit-tmu, https://tmu.edu/campus-community, https://tmu.edu/parents, https://tmu.edu/local-community and https://tmu.edu/events and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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 to fixGoogle 9693
  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

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

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 478 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY!” and “APPLY (OPENS IN NEW WINDOW)”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Request Info”, “Apply” and “Campus Event Schedule”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

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

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Google Cloud

Hiring

Hiring
6 open roles
Job board
careers page

Company

Founded
1947

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 truett.edu, including 19 speed issues, 2 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