citadel.edu website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.9 MB and 1.1 s of main-thread time.

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

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

About 646 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10 ms faster on a phone.

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

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

Facebook costs a phone 219 ms of main-thread work and 308 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.

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

userway.org costs a phone 46 ms of main-thread work and 377 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.

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

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

7 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 5.3 MB in 189 requests on a phone: images 2.9 MB (26), scripts 1.9 MB (57) and other files 314 KiB (76). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Military_College_Lockup_Horizontal_white.png at 3,002 px wide, shown at 312 px. Resized copies would save about 76 KiB.

2 images (250 KiB) 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.

1 image further down the page (165 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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.

Elements with visible text labels do not have matching accessible names. (1 element).

Your <h1> is empty.

The homepage links to 177 pages on citadel.edu and 29 external pages.

Your homepage links to /c2si and /jack-voltaic-conference-series, which answer with an error. Visitors hit a dead end and search engines drop them.

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

2 images failed to load on a phone, for example https://udxsva.com/tag?id=10703.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 links from your homepage to your own site are broken, for example https://www.citadel.edu/c2si (410).

2 links to other sites are dead, for example https://apply.citadel.edu/account/login (503).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

3 links go through two or more redirects, for example https://my.citadel.edu/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

citadel.edu has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 298 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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