Website review, no card needed

cuaa.edu logo

cuaa.edu website review

Visit site (opens in a new tab)Reviewed 29 October 202629 issues · 77 checks

This review found 29 issues worth fixing on cuaa.edu, 12 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
3.3 s1.2 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20262.0 s
Jun 27, 20262.3 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.3 s
Aug 8, 20262.0 s
Aug 15, 20261.8 s
Aug 22, 20262.1 s
Aug 29, 20262.3 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.8 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20263.1 s
Oct 17, 20262.6 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
155 ms104 msMay 9Oct 24121 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026141 ms
May 23, 2026120 ms
May 30, 2026119 ms
Jun 6, 2026114 ms
Jun 13, 2026119 ms
Jun 20, 2026135 ms
Jun 27, 2026137 ms
Jul 4, 2026149 ms
Jul 11, 2026145 ms
Jul 18, 2026140 ms
Jul 25, 2026136 ms
Aug 1, 2026126 ms
Aug 8, 2026110 ms
Aug 15, 2026118 ms
Aug 22, 2026121 ms
Aug 29, 2026123 ms
Sep 5, 2026126 ms
Sep 12, 2026121 ms
Sep 19, 2026127 ms
Sep 26, 2026127 ms
Oct 3, 2026125 ms
Oct 10, 2026137 ms
Oct 17, 2026120 ms
Oct 24, 2026121 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 cuaa.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cuaa.edu at 0.8 s0.8 s
  2. cuaa.edu at 1.6 s1.6 s
  3. cuaa.edu at 2.4 s2.4 s
  4. cuaa.edu at 3.2 s3.2 s
  5. cuaa.edu at 4.0 s4.0 s
  6. cuaa.edu at 4.8 s4.8 s
  7. cuaa.edu at 5.5 s5.5 s
  8. cuaa.edu at 6.3 s6.3 s

Speed

9 to fix41
  • Render-blocking requests

    4.5 s

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

  • Reduce unused JavaScript

    1.9 s · 348 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 302 KiB

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

  • Mobile performance score: 41

    41/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 885 KiB and 901 ms of main-thread time.

  • Reduce unused CSS

    750 ms · 126 KiB

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

  • Google Tag Manager adds 590 ms

    590 ms

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

  • 10 long tasks on the main thread

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

  • Main-thread work: 2.5 s

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

  • Font display

    250 ms

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

  • Improve image delivery

    150 ms · 59 KiB

    2 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 12 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 36 ms

    36 ms

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

Core Web Vitals

7 to fix100
  • 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 element shown below.

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

  • Time to Interactive: 13.4 s

    13.4 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 665 ms

    665 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

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

    +16%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • 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 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

1 to fix33
  • Page weight: 4.3 MB in 69 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 69 requests on a phone: media 2.5 MB (1), scripts 963 KiB (21) and fonts 529 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.21 g

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

Accessibility

2 to fixGoogle 9998
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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

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

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

  • 70 internal links, 31 external

    The homepage links to 70 pages on cuaa.edu and 31 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Live Uncommon Live Uncommon Stacked Logo Live Uncommon Horizontal Logo”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Concordia University Ann Arbor”.

  • Canonical URL set

    The canonical URL is https://www.cuaa.edu/index.html.

  • Structured data in place

    Structured data found: CollegeOrUniversity.

  • 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.cuaa.edu/_files/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://www.cuaa.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 (710 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://www.cuaa.edu/facultystaff/lookup.cfm all use the title “Concordia University Ann Arbor”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.cuaa.edu/facultystaff/lookup.cfm, whose canonical is https://www.cuaa.edu/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://www.cuaa.edu/facultystaff/lookup.cfm took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 35 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 10071
  • 1 broken image

    1 image failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=C49GkwTn4MaHG3jJHYhQHPrwxETI&src=mh&evt=hi.

  • 3 small tap targets

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

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

1 checks passed
  • 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: 9 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.

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

    The homepage carries about 544 words of visible text.

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

  • 14 calls to action

    The homepage has 14 calls to action, for example “Apply”, “Apply Now” and “Request Information”.

  • 1 short form

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (measured from a US location before any click).

  • 21 other companies contacted

    Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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

Upkeep, stack and company

Stack

Hosting
CUW

Company

Employees
301
Founded
1963

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 cuaa.edu, including 16 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