Website review, no card needed

stu.edu logo

stu.edu website review

Visit site (opens in a new tab)Reviewed 4 November 202629 issues · 84 checks

This review found 29 issues worth fixing on stu.edu, 12 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.

  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
1.8 s1.5 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
163 ms118 msMay 16Oct 31133 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026152 ms
May 23, 2026155 ms
May 30, 2026155 ms
Jun 6, 2026158 ms
Jun 13, 2026152 ms
Jun 20, 2026144 ms
Jun 27, 2026145 ms
Jul 4, 2026141 ms
Jul 11, 2026137 ms
Jul 18, 2026144 ms
Jul 25, 2026135 ms
Aug 1, 2026129 ms
Aug 8, 2026126 ms
Aug 15, 2026123 ms
Aug 22, 2026129 ms
Aug 29, 2026137 ms
Sep 5, 2026142 ms
Sep 12, 2026145 ms
Sep 19, 2026142 ms
Sep 26, 2026133 ms
Oct 3, 2026130 ms
Oct 10, 2026129 ms
Oct 17, 2026128 ms
Oct 24, 2026133 ms
Oct 31, 2026133 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 stu.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stu.edu at 1.2 s1.2 s
  2. stu.edu at 2.5 s2.5 s
  3. stu.edu at 3.7 s3.7 s
  4. stu.edu at 4.9 s4.9 s
  5. stu.edu at 6.1 s6.1 s
  6. stu.edu at 7.4 s7.4 s
  7. stu.edu at 8.6 s8.6 s
  8. stu.edu at 9.8 s9.8 s

Speed

8 to fix56
  • Improve image delivery

    6.9 s · 3.7 MB

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

  • Render-blocking requests

    2.6 s

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

  • Reduce unused JavaScript

    1.4 s · 269 KiB

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

  • Reduce unused CSS

    900 ms · 138 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Minify JavaScript

    300 ms · 61 KiB

    61 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.4 s

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

  • 1,671 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and adtrafficquality.google and others), adding 468 KiB and 339 ms of main-thread time.

  • Minify CSS

    150 ms · 34 KiB

    34 KiB could be saved by minifying CSS.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    17 KiB

    Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need.

  • Use efficient cache lifetimes

    15 KiB

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

  • 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: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 24.7 s

    24.7 s

    Your largest element takes 24.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pursue Excellence BE GIANT!”.

  • Time to Interactive: 25.2 s

    25.2 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • 4 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

9 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: 2.1 s

    2.1 s

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

  • Real-user INP: 166 ms

    166 ms

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 586 ms

    586 ms

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

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

    -13%

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

  • Total Blocking Time: 116 ms

    116 ms

    Scripts block the page for only 116 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

4 to fix38
  • Page weight: 13.5 MB in 148 requests

    13.5 MB

    Your homepage downloads 13.5 MB in 148 requests on a phone: media 8.1 MB (1), images 4.2 MB (30) and scripts 746 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

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

  • 11 images below the first screen load straight away

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

  • 5 images in older formats

    5 images (1.6 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.

  • About 3.8 g of CO₂ per visit

    3.83 g

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

1 checks passed
  • 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 fixGoogle 9796
  • 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 (34 elements)

    All page content should be contained by landmarks: 34 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.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (166 characters)

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

  • 185 internal links, 74 external

    The homepage links to 185 pages on stu.edu and 74 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Make It Official - Become a Bobcat Today!”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “St. Thomas University | Miami Catholic University”.

  • Canonical URL set

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

  • Structured data in place

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

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

    There is no https://www.stu.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 (1,144 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.stu.edu/confirm, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages without a meta description

    https://www.stu.edu/request-info, https://www.stu.edu/visit, https://www.stu.edu/global, https://www.stu.edu/programs and https://www.stu.edu/faculty 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 85 found) and read each the way a search engine does.

5 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.stu.edu/.

  • 6 JavaScript errors while loading

    6 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 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 231 words

    The homepage has only about 231 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

5 checks passed
  • Clear next step on the first screen

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

  • 11 calls to action

    The homepage has 11 calls to action, for example “Apply Today”, “Request Information” and “Spirit Shop”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 stu.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
Hosting
Cloudflare

Company

Employees
957
Founded
1961

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on stu.edu, including 13 speed issues, 1 SEO issue 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